From: Simon Horman <horms@verge.net.au>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
Magnus Damm <magnus.damm@gmail.com>,
Linus Walleij <linus.walleij@linaro.org>,
Wolfram Sang <wsa+renesas@sang-engineering.com>,
linux-renesas-soc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-gpio@vger.kernel.org
Subject: Re: [PATCH v2] ARM: dts: armadillo800eva: Split LCD mux and gpio
Date: Thu, 8 Jun 2017 15:45:21 +0200 [thread overview]
Message-ID: <20170608134516.GC19821@verge.net.au> (raw)
In-Reply-To: <38369176.p2s9nCEmhA@avalon>
On Fri, Jun 02, 2017 at 08:53:26AM +0300, Laurent Pinchart wrote:
> Hi Geert,
>
> Thank you for the patch.
>
> On Thursday 01 Jun 2017 12:27:00 Geert Uytterhoeven wrote:
> > Configuration of the lcd0 pinmux group and GPIO hog for the external
> > GPIO mux are done using a single device node, causing the "output-high"
> > property to be applied to both. This will fail for the pinmux group,
> > but doesn't cause any harm, as the failure is ignored silently.
> >
> > However, after "pinctrl: sh-pfc: propagate errors on group config", the
> > failure will become fatal, leading to a broken display:
> >
> > sh-pfc e6050000.pin-controller: pin_config_group_set op failed for group
> > 102 sh-pfc e6050000.pin-controller: Error applying setting, reverse things
> > back sh-pfc e6050000.pin-controller: failed to select default state
> >
> > Move the GPIO hog to its own node to fix this.
> >
> > Fixes: ffd2f9a5afb730b9 ("ARM: shmobile: armadillo800eva dts: Add pinctrl
> > and gpio-hog for lcdc0") Signed-off-by: Geert Uytterhoeven
> > <geert+renesas@glider.be>
> > ---
> > This is a hard dependency for "pinctrl: sh-pfc: propagate errors on
> > group config" (https://patchwork.kernel.org/patch/9186713/).
> >
> > v2:
> > - Keep the GPIO hog, but move it to its own node, instead of using
> > another level of subnodes. As the GPIO hog node is not referenced from
> > a pinctrl-0 property, pinconf doesn't fail with "No pin or group
> > provided in DT node".
>
> I like this approach better, it allows us to drive the output instead of
> pulling it up, without requiring a full implementation of output drive control
> in the pfc driver.
>
> Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Thanks, I have queued this up as a fix for v4.12.
WARNING: multiple messages have this Message-ID (diff)
From: horms@verge.net.au (Simon Horman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] ARM: dts: armadillo800eva: Split LCD mux and gpio
Date: Thu, 8 Jun 2017 15:45:21 +0200 [thread overview]
Message-ID: <20170608134516.GC19821@verge.net.au> (raw)
In-Reply-To: <38369176.p2s9nCEmhA@avalon>
On Fri, Jun 02, 2017 at 08:53:26AM +0300, Laurent Pinchart wrote:
> Hi Geert,
>
> Thank you for the patch.
>
> On Thursday 01 Jun 2017 12:27:00 Geert Uytterhoeven wrote:
> > Configuration of the lcd0 pinmux group and GPIO hog for the external
> > GPIO mux are done using a single device node, causing the "output-high"
> > property to be applied to both. This will fail for the pinmux group,
> > but doesn't cause any harm, as the failure is ignored silently.
> >
> > However, after "pinctrl: sh-pfc: propagate errors on group config", the
> > failure will become fatal, leading to a broken display:
> >
> > sh-pfc e6050000.pin-controller: pin_config_group_set op failed for group
> > 102 sh-pfc e6050000.pin-controller: Error applying setting, reverse things
> > back sh-pfc e6050000.pin-controller: failed to select default state
> >
> > Move the GPIO hog to its own node to fix this.
> >
> > Fixes: ffd2f9a5afb730b9 ("ARM: shmobile: armadillo800eva dts: Add pinctrl
> > and gpio-hog for lcdc0") Signed-off-by: Geert Uytterhoeven
> > <geert+renesas@glider.be>
> > ---
> > This is a hard dependency for "pinctrl: sh-pfc: propagate errors on
> > group config" (https://patchwork.kernel.org/patch/9186713/).
> >
> > v2:
> > - Keep the GPIO hog, but move it to its own node, instead of using
> > another level of subnodes. As the GPIO hog node is not referenced from
> > a pinctrl-0 property, pinconf doesn't fail with "No pin or group
> > provided in DT node".
>
> I like this approach better, it allows us to drive the output instead of
> pulling it up, without requiring a full implementation of output drive control
> in the pfc driver.
>
> Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Thanks, I have queued this up as a fix for v4.12.
next prev parent reply other threads:[~2017-06-08 13:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-01 10:27 [PATCH v2] ARM: dts: armadillo800eva: Split LCD mux and gpio Geert Uytterhoeven
2017-06-01 10:27 ` Geert Uytterhoeven
2017-06-02 5:53 ` Laurent Pinchart
2017-06-02 5:53 ` Laurent Pinchart
2017-06-08 13:45 ` Simon Horman [this message]
2017-06-08 13:45 ` Simon Horman
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=20170608134516.GC19821@verge.net.au \
--to=horms@verge.net.au \
--cc=geert+renesas@glider.be \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=wsa+renesas@sang-engineering.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.