From: Mark Brown <broonie@kernel.org>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Jay Fang <f.fangjian@huawei.com>,
"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 12:34:30 +0100 [thread overview]
Message-ID: <20210506113430.GB4642@sirena.org.uk> (raw)
In-Reply-To: <CAHp75Veoqnd3Hgzq8DAz-_=QxMt-+r608dkzPp67YA5eitLJNw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 518 bytes --]
On Thu, May 06, 2021 at 02:24:17PM +0300, Andy Shevchenko wrote:
> On Thursday, May 6, 2021, Linus Walleij <linus.walleij@linaro.org> wrote:
> > Curious that ACPI has SPI CS as always active high,
> Here I didn’t get what exactly you are pointing out. GPIOs are active high,
> due to historical reasons. Otherwise SPI CS depends on the actual hardware
> and may be (most of the cases?) active low.
SPI chip selects are almost always active low - the signal is often
written nCS or /CS for that reason.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-05-06 11:35 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 ` [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 [this message]
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=20210506113430.GB4642@sirena.org.uk \
--to=broonie@kernel.org \
--cc=andy.shevchenko@gmail.com \
--cc=f.fangjian@huawei.com \
--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