On Wed, Dec 04, 2013 at 06:11:50PM +0100, Laurent Pinchart wrote: > 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. > > Signed-off-by: Laurent Pinchart <laurent.pinchart@xxxxxxxxxxxxxxxx> > --- > arch/arm/boot/dts/omap3-beagle-xm.dts | 45 ++++++++++++++++++++++++++++------- > arch/arm/boot/dts/omap3-beagle.dts | 28 +++++++++++++++------- > arch/arm/boot/dts/omap3-igep0020.dts | 26 ++++++++++---------- > arch/arm/boot/dts/omap3-zoom3.dts | 19 ++++++++++----- > arch/arm/boot/dts/omap3.dtsi | 13 +++++++++- > 5 files changed, 95 insertions(+), 36 deletions(-) > > While working on the OMAP3 ISP driver I've run into a failure to request a > memory region already requested by the pinctrl-single driver. This patch is an > attempt to fix the problem. An alternative approach would be to support > multiple reg values in the pinctrl-single driver, but that might not be much > cleaner. I'm open to suggestions. Acked-By: Sebastian Reichel <sre@xxxxxxxxxx> I haven't checked the board dts files, but the change in omap3.dtsi is needed to "fix a external abort on non-linefetch" when doing cat /sys/kernel/debug/pinctrl/.../pins on my Nokia N900. -- Sebastian
Attachment:
signature.asc
Description: Digital signature
