Fwd: Tegra 30 System hangs because of commit "pinctrl: move subsystem mutex to pinctrl_dev struct"

[Bryan Wu]

On Mon, Apr 29, 2013 at 12:59 PM, Stephen Warren <swarren at wwwdotorg.org> wrote:
> On 04/29/13 12:41, Bryan Wu wrote:
>>
>> Forward to ARM and Tegra mail list.
>>
>> ---------- Forwarded message ----------
>> From: Bryan Wu <cooloney at gmail.com>
>> Date: Mon, Apr 29, 2013 at 11:15 AM
>> Subject: Tegra 30 System hangs because of commit "pinctrl: move
>> subsystem mutex to pinctrl_dev struct"
>> To: patrice.chotard at st.com, Linus Walleij <linus.walleij at linaro.org>
>> Cc: Stephen Warren <swarren at wwwdotorg.org>,
>> "linux-next at vger.kernel.org" <linux-next at vger.kernel.org>
>>
>>
>> Hi Patrice and Linus,
>>
>> I'm running linux-next on my Tegra 30 system everyday. But since
>> next-20130426 release, the linux-next kernel will hang on my Tegra 30
>> boards like Cardhu and Beaver.
>>
>> After some bisect and comparing to next-20130424, I found the commit
>> "pinctrl: move subsystem mutex to pinctrl_dev struct" introduced this
>> issue. If I simply revert this patch in next-20130429, system boots up
>> as before.
>>
>> Could you please help to check this?
>
>
> I would suggest simply dropping or reverting this patch; I had pointed out a
> long time ago that it was unlikely to be correct.
>
> My guess/suspicion is a recursive lock attempt during processing hogs during
> pinctrl device registration, or perhaps during dt->map conversion. Bryan,
> are you able to confirm this?

Oh, no worries now. It was fixed in pinctrl for-next branch. I guess
linux-next will be update soon.

I will keep testing this when new linux-next is out.

-Bryan