From: tpiepho@impinj•com (Trent Piepho)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH 4/4] ARM: imx: Update spi_imx platform data to reflect current state
Date: Wed, 18 Oct 2017 17:50:30 +0000 [thread overview]
Message-ID: <1508349029.87493.8.camel@impinj.com> (raw)
In-Reply-To: <20171018021709.GD18810@dragon>
On Wed, 2017-10-18 at 10:17 +0800, Shawn Guo wrote:
> On Fri, Oct 13, 2017 at 12:54:10PM -0700, Trent Piepho wrote:
> >
> > If a board uses all native chip selects, then it's not necessary to
> > specify a chip select array at all, as all native is the default (this is
> > how device-tree configured SPI masters work too). Most of the spi-imx
> > platform data users have their chip select arrays removed by this patch.
> >
> >
> Does this patch have any dependency on others in this series, or can it
> be sent via arm-soc tree independently?
It needs patch 1 and 3 in the series. Currently supplying cs gpios is
mandatory for both platform data and DT based systems using spi-imx.
The latter is a bug, as the DT binding clearly makes cs-gpios optional
and other drivers do not require it. I figured I might as well clean
up the platform data while I fixed that bug and came across the
imx31moboard bug in that process.
prev parent reply other threads:[~2017-10-18 17:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-13 19:54 [PATCH 1/4] spi: imx: GPIO based chip selects should not be required Trent Piepho
2017-10-13 19:54 ` [PATCH 2/4] spi: imx: Fix failure path leak on GPIO request error Trent Piepho
2017-10-19 10:27 ` Oleksij Rempel
2017-10-13 19:54 ` [PATCH 3/4] spi: imx: Don't require platform data chipselect array Trent Piepho
2017-10-18 9:02 ` Julien Thierry
2017-10-18 17:30 ` Trent Piepho
2017-10-30 23:47 ` Trent Piepho
2017-10-13 19:54 ` [PATCH 4/4] ARM: imx: Update spi_imx platform data to reflect current state Trent Piepho
2017-10-15 23:34 ` Greg Ungerer
2017-10-18 2:17 ` Shawn Guo
2017-10-18 17:50 ` Trent Piepho [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=1508349029.87493.8.camel@impinj.com \
--to=tpiepho@impinj$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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