From: Richard Fitzgerald <rf@opensource.cirrus.com>
To: "Mika Penttilä" <mika.penttila@nextfour.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [REGRESSION][BISECTED] i.MX6 pinctrl hogs stopped working
Date: Tue, 10 Apr 2018 11:21:29 +0100 [thread overview]
Message-ID: <1d3c6099-3b33-d5dd-e12b-903586dc79f3@opensource.cirrus.com> (raw)
In-Reply-To: <8b07e30a-7dd1-7923-dc50-b84f0e43e9e9@nextfour.com>
On 04/04/18 06:33, Mika Penttilä wrote:
> Hi!
>
> Reverting this made the hogs on a i.MX6 board work again. :
>
>
> commit b89405b6102fcc3746f43697b826028caa94c823
> Author: Richard Fitzgerald <rf@opensource.cirrus.com>
> Date: Wed Feb 28 15:53:06 2018 +0000
>
> pinctrl: devicetree: Fix dt_to_map_one_config handling of hogs
>
>
>
> --Mika
>
I think you should check whether the bug is with the i.MX6 driver
relying on the previous buggy behaviour of pinctrl. I haven't got
i.MX6 hardware to test myself.
The bug I fixed in that patch was that when pinctrl is probing a
pinctrl driver it would try to apply all the pinctrl settings
listed in a dt node to the pinctrl driver it is probing instead
of the pinctrl drivers they actually refer to. This was a bug
introduced by an earlier patch (which unfortunately I forgot to
include a fixes line reference to)
pinctrl: core: Use delayed work for hogs
So if a pinctrl driver "A" had a dependency on another pinctrl
driver "B" those dependencies wouldn't be properly created because
all the "B" pinctrl DT entries would be attempted against "A"
instead of "B". This caused failures if a pinctrl driver had a
dependency on another pinctrl driver, of if creating a pinctrl
driver that is a child of an MFD and that MFD has dependencies
on another pinctrl driver.
next prev parent reply other threads:[~2018-04-10 10:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-04 5:33 Mika Penttilä
2018-04-10 10:21 ` Richard Fitzgerald [this message]
2018-04-10 18:33 ` Mika Penttilä
2018-04-17 8:50 ` Richard Fitzgerald
2018-04-27 9:13 ` Richard Fitzgerald
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=1d3c6099-3b33-d5dd-e12b-903586dc79f3@opensource.cirrus.com \
--to=rf@opensource.cirrus.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.penttila@nextfour.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
all inboxes | Powered by JetHome®