linux-spi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-spi@vger.kernel.org
Subject: [GIT PULL] SPI fixes for v5.5
Date: Tue, 17 Dec 2019 12:19:32 +0000	[thread overview]
Message-ID: <20191217121932.GD4755@sirena.org.uk> (raw)

[-- Attachment #1: Type: text/plain, Size: 2467 bytes --]

The following changes since commit ffa119f7c42d29be2dd759bb18cc4d1f45804c6b:

  dt-bindings: spi: Convert stm32 QSPI bindings to json-schema (2019-11-22 19:54:02 +0000)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git tags/spi-fix-v5.5-rc2

for you to fetch changes up to 63aa6a692595d47a0785297b481072086b9272d2:

  spi: fsl: use platform_get_irq() instead of of_irq_to_resource() (2019-12-16 11:54:55 +0000)

----------------------------------------------------------------
spi: Fixes for v5.5

A relatively large set of fixes here, the biggest part of it is for
fallout from the GPIO descriptor rework that affected several of the
devices with usable native chip select support.  There's also some new
PCI IDs for Intel Jasper Lake devices.

The conversion to platform_get_irq() in the fsl driver is an incremental
fix for build errors introduced on SPARC by the earlier fix for error
handling in probe in that driver.

----------------------------------------------------------------
Charles Keepax (2):
      spi: cadence: Correct handling of native chipselect
      spi: dw: Correct handling of native chipselect

Christophe Leroy (2):
      spi: fsl: don't map irq during probe
      spi: fsl: use platform_get_irq() instead of of_irq_to_resource()

Chuhong Yuan (1):
      spi: spi-cavium-thunderx: Add missing pci_release_regions()

Huanpeng Xin (1):
      spi: sprd: Fix the incorrect SPI register

Jarkko Nikula (1):
      spi: pxa2xx: Add support for Intel Jasper Lake

Linus Walleij (3):
      spi: fsl: Fix GPIO descriptor support
      gpio: Handle counting of Freescale chipselects
      spi: fsl: Handle the single hardwired chipselect case

Michael Walle (1):
      spi: nxp-fspi: Ensure width is respected in spi-mem operations

Vignesh Raghavendra (1):
      spi: spi-ti-qspi: Fix a bug when accessing non default CS

YueHaibing (1):
      gpiolib: of: Make of_gpio_spi_cs_get_count static

 drivers/gpio/gpiolib-of.c         | 27 +++++++++++++++++++++++++++
 drivers/spi/spi-cadence.c         |  6 +++---
 drivers/spi/spi-cavium-thunderx.c |  2 ++
 drivers/spi/spi-dw.c              |  5 +++--
 drivers/spi/spi-fsl-spi.c         | 22 ++++++++++++++++------
 drivers/spi/spi-nxp-fspi.c        |  2 +-
 drivers/spi/spi-pxa2xx.c          |  4 ++++
 drivers/spi/spi-sprd.c            |  2 +-
 drivers/spi/spi-ti-qspi.c         |  6 +++++-
 9 files changed, 62 insertions(+), 14 deletions(-)

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2019-12-17 12:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-17 12:19 Mark Brown [this message]
2019-12-17 21:15 ` [GIT PULL] SPI fixes for v5.5 pr-tracker-bot
2020-01-06 13:12 [GIT PULL] spi " Mark Brown
2020-01-06 21:05 ` pr-tracker-bot

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=20191217121932.GD4755@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=torvalds@linux-foundation.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).