aboutsummaryrefslogtreecommitdiff
path: root/drivers/mtd/lpddr/lpddr_cmds.c
diff options
context:
space:
mode:
authorPaul Walmsley <[email protected]>2010-02-22 22:09:20 -0700
committerPaul Walmsley <[email protected]>2010-02-24 12:16:15 -0700
commit657ebfadc19c5a14f709dee1645082828330d5d4 (patch)
tree26d615ae6e76437e0852b8d7fc060a070786f369 /drivers/mtd/lpddr/lpddr_cmds.c
parentb92c170d019db7554db95380d2e1dfb3a368e350 (diff)
OMAP3/4 clock: split into per-chip family files
clock34xx_data.c now contains data for the OMAP34xx family, the OMAP36xx family, and the OMAP3517 family, so rename it to clock3xxx_data.c. Rename clock34xx.c to clock3xxx.c, and move the chip family-specific clock functions to clock34xx.c, clock36xx.c, or clock3517.c, as appropriate. So now "clock3xxx.*" refers to the OMAP3 superset. The main goal here is to prepare to compile chip family-specific clock functions only for kernel builds that target that chip family. To get to that point, we also need to add CONFIG_SOC_* options for those other chip families; that will be done in future patches, planned for 2.6.35. OMAP4 is also affected by this. It duplicated the OMAP3 non-CORE DPLL clkops structure. The OMAP4 variant of this clkops structure has been removed, and since there was nothing else currently in clock44xx.c, it too has been removed -- it can always be added back later when there is some content for it. (The OMAP4 clock autogeneration scripts have been updated accordingly.) Signed-off-by: Paul Walmsley <[email protected]> Cc: BenoĆ®t Cousson <[email protected]> Cc: Rajendra Nayak <[email protected]> Cc: Ranjith Lohithakshan <[email protected]> Cc: Tony Lindgren <[email protected]>
Diffstat (limited to 'drivers/mtd/lpddr/lpddr_cmds.c')
0 files changed, 0 insertions, 0 deletions