From: Sven Van Asbroeck <thesven73@gmail.com>
To: Mark Brown <broonie@kernel.org>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Jonathan Cameron <jonathan.cameron@huawei.com>,
Lukas Wunner <lukas@wunner.de>,
linux-spi <linux-spi@vger.kernel.org>,
Simon Han <z.han@kunbus.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Charles Keepax <ckeepax@opensource.cirrus.com>
Subject: Re: [PATCH v1] spi: fix client driver breakages when using GPIO descriptors
Date: Wed, 11 Nov 2020 11:24:14 -0500 [thread overview]
Message-ID: <CAGngYiVAdPSCEQm5pJdFQ+3VpwNH1vGD6rPNK1_SQK3Uvfbt5A@mail.gmail.com> (raw)
In-Reply-To: <160510968064.12304.14797288117651443603.b4-ty@kernel.org>
On Wed, Nov 11, 2020 at 10:48 AM Mark Brown <broonie@kernel.org> wrote:
>
> Applied to
>
> https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
Thank you !
Now that our minds are still focused on this subject, should
commit 138c9c32f090 ("spi: spidev: Fix CS polarity if GPIO descriptors
are used")
be reverted?
This fixed spidev to deal with SPI_CS_HIGH on gpiod.
But after our fix, its behaviour will probably be broken again.
Another candidate for revert is
commit ada9e3fcc175 ("spi: dw: Correct handling of native chipselect")
although I don't understand that code well enough to be sure.
Adding Charles Keepax.
next prev parent reply other threads:[~2020-11-11 16:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-06 15:07 [PATCH v1] spi: fix client driver breakages when using GPIO descriptors Sven Van Asbroeck
2020-11-09 14:25 ` Andy Shevchenko
2020-11-09 14:41 ` Sven Van Asbroeck
2020-11-11 1:05 ` Linus Walleij
2020-11-11 12:33 ` Mark Brown
2020-11-11 13:36 ` Linus Walleij
2020-11-16 21:06 ` Mark Brown
2020-11-18 1:03 ` Linus Walleij
2020-11-18 11:40 ` Mark Brown
2020-11-24 15:21 ` Linus Walleij
2020-11-24 16:40 ` Mark Brown
2020-11-25 9:19 ` Grant Likely
2020-11-25 9:17 ` Grant Likely
2020-11-11 1:08 ` Linus Walleij
2020-11-11 15:48 ` Mark Brown
2020-11-11 16:24 ` Sven Van Asbroeck [this message]
2020-11-11 16:32 ` Mark Brown
2020-11-12 11:41 ` Charles Keepax
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=CAGngYiVAdPSCEQm5pJdFQ+3VpwNH1vGD6rPNK1_SQK3Uvfbt5A@mail.gmail.com \
--to=thesven73@gmail.com \
--cc=broonie@kernel.org \
--cc=ckeepax@opensource.cirrus.com \
--cc=jonathan.cameron@huawei.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=z.han@kunbus.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).