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 7/7] i.MX defconfig update for 5.4
Date: Sun, 25 Aug 2019 17:32:37 +0200 [thread overview]
Message-ID: <20190825153237.28829-7-shawnguo@kernel.org> (raw)
In-Reply-To: <20190825153237.28829-1-shawnguo@kernel.org>
The following changes since commit 5f9e832c137075045d15cd6899ab0505cfb2ca4b:
Linus 5.3-rc1 (2019-07-21 14:05:38 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux.git tags/imx-defconfig-5.4
for you to fetch changes up to cd1b1264632a3fe739016843005e49e42c60be55:
arm64: defconfig: CONFIG_DRM_ETNAVIV=m (2019-08-03 17:15:37 +0200)
----------------------------------------------------------------
i.MX defconfig update for 5.4:
- Enable pinctrl and clock driver support for i.MX8MN SoC.
- Enable SDMA support for i.MX8MQ and i.MX8MM SoC, including
FW_LOADER_USER_HELPER and FW_LOADER_USER_HELPER_FALLBACK to support
SDMA firmware loading via udev.
- Enable module build of i.MX8 DDR PMU driver and ETNAVIV GPU driver.
- Enable module build of OV5645 camera driver in imx_v6_v7_defconfig.
----------------------------------------------------------------
Anson Huang (2):
arm64: defconfig: Select CONFIG_PINCTRL_IMX8MN by default
arm64: defconfig: Select CONFIG_CLK_IMX8MN by default
Christian Gmeiner (1):
arm64: defconfig: CONFIG_DRM_ETNAVIV=m
Fabio Estevam (1):
ARM: imx_v6_v7_defconfig: Select the OV5645 camera driver
Leonard Crestez (1):
arm64: defconfig: Build imx8 ddr pmu as module
Robin Gong (1):
arm64: defconfig: Enable SDMA on i.mx8mq/8mm
arch/arm/configs/imx_v6_v7_defconfig | 1 +
arch/arm64/configs/defconfig | 7 +++++++
2 files changed, 8 insertions(+)
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-08-25 15:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-25 15:32 [GIT PULL 1/7] i.MX drivers update for 5.4 Shawn Guo
2019-08-25 15:32 ` [GIT PULL 2/7] i.MX SoC changes " Shawn Guo
2019-09-03 12:26 ` Arnd Bergmann
2019-08-25 15:32 ` [GIT PULL 3/7] i.MX DT bindings update " Shawn Guo
2019-09-03 14:04 ` Arnd Bergmann
2019-08-25 15:32 ` [GIT PULL 4/7] i.MX device tree update with new clocks Shawn Guo
2019-09-03 14:08 ` Arnd Bergmann
2019-08-25 15:32 ` [GIT PULL 5/7] i.MX arm32 device tree changes for 5.4 Shawn Guo
2019-09-03 14:10 ` Arnd Bergmann
2019-08-25 15:32 ` [GIT PULL 6/7] i.MX arm64 device tree update " Shawn Guo
2019-09-03 14:12 ` Arnd Bergmann
2019-08-25 15:32 ` Shawn Guo [this message]
2019-09-03 17:00 ` [GIT PULL 7/7] i.MX defconfig " Arnd Bergmann
2019-09-03 20:58 ` [GIT PULL 1/7] i.MX drivers " Arnd Bergmann
2019-09-11 1:28 ` 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=20190825153237.28829-7-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).