From: Mark Brown <broonie@kernel.org>
To: Fabio Estevam <festevam@gmail.com>
Cc: Matthias Schiffer <matthias.schiffer@ew.tq-group.com>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
NXP Linux Team <linux-imx@nxp.com>,
linux-spi <linux-spi@vger.kernel.org>,
"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] spi-imx: remove num-cs support, set num_chipselect to 4
Date: Fri, 4 Sep 2020 14:10:14 +0100 [thread overview]
Message-ID: <20200904131014.GF4625@sirena.org.uk> (raw)
In-Reply-To: <CAOMZO5DGHoG_8X+fbrGCHR4g=sGdEaF7bYrHbC_2T=aUnfTs8g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 355 bytes --]
On Fri, Sep 04, 2020 at 09:35:38AM -0300, Fabio Estevam wrote:
> On Thu, Sep 3, 2020 at 11:40 AM Matthias Schiffer
> > + master->num_chipselect = 4;
> On an imx6q-sabresd, which only has one SPI chip-select via GPIO, this
> makes the SPI core to understand that it has 4 chip selects.
We shouldn't do anything with the extra chip selects though?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2020-09-04 13:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-03 14:40 [PATCH] spi-imx: remove num-cs support, set num_chipselect to 4 Matthias Schiffer
2020-09-04 12:35 ` Fabio Estevam
2020-09-04 13:02 ` (EXT) " Matthias Schiffer
2020-09-04 13:57 ` Fabio Estevam
2020-09-04 14:34 ` (EXT) " Matthias Schiffer
2020-09-04 15:04 ` Mark Brown
2020-09-04 15:42 ` Fabio Estevam
2020-09-07 7:40 ` (EXT) " Matthias Schiffer
2020-09-13 14:15 ` Fabio Estevam
2020-09-04 13:10 ` Mark Brown [this message]
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=20200904131014.GF4625@sirena.org.uk \
--to=broonie@kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=matthias.schiffer@ew.tq-group.com \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@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).