From: sebastian.hesselbarth@gmail.com (Sebastian Hesselbarth)
To: linux-arm-kernel@lists.infradead.org
Subject: [BISECTED] v4.5-rc1 mvebu/kirkwood-pinctrl regression
Date: Tue, 26 Jan 2016 22:17:12 +0100 [thread overview]
Message-ID: <56A7E258.7040006@gmail.com> (raw)
In-Reply-To: <20160126202017.GI27473@lunn.ch>
On 26.01.2016 21:20, Andrew Lunn wrote:
> On Tue, Jan 26, 2016 at 08:22:51PM +0200, Aaro Koskinen wrote:
>> Hi,
>>
>> On kirkwood-openrd-client SDIO stopped working, and I get the following
>> pinctrl logs:
>>
>> [ 0.096502] pinctrl core: initialized pinctrl subsystem
>> [ 1.765275] kirkwood-pinctrl f1010000.pin-controller: registered pinctrl driver
>> [ 5.375416] kirkwood-pinctrl f1010000.pin-controller: unsupported function sdio on pin mpp12
>> [ 5.383972] pinctrl core: failed to register map default (5): invalid type given
>
> Humm.. What does
>
> /sys/kernel/debug/pinctrl/f1010000.pin-controller/pinmux-functions show?
>
> On my 6282 i have:
>
> function: sdio, groups = [ mpp12 mpp13 mpp14 mpp15 mpp16 mpp17 ]
>
> What about
>
> /sys/kernel/debug/pinctrl/f1010000.pin-controller/pinmux-pins
>
> Has something already claimed it?
Nah, Aaro is right, pinctrl-mvebu is broken for mpp12 on 6281. We should
revisit static mpp mode to dynamic mpp group assignment one day.
I'll send a fix in a minute when compiling v4.5-rc1 is done.
Sebastian
next prev parent reply other threads:[~2016-01-26 21:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-26 18:22 [BISECTED] v4.5-rc1 mvebu/kirkwood-pinctrl regression Aaro Koskinen
2016-01-26 20:20 ` Andrew Lunn
2016-01-26 21:17 ` Sebastian Hesselbarth [this message]
2016-01-26 21:49 ` [PATCH] pinctrl: mvebu: fix num_settings in mpp group assignment Sebastian Hesselbarth
2016-01-26 22:42 ` Aaro Koskinen
2016-02-01 22:48 ` [PATCH v2] " Sebastian Hesselbarth
2016-02-02 20:19 ` Aaro Koskinen
2016-02-13 22:52 ` Linus Walleij
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=56A7E258.7040006@gmail.com \
--to=sebastian.hesselbarth@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).