diff options
| author | Florian Vaussard <florian.vaussard@epfl.ch> | 2014-03-07 20:22:11 +0100 |
|---|---|---|
| committer | Tony Lindgren <tony@atomide.com> | 2014-03-12 10:17:25 -0700 |
| commit | af3c0380ebb1de0cd688a9e02d75da3cc79e43f6 (patch) | |
| tree | aa54564dc15e0675ce4d2ec8d0a72dfef4e3bf44 /arch/arm/boot/dts/imx6q-sabrelite.dts | |
| parent | cfbf8d4857c26a8a307fb7cd258074c9dcd8c691 (diff) | |
ARM: dts: overo: reorganize include files
Currently, overo-related include files are organized as follow:
omap3-overo.dtsi
|
|
omap34xx.dtsi omap3-overo-tobi-common.dtsi omap36xx.dtsi
| | | |
--------------- ---------------
| |
omap3-overo-tobi.dts omap3-overo-storm-tobi.dts
This is unpractical when one has to deal with SoC-specific pinmux
belonging to the omap3_pmx_core2 (defined in omap34xx/omap36xx),
for pins related to the processor board. With the current
hierarchy, such pinmux has to be defined in the expansion board's
.dts, which is not logical.
This patches reorganizes the files to add (yet another) abstraction
layer between the processor and the expansion boards.
omap34xx.dtsi omap3-overo-base.dtsi omap36xx.dtsi
| | | |
--------------- ---------------
| |
omap3-overo.dtsi omap3-overo-storm.dtsi
| |
-------- ------
| omap3-overo-tobi-common.dtsi |
| | | |
--------------- ---------------
| |
omap3-overo-tobi.dts omap3-overo-storm-tobi.dts
Signed-off-by: Florian Vaussard <florian.vaussard@epfl.ch>
Signed-off-by: Tony Lindgren <tony@atomide.com>
Diffstat (limited to 'arch/arm/boot/dts/imx6q-sabrelite.dts')
0 files changed, 0 insertions, 0 deletions