diff options
author | Paul Walmsley <paul@pwsan.com> | 2010-12-21 15:30:55 -0700 |
---|---|---|
committer | Paul Walmsley <paul@pwsan.com> | 2010-12-21 20:01:54 -0700 |
commit | cdb54c4457d68994da7c2e16907adfbfc130060d (patch) | |
tree | 3d360dbb25dbcad732a378531db14aec69b74bf0 /arch/arm/mach-omap2/board-3430sdp.c | |
parent | 0f318fd52d7e251c5f48416c3e7156acc680d81c (diff) | |
download | blackbird-op-linux-cdb54c4457d68994da7c2e16907adfbfc130060d.tar.gz blackbird-op-linux-cdb54c4457d68994da7c2e16907adfbfc130060d.zip |
OMAP4: PRCM: rename _MOD macros to _INST
Back in the OMAP2/3 PRCM interface days, the macros that referred to
the offsets of individual PRM/CM instances from the top of the PRM/CM
hardware modules were incorrectly suffixed with "_MOD". (They should
have been suffixed with something like "_INST" or "_INSTANCE".) These
days, now that we have better contact with the OMAP hardware people,
we know that this naming is wrong. And in fact in OMAP4, there are
actual hardware module offsets inside the instances, so the incorrect
naming gets confusing very quickly for anyone who knows the hardware.
Fix this naming for OMAP4, before things get too far along, by
changing "_MOD" to "_INST" on the end of these macros. So, for
example, OMAP4430_CM2_INSTR_MOD becomes OMAP4430_CM2_INSTR_INST.
This unfortunately creates quite a large diff, but it is a
straightforward rename. This patch should not result in any
functional changes.
The autogeneration scripts have been updated accordingly.
Signed-off-by: Paul Walmsley <paul@pwsan.com>
Cc: Benoît Cousson <b-cousson@ti.com>
Cc: Rajendra Nayak <rnayak@ti.com>
Cc: Santosh Shilimkar <santosh.shilimkar@ti.com>
Reviewed-by: Kevin Hilman <khilman@deeprootsystems.com>
Tested-by: Kevin Hilman <khilman@deeprootsystems.com>
Tested-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
Tested-by: Rajendra Nayak <rnayak@ti.com>
Diffstat (limited to 'arch/arm/mach-omap2/board-3430sdp.c')
0 files changed, 0 insertions, 0 deletions