From: s.hauer@pengutronix.de (Sascha Hauer)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/4] spi: imx: GPIO based chip selects should not be required
Date: Mon, 6 Nov 2017 08:32:46 +0100 [thread overview]
Message-ID: <20171106073246.efcz7r2vnymz3me7@pengutronix.de> (raw)
In-Reply-To: <1509736735.5473.87.camel@impinj.com>
On Fri, Nov 03, 2017 at 07:18:56PM +0000, Trent Piepho wrote:
> On Fri, 2017-11-03 at 18:37 +0000, Mark Brown wrote:
> > On Fri, Nov 03, 2017 at 05:53:59PM +0000, Trent Piepho wrote:
> >
> > > Just to be clear, one doesn't need to use GPIOs with the driver as is.
> > > But the bindings to do that are non-standard and these patches make the
> > > driver follow the standard. (and don't break anyone).
> >
> > If there are non-standard bindings then mark them as deprecated. I
> > can't immediately find *any* binding documentation for this controller.
> > The last commit looks like it was more attempting to work round broken
> > board bindings and do something sensible than add a new binding, at
> > least that's what I remember my sense of it being.
>
> The non-standard part is needing to add cs-gpios = <0> to get a native
> chip select when that is documented as being optional. It doesn't
> follow the spec. It doesn't match other drivers (and dw-spi is equally
> as broken in the same manner, probably others too) that do follow the
> spec.
>
> > If the hardware is as broken as these controllers always were in the
> > past and there are workarounds which work in all practical situations
> > (AFAIK all the relevant SoCs permit GPIO usage on the chip select pins)
>
> Comments in the driver indicate that some SoCs do not allow GPIO usage
> on all chip select pins.
Which comments do you mean? I remember there were comments, but I can't
find any in the driver.
The only SoC which has dedicated SPI CS pins which can't be configured
as GPIOs is the i.MX31. Unless you have an i.MX31 you shouldn't be
forced to use native chip selects.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2017-11-06 7:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-27 1:08 [PATCH v2 0/4] Fix for imx-spi CS GPIOs Trent Piepho
2017-10-27 1:08 ` [PATCH v2 1/4] spi: imx: GPIO based chip selects should not be required Trent Piepho
2017-10-31 11:19 ` Mark Brown
2017-10-31 16:57 ` Trent Piepho
2017-11-02 15:14 ` Mark Brown
2017-11-03 17:53 ` Trent Piepho
2017-11-03 18:37 ` Mark Brown
2017-11-03 19:18 ` Trent Piepho
2017-11-03 19:36 ` Mark Brown
2017-11-03 20:09 ` Trent Piepho
2017-11-03 20:11 ` Mark Brown
2017-11-06 7:32 ` Sascha Hauer [this message]
2017-11-06 19:20 ` Trent Piepho
2017-10-27 1:08 ` [PATCH v2 2/4] spi: imx: Fix failure path leak on GPIO request error Trent Piepho
2017-10-27 1:08 ` [PATCH v2 3/4] spi: imx: Don't require platform data chipselect array Trent Piepho
2017-10-27 11:14 ` Oleksij Rempel
2017-10-27 1:08 ` [PATCH v2 4/4] ARM: imx: Update spi_imx platform data to reflect current state Trent Piepho
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=20171106073246.efcz7r2vnymz3me7@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.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).