From: Jay Fang <f.fangjian@huawei.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: "broonie@kernel.org" <broonie@kernel.org>,
"linus.walleij@linaro.org" <linus.walleij@linaro.org>,
"linux-spi@vger.kernel.org" <linux-spi@vger.kernel.org>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
"linuxarm@huawei.com" <linuxarm@huawei.com>,
"huangdaode@huawei.com" <huangdaode@huawei.com>,
"tangzihao1@hisilicon.com" <tangzihao1@hisilicon.com>
Subject: Re: [PATCH 0/2] spi: Correct CS GPIOs polarity when using GPIO descriptors
Date: Thu, 6 May 2021 17:11:31 +0800 [thread overview]
Message-ID: <e919da77-a664-d78b-2c47-cc9ba8745a72@huawei.com> (raw)
In-Reply-To: <CAHp75Vei0QGaKiq5Nai7Gsa=jcMSipaXV_6qZbBy=f0OrN=DHQ@mail.gmail.com>
On 2021/5/6 16:14, Andy Shevchenko wrote:
>
>
> On Thursday, May 6, 2021, Andy Shevchenko <andy.shevchenko@gmail.com <mailto:andy.shevchenko@gmail.com>> wrote:
>
>
>
> On Thursday, May 6, 2021, Jay Fang <f.fangjian@huawei.com <mailto:f.fangjian@huawei.com>> wrote:
>
> 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.
>
>
> NAK. There is a patch against documentation that clarifies polarity of GPIO for ACPI. I have a fix for that to use generic implementation of CS GPIOs .
Thanks. Has the Fix patch been merged ? Commit Id ?
>
>
> https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git/commit/?h=bleeding-edge&id=ec3576eac11d66a388b6cba6a7cfb3b45039a712 <https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git/commit/?h=bleeding-edge&id=ec3576eac11d66a388b6cba6a7cfb3b45039a712>
>
>
> If your ACPI table uses GPIO CS with polarity low (assumes _DSD() is involved), this is a bug. Fix firmware or do a quirk specific for your platform.
>
>
>
>
>
> 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
>
>
>
> --
> With Best Regards,
> Andy Shevchenko
>
>
>
>
> --
> With Best Regards,
> Andy Shevchenko
>
>
next prev parent reply other threads:[~2021-05-06 9:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-06 3:00 [PATCH 0/2] spi: Correct CS GPIOs polarity when using GPIO descriptors Jay Fang
2021-05-06 3:00 ` [PATCH 1/2] " 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 ` Jay Fang [this message]
2021-05-06 9:44 ` [PATCH 0/2] spi: Correct CS GPIOs polarity when using GPIO descriptors 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=e919da77-a664-d78b-2c47-cc9ba8745a72@huawei.com \
--to=f.fangjian@huawei.com \
--cc=andy.shevchenko@gmail.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