From: Trent Piepho <tpiepho-cgc2CodaaHDQT0dZR+AlfA@public.gmane.org>
To: linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Cc: Trent Piepho <tpiepho-cgc2CodaaHDQT0dZR+AlfA@public.gmane.org>
Subject: [PATCH v3 0/4] Fix for imx-spi CS GPIOs
Date: Tue, 31 Oct 2017 12:49:03 -0700 [thread overview]
Message-ID: <20171031194907.29108-1-tpiepho@impinj.com> (raw)
This fixes a bug where GPIO based chip selects must be specified in the OF
node for spi-imx when they should be optional.
Fixes a regression in the platform data of imx31moboard.
Clean up of some old platform data based spi-imx users.
Changes from V1:
* Collected reviewed bys.
* Minor change to coding style in one patch.
Changes from V2:
* Reverted minor coding change from V2, it was right to begin with
* Have imx-spi also honor "num-cs" property
* Leak of spi_bitbang on failure needed to be fixed differently
* Port to linux-next, which has other changes to spi-imx
Trent Piepho (4):
spi: imx: GPIO based chip selects should not be required
spi: imx: Fix failure path leak on GPIO request error
spi: imx: Don't require platform data chipselect array
ARM: imx: Update spi_imx platform data to reflect current state
arch/arm/mach-imx/mach-mx31_3ds.c | 18 ++----------------
arch/arm/mach-imx/mach-mx31lilly.c | 12 ++----------
arch/arm/mach-imx/mach-mx31lite.c | 16 ++--------------
arch/arm/mach-imx/mach-mx31moboard.c | 17 +++--------------
arch/arm/mach-imx/mach-pcm037_eet.c | 5 +----
drivers/spi/spi-imx.c | 36 ++++++++++++++++++++---------------
include/linux/platform_data/spi-imx.h | 29 ++++++++++++++++------------
7 files changed, 48 insertions(+), 85 deletions(-)
--
2.14.3
--
To unsubscribe from this list: send the line "unsubscribe linux-spi" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2017-10-31 19:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-31 19:49 Trent Piepho [this message]
[not found] ` <20171031194907.29108-1-tpiepho-cgc2CodaaHDQT0dZR+AlfA@public.gmane.org>
2017-10-31 19:49 ` [PATCH v3 1/4] spi: imx: GPIO based chip selects should not be required Trent Piepho
2017-10-31 19:49 ` [PATCH v3 2/4] spi: imx: Fix failure path leak on GPIO request error Trent Piepho
[not found] ` <20171031194907.29108-3-tpiepho-cgc2CodaaHDQT0dZR+AlfA@public.gmane.org>
2017-10-31 20:01 ` Mark Brown
2017-11-10 21:30 ` Applied "spi: imx: Fix failure path leak on GPIO request error" to the spi tree Mark Brown
2017-10-31 19:49 ` [PATCH v3 3/4] spi: imx: Don't require platform data chipselect array Trent Piepho
[not found] ` <20171031194907.29108-4-tpiepho-cgc2CodaaHDQT0dZR+AlfA@public.gmane.org>
2017-11-10 21:30 ` Applied "spi: imx: Don't require platform data chipselect array" to the spi tree Mark Brown
2017-10-31 19:49 ` [PATCH v3 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=20171031194907.29108-1-tpiepho@impinj.com \
--to=tpiepho-cgc2codaahdqt0dzr+alfa@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.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).