Re: debugfs pinctrl crash on beagle-xm

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



* Nishanth Menon <nm@xxxxxx> [131212 15:38]:
> On 12/10/2013 04:41 AM, Tomi Valkeinen wrote:
> > Hi,
> > 
> > On beagle-xm, v3.13-rc3, I see the following crash if I use the pinctrl
> > debugfs:
> > 
> > # cat /debug/pinctrl/48002030.pinmux/pins
> > [   16.464233] Unhandled fault: external abort on non-linefetch (0x1028)
> > at 0xfa002268
> 
> in 3630 TRM, There is a hole in the memory map between
> 0x48002264(CONTROL_PADCONF_SDRC_CKE1) and
> 0x480025A0(CONTROL_PADCONF_SDRC_BA0) which obviously generates abort
> when read at 0x48002268
> 
> on 3430, we should also see a crash in the hole region
> 0x48002264(CONTROL_PADCONF_SDRC_CKE1) to
> 0x480025D8(CONTROL_PADCONF_ETK_CLK).
> 
> in dts, omap3_pmx_core: pinmux@48002030 describes the range as reg =
> <0x48002030 0x05cc> (which is the max range for the module)
> 
> wish pinctrl-single driver could support handle multiple address ranges?
> 
> [...]

There's an RFC patch from Laurent to split the pmx_core into two instances
that should take care of this issue:

[PATCH/RFC] ARM: omap3: Split the pinmux core device

Regards,

Tony
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux