Dear "Hiremath, Vaibhav",
In message 19F8576C6E063C45BE387C64729E739404370D7ACF@dbde02.ent.ti.com you wrote:
#define CONTROL_PADCONF_D2D_SBUSFLAG 0x0260 #define CONTROL_PADCONF_SDRC_CKE0 0x0262 #define CONTROL_PADCONF_SDRC_CKE1 0x0264 +/* AM3517 specific */ +#define CONTROL_PADCONF_CCDC_PCLK 0x01E4 +#define CONTROL_PADCONF_CCDC_FIELD 0x01E6 +#define CONTROL_PADCONF_CCDC_HD 0x01E8 +#define CONTROL_PADCONF_CCDC_VD 0x01EA +#define CONTROL_PADCONF_CCDC_WEN 0x01EC
...
Where are these defines used? I think I don't see them in any of the patches of this patch series?
[Hiremath, Vaibhav] These are being used in board/ty/am3517/am3517evm.c file under the function set_muxconf_regs().
As Tom noted it probably makes sense to move these to a board specific file.
But then, this looks very much like register offsets for some device. If this should be the case, plase make sure to convert this into a C struct and use appropriate accesor macros.
Best regards,
Wolfgang Denk