+ *
+ * MISRA Rule |
+ * Rule Class (Required/Advisory) |
+ * Rule Description |
+ * Description of Deviation(s) |
+ *
+ *
+ * 11.4 |
+ * A |
+ * The cast should not be performed between a pointer to the object type
+ * and a different pointer to the object type. |
+ * The cast from the object type and a different pointer to the object
+ * was used intentionally because of the performance reasons. |
+ *
+ *
+ * 14.2 |
+ * R |
+ * All non-null statements shall either have at least one side-effect,
+ * however executed, or cause control flow to change. |
+ * To maintain common codebase, some variables, unused for a specific
+ * device, are casted to void to prevent generation of an unused variable
+ * compiler warning. |
+ *
+ *
+ * 16.7 |
+ * A |
+ * The object addressed by the pointer parameter is not modified and so
+ * the pointer could be of type 'pointer to const'. |
+ * The warning is generated because of the pointer dereferencing to
+ * address which makes the MISRA checker think the data is not
+ * modified. |
+ *
+ *
+ * 17.4 |
+ * R |
+ * The array indexing shall be the only allowed form of pointer
+ * arithmetic. |
+ * The pointer arithmetic used in several places on the Cy_Em_EEPROM
+ * implementation is safe and preferred because it increases the code
+ * flexibility. |
+ *
+ *
+ * 19.7 |
+ * A |
+ * A function shall be used in preference to a function-like macro. |
+ * Macro is used because of performance reasons. |
+ *
+ *
+ *
+ * \section group_em_eeprom_changelog Changelog
+ *