Rename some register fields to "look familiar" or be more descriptive
- In binary fields, avoid ambiguous names. For example: FRAME_TYPE (0 means FD or 1 means FD?) -> FRAME_FDTYPE (or, if we want to be less verbose - FDF).
- A philosophic question - should the names be long and descriptive, or short?
- In documentation, always mention the meaning of the shortcut (the full register name).
-
STATUS (SR)
- RBS -> RXNE (RX Not Empty)
- TBS -> TXNF (TX Not Empty)
- DO(S) (Data Overrun Status)
- ET -> EF (Error Frame / Error Transmitted?)
- ES -> EW (Error Warning)
- BS -> IDLE/BI (Bus Idle)
-
SETTINGS (CR?)
- INT_LOOP - looks like it concerns interrupts but doesn't (maybe just LOOP)
-
INT (ISR,IESR,IECR,IMSR,IMCR):
RI -> FRI / RFITI -> FTI / TFI- RFI -> RXFI (RX Full Interrupt)
- RBNEI -> RXNEI (RX Not Empty Interrupt)
-
EWL
- EWL_LIMIT -> EW_LIMIT / EWL
-
RX_STATUS
- RX_EMPTY -> RXE
- RX_FULL -> RXF
-
TX_COMMAND
- TXIn -> TXBn ? What does the I stand for?
-
FRAME_FORM_W
- ID_TYPE -> EFF/ID_EXTENDED (Extended Frame Format)
- FR_TYPE -> FDF/FR_FD