imx233: generate register headers using headergen_v2 and update code for it

NOTE: this commit does not introduce any change, ideally even the binary should
be almost the same. I checked the disassembly by hand and there are only a few
differences here and there, mostly the compiler decides to compile very close
expressions slightly differently. I tried to run the new code on several targets
to make sure and saw no difference.

The major syntax changes of the new headers are as follows:
- BF_{WR,SET,CLR} are now superpowerful and allows to set several fileds at once:
  BF_WR(reg, field1(value1), field2(value2), ...)
- BF_CS (use like BF_WR) does a write to reg_CLR and then reg_SET instead of RMW
- there is no more need for macros like BF_{WR_,SET,CLR}_V, since one can simply
  BF_WR with field_V(name)
- the old BF_SETV macro has no trivial equivalent and is replaced with its
  its equivalent for BF_WR(reg_SET, ...)

I also rename the register headers: "regs/regs-x.h" -> "regs/x.h" to avoid the
redundant "regs".

Final note: the registers were generated using the following command:
./headergen_v2 -g imx -o ../../firmware/target/arm/imx233/regs/ desc/regs-stmp3{600,700,780}.xml

Change-Id: I7485e8b4315a0929a8edb63e7fa1edcaa54b1edc

1 files changed, 3 insertions, 3 deletions

diff --git a/firmware/drivers/rtc/rtc_imx233.c b/firmware/drivers/rtc/rtc_imx233.c
index c2df4d1..df139db 100644
--- a/firmware/drivers/rtc/rtc_imx233.c
+++ b/firmware/drivers/rtc/rtc_imx233.c
@@ -114,9 +114,9 @@ void rtc_enable_alarm(bool enable)
     BF_CLR(RTC_CTRL, ALARM_IRQ_EN);
     BF_CLR(RTC_CTRL, ALARM_IRQ);
     uint32_t val = imx233_rtc_read_persistent(0);
-    BF_WRX(val, RTC_PERSISTENT0, ALARM_EN, enable);
-    BF_WRX(val, RTC_PERSISTENT0, ALARM_WAKE_EN, enable);
-    BF_WRX(val, RTC_PERSISTENT0, ALARM_WAKE, 0);
+    BF_WRX(val, RTC_PERSISTENT0, ALARM_EN(enable));
+    BF_WRX(val, RTC_PERSISTENT0, ALARM_WAKE_EN(enable));
+    BF_WRX(val, RTC_PERSISTENT0, ALARM_WAKE(0));
     imx233_rtc_write_persistent(0, val);
 }