| commit | 41644e75c5daef04f6849037c5abb98fe949769f | |
| author | Javier Martinez Canillas <javier.martinez@collabora.co.uk> | |
| Wed, 27 Feb 2013 01:30:51 +0000 (27 02:30 +0100) | ||
| committer | Benoit Cousson <benoit.cousson@linaro.org> | |
| Mon, 8 Apr 2013 22:18:00 +0000 (9 00:18 +0200) | ||
| tree | fcbfb2ac834384ff493bdf047abdc4cd645f33b8 | treesnapshot (tar.gz zip) |
| parent | 6e8489dffd57c8e1afdac3da971604140492de9e | commitdiff |
ARM: dts: OMAP3: reduce GPMC mapped registers address space
Currently the OMAP General-Purpose Memory Controller (GPMC) device
node maps 16 MB of address space for its hardware registers.
This is because the OMAP Technical Reference Manual says that the
GPMC module register address space size is 16 MB. But in practice
the maximum address offset used by a GPMC register is 0x02d0.
So, there is no need to map such a big address space for GPMC regs.
This change was suggested by Jon Hunter [1].
[1]: https://patchwork.kernel.org/patch/2057111/
Signed-off-by: Javier Martinez Canillas <javier.martinez@collabora.co.uk>
Acked-by: Jon Hunter <jon-hunter@ti.com>
Signed-off-by: Benoit Cousson <benoit.cousson@linaro.org>
Currently the OMAP General-Purpose Memory Controller (GPMC) device
node maps 16 MB of address space for its hardware registers.
This is because the OMAP Technical Reference Manual says that the
GPMC module register address space size is 16 MB. But in practice
the maximum address offset used by a GPMC register is 0x02d0.
So, there is no need to map such a big address space for GPMC regs.
This change was suggested by Jon Hunter [1].
[1]: https://patchwork.kernel.org/patch/2057111/
Signed-off-by: Javier Martinez Canillas <javier.martinez@collabora.co.uk>
Acked-by: Jon Hunter <jon-hunter@ti.com>
Signed-off-by: Benoit Cousson <benoit.cousson@linaro.org>
| arch/arm/boot/dts/omap3.dtsi | diffblobblamehistory |