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: Shawn Guo <shawnguo@kernel.org>, 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 1/6] i.MX drivers update for 5.8
Date: Sat, 23 May 2020 11:25:11 +0800	[thread overview]
Message-ID: <20200523032516.11016-1-shawnguo@kernel.org> (raw)

The following changes since commit 8f3d9f354286745c751374f5f1fcafee6b3f3136:

  Linux 5.7-rc1 (2020-04-12 12:35:55 -0700)

are available in the Git repository at:

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

for you to fetch changes up to 89f12d6509bff004852c51cb713a439a86816b24:

  firmware: imx: scu: Fix possible memory leak in imx_scu_probe() (2020-05-20 11:33:08 +0800)

----------------------------------------------------------------
i.MX drivers update for 5.8:

- Optimize imx-scu driver to use one TX and one RX instead of four for
  talking to SCU.
- Fix one possible message header corruption where the response is
  longer than the request.
- Move System Control defines into dt-bindings header, so that DT can
  use them as well.
- A couple of small fixups.

----------------------------------------------------------------
Anson Huang (1):
      soc: imx8m: No need to put node when of_find_compatible_node() failed

Dong Aisheng (2):
      dt-bindings: firmware: imx: Move system control into dt-binding headfile
      dt-bindings: firmware: imx: Add more system controls and PM clock types

Franck LENORMAND (1):
      firmware: imx: scu: Fix corruption of header

Peng Fan (1):
      firmware: imx-scu: Support one TX and one RX

Wei Yongjun (1):
      firmware: imx: scu: Fix possible memory leak in imx_scu_probe()

 drivers/firmware/imx/imx-scu.c          | 64 ++++++++++++++++++-------
 drivers/soc/imx/soc-imx8m.c             |  7 ++-
 drivers/thermal/imx_sc_thermal.c        |  2 +-
 include/dt-bindings/firmware/imx/rsrc.h | 84 +++++++++++++++++++++++++++++++++
 include/linux/firmware/imx/sci.h        |  1 -
 include/linux/firmware/imx/types.h      | 65 -------------------------
 6 files changed, 136 insertions(+), 87 deletions(-)
 delete mode 100644 include/linux/firmware/imx/types.h

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

             reply	other threads:[~2020-05-23  3:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-23  3:25 Shawn Guo [this message]
2020-05-23  3:25 ` [GIT PULL 2/6] i.MX SoC changes for 5.8 Shawn Guo
2020-05-23  3:25 ` [GIT PULL 3/6] i.MX bindings change " Shawn Guo
2020-05-23  3:25 ` [GIT PULL 4/6] i.MX device tree changes " Shawn Guo
2020-05-23  3:25 ` [GIT PULL 5/6] i.MX arm64 " Shawn Guo
2020-05-23  3:25 ` [GIT PULL 6/6] i.MX defconfig update " Shawn Guo

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=20200523032516.11016-1-shawnguo@kernel.org \
    --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).