All of lore.kernel.org
 help / color / mirror / Atom feed
From: shawnguo@kernel.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: i.MX fixes for 4.18
Date: Tue, 19 Jun 2018 16:14:06 +0800	[thread overview]
Message-ID: <20180619081405.GF16091@dragon> (raw)

The following changes since commit ce397d215ccd07b8ae3f71db689aedb85d56ab40:

  Linux 4.18-rc1 (2018-06-17 08:04:49 +0900)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux.git tags/imx-fixes-4.18

for you to fetch changes up to 1bcfe0564044be578841744faea1c2f46adc8178:

  ARM: dts: imx6sx: fix irq for pcie bridge (2018-06-19 14:39:36 +0800)

----------------------------------------------------------------
i.MX fixes for 4.18:
 - Fix i.MX6SX PCIe MSI interrupt number, so that MSI IRQs can be
   properly propagated to the upstream interrupt controller.
 - Fix GPCv2 MIPI/PCIe/USB_HSIC's PGC offset.  The values in Reference
   Manual are incorrect.
 - Correct SDMA setting for i.MX6Q SPI5 device to fix the issue, that
   the SPI controller RX FIFO was not empty after a DMA transfer, and
   the driver gets stuck in the next PIO transfer when reading one word
   more than expected.

----------------------------------------------------------------
Anson Huang (1):
      soc: imx: gpcv2: correct PGC offset

Oleksij Rempel (1):
      ARM: dts: imx6sx: fix irq for pcie bridge

Sean Nyekjaer (1):
      ARM: dts: imx6q: Use correct SDMA script for SPI5 core

 arch/arm/boot/dts/imx6q.dtsi  |  2 +-
 arch/arm/boot/dts/imx6sx.dtsi |  2 +-
 drivers/soc/imx/gpcv2.c       | 13 +++++++++----
 3 files changed, 11 insertions(+), 6 deletions(-)

             reply	other threads:[~2018-06-19  8:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-19  8:14 Shawn Guo [this message]
2018-06-23 17:17 ` i.MX fixes for 4.18 Olof Johansson

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=20180619081405.GF16091@dragon \
    --to=shawnguo@kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.