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 change for 5.11
Date: Wed, 2 Dec 2020 22:27:12 +0800 [thread overview]
Message-ID: <20201202142717.9262-1-shawnguo@kernel.org> (raw)
The following changes since commit 3650b228f83adda7e5ee532e2b90429c03f7b9ec:
Linux 5.10-rc1 (2020-10-25 15:14:11 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux.git tags/imx-drivers-5.11
for you to fetch changes up to e00e70a4dae4cae026d43f2f05ba46a19c4ef22d:
firmware: imx: scu-pd: Add some power domains support for i.MX8qxp MIPI1 subsystem (2020-11-30 17:47:18 +0800)
----------------------------------------------------------------
i.MX drivers change for 5.11:
- A series from Daniel Baluta to update imx-dsp driver and export
functions for on demand channel request/free.
- A number of patches to add power domains for i.MX8qxp DC0, LVDS1,
MIPI1 and JPEG subsystems.
- Add dummy functions for i.MX firmware drivers to avoid build failure
seen with COMPILE_TEST.
----------------------------------------------------------------
Daniel Baluta (3):
firmware: imx: Introduce imx_dsp_setup_channels
firmware: imx: Save channel name for further use
firmware: imx-dsp: Export functions to request/free channels
Liu Ying (3):
firmware: imx: scu-pd: Add video0/1 power domains support for i.MX8qxp DC0 subsystem
firmware: imx: scu-pd: Add main power domain support for i.MX8qxp LVDS1 subsystem
firmware: imx: scu-pd: Add some power domains support for i.MX8qxp MIPI1 subsystem
Mirela Rabulea (1):
firmware: imx: scu-pd: Add power domains for imx-jpeg
Peng Fan (1):
firmware: imx: add dummy functions
drivers/firmware/imx/imx-dsp.c | 72 ++++++++++++++++++++++++++---------
drivers/firmware/imx/scu-pd.c | 12 ++++++
include/linux/firmware/imx/dsp.h | 10 +++++
include/linux/firmware/imx/ipc.h | 13 +++++++
include/linux/firmware/imx/sci.h | 27 +++++++++++++
include/linux/firmware/imx/svc/misc.h | 19 +++++++++
6 files changed, 135 insertions(+), 18 deletions(-)
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2020-12-02 14:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-02 14:27 Shawn Guo [this message]
2020-12-02 14:27 ` [GIT PULL 2/6] i.MX SoC update for 5.11 Shawn Guo
2020-12-09 16:41 ` Arnd Bergmann
2020-12-02 14:27 ` [GIT PULL 3/6] i.MX DT bindings " Shawn Guo
2020-12-08 23:09 ` Arnd Bergmann
2020-12-02 14:27 ` [GIT PULL 4/6] i.MX device tree " Shawn Guo
2020-12-08 23:09 ` Arnd Bergmann
2020-12-02 14:27 ` [GIT PULL 5/6] i.MX arm64 device tree change " Shawn Guo
2020-12-08 23:09 ` Arnd Bergmann
2020-12-02 14:27 ` [GIT PULL 6/6] i.MX defconfig update " Shawn Guo
2020-12-08 16:34 ` Arnd Bergmann
2020-12-08 23:31 ` [GIT PULL 1/6] i.MX drivers change " Arnd Bergmann
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=20201202142717.9262-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).