From: Nishanth Menon <nm@ti.com>
To: Tony Lindgren <tony@atomide.com>
Cc: Tomi Valkeinen <tomi.valkeinen@ti.com>,
linux-omap <linux-omap@vger.kernel.org>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Subject: Re: debugfs pinctrl crash on beagle-xm
Date: Fri, 13 Dec 2013 11:10:20 -0600 [thread overview]
Message-ID: <52AB3F7C.9050201@ti.com> (raw)
In-Reply-To: <20131213170438.GA28184@atomide.com>
On 12/13/2013 11:04 AM, Tony Lindgren wrote:
> * Nishanth Menon <nm@ti.com> [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
Arggh.. yet again, I missed that :( grr...
https://patchwork.kernel.org/patch/3335341/ follows the similar
direction Laurent took for https://patchwork.kernel.org/patch/3283781/
--
Regards,
Nishanth Menon
prev parent reply other threads:[~2013-12-13 17:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-10 10:41 debugfs pinctrl crash on beagle-xm Tomi Valkeinen
2013-12-12 23:36 ` Nishanth Menon
2013-12-13 17:04 ` Tony Lindgren
2013-12-13 17:10 ` Nishanth Menon [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52AB3F7C.9050201@ti.com \
--to=nm@ti.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-omap@vger.kernel.org \
--cc=tomi.valkeinen@ti.com \
--cc=tony@atomide.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).