From: Jay Fang <f.fangjian@huawei.com>
To: <broonie@kernel.org>, <linus.walleij@linaro.org>
Cc: <linux-spi@vger.kernel.org>, <linux-gpio@vger.kernel.org>,
<linuxarm@huawei.com>, <huangdaode@huawei.com>,
<tangzihao1@hisilicon.com>
Subject: [PATCH 0/2] spi: Correct CS GPIOs polarity when using GPIO descriptors
Date: Thu, 6 May 2021 11:00:15 +0800 [thread overview]
Message-ID: <1620270017-52643-1-git-send-email-f.fangjian@huawei.com> (raw)
This series introduces a generic implementation to solve the conflict
between the 'cs-gpios' flags and the optional SPI slaves flags. So we
don't need to add two similar quirks separately for DT and ACPI.
Jay Fang (2):
spi: Correct CS GPIOs polarity when using GPIO descriptors
Revert "gpio: of: Handle SPI chipselect legacy bindings"
drivers/gpio/gpiolib-of.c | 51 ++---------------------------------------------
drivers/spi/spi.c | 22 ++++++++++++++++++--
2 files changed, 22 insertions(+), 51 deletions(-)
--
2.7.4
next reply other threads:[~2021-05-06 3:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-06 3:00 Jay Fang [this message]
2021-05-06 3:00 ` [PATCH 1/2] spi: Correct CS GPIOs polarity when using GPIO descriptors Jay Fang
2021-05-06 3:00 ` [PATCH 2/2] Revert "gpio: of: Handle SPI chipselect legacy bindings" Jay Fang
[not found] ` <CAHp75Vfr8t9UVqVn6hLSN6Mi3=iNAn612eE-qKq9HfrwNhpg3Q@mail.gmail.com>
[not found] ` <CAHp75Vei0QGaKiq5Nai7Gsa=jcMSipaXV_6qZbBy=f0OrN=DHQ@mail.gmail.com>
2021-05-06 9:11 ` [PATCH 0/2] spi: Correct CS GPIOs polarity when using GPIO descriptors Jay Fang
2021-05-06 9:44 ` Andy Shevchenko
2021-05-06 9:51 ` Andy Shevchenko
2021-05-06 11:06 ` Linus Walleij
2021-05-06 11:24 ` Mark Brown
[not found] ` <CAHp75Veoqnd3Hgzq8DAz-_=QxMt-+r608dkzPp67YA5eitLJNw@mail.gmail.com>
2021-05-06 11:34 ` Mark Brown
2021-05-06 12:17 ` Andy Shevchenko
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=1620270017-52643-1-git-send-email-f.fangjian@huawei.com \
--to=f.fangjian@huawei.com \
--cc=broonie@kernel.org \
--cc=huangdaode@huawei.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=tangzihao1@hisilicon.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).