From: Tony Lindgren <tony@atomide.com>
To: "H. Nikolaus Schaller" <hns@goldelico.com>
Cc: "Benoît Cousson" <bcousson@baylibre.com>,
"Rob Herring" <robh+dt@kernel.org>,
"Mark Rutland" <mark.rutland@arm.com>,
"Linus Walleij" <linus.walleij@linaro.org>,
"Bartosz Golaszewski" <bgolaszewski@baylibre.com>,
linux-omap@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org,
letux-kernel@openphoenux.org
Subject: Re: [BUG/PATCH 1/4] DTS: GTA04: SPI / gpiolib: work around a regression that unhides a broken legacy handler, which makes the gta04 display inoperable
Date: Mon, 1 Apr 2019 09:46:17 -0700 [thread overview]
Message-ID: <20190401164617.GH49658@atomide.com> (raw)
In-Reply-To: <e8d784f7fb06fd3a6a92bc730f919352c4ad4411.1554026842.git.hns@goldelico.com>
Hi,
* H. Nikolaus Schaller <hns@goldelico.com> [190331 10:08]:
> This is an ugly workaround for a regression introduced into v5.1-rc1 by
>
> <c1c04cea13dc234ce9a4504879ddd36ea524d880>
You should standardized commit references like this instead:
c1c04cea13dc ("gpio: of: Fix logic inversion")
Then please also include a proper Fixes tag.
You can configure an alias for it to make things easier:
git log --abbrev=12 --pretty=format:"%h (\"%s\")"
> --- a/arch/arm/boot/dts/omap3-gta04.dtsi
> +++ b/arch/arm/boot/dts/omap3-gta04.dtsi
> @@ -114,6 +114,7 @@
> gpio-miso = <&gpio1 18 GPIO_ACTIVE_HIGH>;
> gpio-mosi = <&gpio1 20 GPIO_ACTIVE_HIGH>;
> cs-gpios = <&gpio1 19 GPIO_ACTIVE_HIGH>;
> + spi-cs-high; /* make the legacy handler in gpiolib not intervene */
> num-chipselects = <1>;
>
> /* lcd panel */
> @@ -123,6 +124,7 @@
> spi-max-frequency = <100000>;
> spi-cpol;
> spi-cpha;
> + spi-cs-high; /* here is where it should be but this is ignored by a bug in the gpiolib handler */
>
> backlight= <&backlight>;
> label = "lcd";
So what's the plan with this fix? Add this for v5.2-rc cycle,
then revert it later? I'd probably go directly for the proper
fix if possible.
Regards,
Tony
next prev parent reply other threads:[~2019-04-01 16:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-31 10:07 [BUG/PATCH 0/4] gpiolib: fix issues with legacy spi-cs-high handling H. Nikolaus Schaller
2019-03-31 10:07 ` [BUG/PATCH 1/4] DTS: GTA04: SPI / gpiolib: work around a regression that unhides a broken legacy handler, which makes the gta04 display inoperable H. Nikolaus Schaller
2019-04-01 16:46 ` Tony Lindgren [this message]
2019-04-01 16:56 ` H. Nikolaus Schaller
2019-04-01 16:58 ` Tony Lindgren
2019-03-31 10:07 ` [BUG/PATCH 2/4] REVERT: DTS: GTA04: SPI / gpiolib: no no no, we do not want to "fix" our device tree file H. Nikolaus Schaller
2019-03-31 10:07 ` [BUG/PATCH 3/4] gpiolib: make legacy handling for spi-cs-high optional H. Nikolaus Schaller
2019-03-31 10:07 ` [BUG/PATCH 4/4] gpiolib: spi-cs-high is checking the wrong node (the controller and not the SPI slave device) H. Nikolaus Schaller
2019-04-01 16:59 ` [BUG/PATCH 0/4] gpiolib: fix issues with legacy spi-cs-high handling H. Nikolaus Schaller
2019-04-02 3:19 ` 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=20190401164617.GH49658@atomide.com \
--to=tony@atomide.com \
--cc=bcousson@baylibre.com \
--cc=bgolaszewski@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=hns@goldelico.com \
--cc=letux-kernel@openphoenux.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.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).