From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Simon Horman <horms@verge.net.au>,
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: Fri, 02 Jun 2017 08:53:26 +0300 [thread overview]
Message-ID: <38369176.p2s9nCEmhA@avalon> (raw)
In-Reply-To: <1496312820-27237-1-git-send-email-geert+renesas@glider.be>
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>
> ---
> arch/arm/boot/dts/r8a7740-armadillo800eva.dts | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/arch/arm/boot/dts/r8a7740-armadillo800eva.dts
> b/arch/arm/boot/dts/r8a7740-armadillo800eva.dts index
> 297b1f10f7346a9f..8c85d3ee5f5e7bfd 100644
> --- a/arch/arm/boot/dts/r8a7740-armadillo800eva.dts
> +++ b/arch/arm/boot/dts/r8a7740-armadillo800eva.dts
> @@ -273,7 +273,9 @@
> lcd0_pins: lcd0 {
> groups = "lcd0_data24_0", "lcd0_lclk_1", "lcd0_sync";
> function = "lcd0";
> + };
>
> + lcd0_mux {
> /* DBGMD/LCDC0/FSIA MUX */
> gpio-hog;
> gpios = <176 0>;
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2017-06-02 5:53 UTC|newest]
Thread overview: 3+ 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-02 5:53 ` Laurent Pinchart [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=38369176.p2s9nCEmhA@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=geert+renesas@glider.be \
--cc=horms@verge.net.au \
--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 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).