diff options
| author | Laurent Pinchart <laurent.pinchart@ideasonboard.com> | 2014-01-07 23:01:39 +0100 |
|---|---|---|
| committer | Tony Lindgren <tony@atomide.com> | 2014-01-07 23:01:39 +0100 |
| commit | 3d495383648a7cda3ea51a1e2fa5d288581479aa (patch) | |
| tree | 3e8bf6aa3b7c1690a853e64491efd3be0f170ea2 /lib/kstrtox.c | |
| parent | ARM: dts: Add omap specific pinctrl defines to use padconf addresses (diff) | |
| download | linux-3d495383648a7cda3ea51a1e2fa5d288581479aa.tar.xz linux-3d495383648a7cda3ea51a1e2fa5d288581479aa.zip | |
ARM: dts: Split omap3 pinmux core device
The omap3_pmx_core pinmux device in the device tree handles the system
controller module (SCM) PADCONFS fonction. Its control registers are
split in two distinct areas, with other SCM registers in-between. Those
other registers can't thus be requested by other drivers as the memory
region gets reserved by the pinmux driver.
Split the omap3_pmx_core device tree node in two for the two memory
regions. The second region address and size depends on the SoC model.
The change in omap3.dtsi fixes an "external abort on non-linefetch" when
doing
cat /sys/kernel/debug/pinctrl/.../pins
on a Nokia N900.
Note that the core2 padconf region is different for 3430 vs 3630,
and does not exist on 3517 as noted by Nishanth Menon <nm@ti.com>.
Reported-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
Signed-off-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Acked-By: Sebastian Reichel <sre@debian.org>
Signed-off-by: Nishanth Menon <nm@ti.com>
[tony@atomide.com: updated for 3430 vs 3630 core2 based on Nishant's patch]
Signed-off-by: Tony Lindgren <tony@atomide.com>
Diffstat (limited to 'lib/kstrtox.c')
0 files changed, 0 insertions, 0 deletions