linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Shawn Guo <shawnguo@kernel.org>
To: soc@kernel.org, arm@kernel.org
Cc: Stefan Agner <stefan@agner.ch>, Li Yang <leoyang.li@nxp.com>,
	linux-imx@nxp.com, kernel@pengutronix.de,
	Fabio Estevam <festevam@gmail.com>,
	linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] i.MX fixes for 5.8
Date: Wed, 24 Jun 2020 19:17:26 +0800	[thread overview]
Message-ID: <20200624111725.GA24312@dragon> (raw)

The following changes since commit b3a9e3b9622ae10064826dccb4f7a52bd88c7407:

  Linux 5.8-rc1 (2020-06-14 12:45:04 -0700)

are available in the Git repository at:

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

for you to fetch changes up to a721321446432c3899aeca16cc6ddc30422b7f74:

  soc: imx8m: fix build warning (2020-06-24 14:33:28 +0800)

----------------------------------------------------------------
i.MX fixes for 5.8:

- Fix LDO1 and LDO2 voltage range for a couple of i.MX8M board device
  trees.
- Fix i.MX8MP UID fuse offset in i.MX8M SoC driver.
- Fix watchdog configuration in imx6ul-kontron device tree.
- Fix one build warning seen on building soc-imx8m driver with
  x86_64-randconfig.
- Add missing put_device() call for a couple of mach-imx PM functions.

----------------------------------------------------------------
Adam Ford (1):
      arm64: dts: imx8mm-beacon: Fix voltages on LDO1 and LDO2

Anson Huang (1):
      soc: imx8m: Correct i.MX8MP UID fuse offset

Frieder Schrempf (2):
      ARM: dts: imx6ul-kontron: Move watchdog from Kontron i.MX6UL/ULL board to SoM
      ARM: dts: imx6ul-kontron: Change WDOG_ANY signal from push-pull to open-drain

Peng Fan (1):
      soc: imx8m: fix build warning

Robin Gong (2):
      arm64: dts: imx8mm-evk: correct ldo1/ldo2 voltage range
      arm64: dts: imx8mn-ddr4-evk: correct ldo1/ldo2 voltage range

yu kuai (2):
      ARM: imx5: add missing put_device() call in imx_suspend_alloc_ocram()
      ARM: imx6: add missing put_device() call in imx6q_suspend_init()

 arch/arm/boot/dts/imx6ul-kontron-n6x1x-s.dtsi          | 13 -------------
 arch/arm/boot/dts/imx6ul-kontron-n6x1x-som-common.dtsi | 13 +++++++++++++
 arch/arm/mach-imx/pm-imx5.c                            |  6 ++++--
 arch/arm/mach-imx/pm-imx6.c                            | 10 ++++++----
 arch/arm64/boot/dts/freescale/imx8mm-beacon-som.dtsi   |  4 ++--
 arch/arm64/boot/dts/freescale/imx8mm-evk.dts           |  4 ++--
 arch/arm64/boot/dts/freescale/imx8mn-ddr4-evk.dts      |  4 ++--
 drivers/soc/imx/soc-imx8m.c                            | 10 +++++++---
 8 files changed, 36 insertions(+), 28 deletions(-)

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

                 reply	other threads:[~2020-06-24 11:19 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20200624111725.GA24312@dragon \
    --to=shawnguo@kernel.org \
    --cc=arm@kernel.org \
    --cc=festevam@gmail.com \
    --cc=kernel@pengutronix.de \
    --cc=leoyang.li@nxp.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-imx@nxp.com \
    --cc=soc@kernel.org \
    --cc=stefan@agner.ch \
    /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).