From: Shawn Guo <shawnguo@kernel.org>
To: arm@kernel.org
Cc: Fabio Estevam <fabio.estevam@nxp.com>,
Shawn Guo <shawnguo@kernel.org>,
linux-imx@nxp.com, kernel@pengutronix.de,
linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 7/7] i.MX defconfig update for 4.21
Date: Mon, 10 Dec 2018 15:46:38 +0800 [thread overview]
Message-ID: <20181210074638.27873-7-shawnguo@kernel.org> (raw)
In-Reply-To: <20181210074638.27873-1-shawnguo@kernel.org>
The following changes since commit 651022382c7f8da46cb4872a545ee1da6d097d2a:
Linux 4.20-rc1 (2018-11-04 15:37:52 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux.git tags/imx-defconfig-4.21
for you to fetch changes up to bb9c90ab4eddf83e1aa041498f65b8bf8be6802f:
ARM: imx_v6_v7_defconfig: add imx7ulp support (2018-12-06 22:55:20 +0800)
----------------------------------------------------------------
i.MX defconfig update for 4.21:
- Enable build of i.MX7ULP SoC support.
- Enable Goodix touchscreen driver which is needed by ConnectCore 6UL
SBC Pro (ccimx6ulsbcpro) board support.
- Enable USB_ANNOUNCE_NEW_DEVICES to help USB issue debugging and
BT_BNEP to support network over bluetooth.
- Remove explicit ARM_UNWIND disabling as it's selected by ARM EABI
support.
- Enable DA9063 PMIC for emtrion i.MX6 boards support.
- Enable driver support for Pixel Pipeline (PXP) and DCP crypto block
which are found on i.MX6 and i.MX7 SoCs.
----------------------------------------------------------------
A.s. Dong (1):
ARM: imx_v6_v7_defconfig: add imx7ulp support
Alex Gonzalez (1):
ARM: imx_v6_v7_defconfig: Select TOUCHSCREEN_GOODIX
Andreas Müller (2):
ARM: imx_v6_v7_defconfig: Enable BT_BNEP
ARM: imx_v6_v7_defconfig: Enable USB_ANNOUNCE_NEW_DEVICES
Fabio Estevam (1):
ARM: imx_v6_v7_defconfig: Select the PXP driver
Jan Tuerk (1):
ARM: imx_v6_v7_defconfig: Enable DA9063 PMIC support
Leonard Crestez (1):
ARM: imx_v6_v7_defconfig: Enable CRYPTO_DEV_MXS_DCP
Otavio Salvador (1):
ARM: imx_v6_v7_defconfig: Remove explicit ARM_UNWIND disable
arch/arm/configs/imx_v6_v7_defconfig | 10 +++++++++-
1 file changed, 9 insertions(+), 1 deletion(-)
_______________________________________________
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:[~2018-12-10 7:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-10 7:46 [GIT PULL 1/7] i.MX drivers changes for 4.21 Shawn Guo
2018-12-10 7:46 ` [GIT PULL 2/7] i.MX SoC " Shawn Guo
2018-12-11 2:51 ` Shawn Guo
2018-12-12 21:53 ` Olof Johansson
2018-12-10 7:46 ` [GIT PULL 3/7] i.MX device tree update " Shawn Guo
2018-12-12 20:55 ` Olof Johansson
2018-12-10 7:46 ` [GIT PULL 4/7] i.MX7D PICO boards " Shawn Guo
2018-12-12 20:56 ` Olof Johansson
2018-12-10 7:46 ` [GIT PULL 5/7] i.MX7ULP device tree " Shawn Guo
2018-12-12 20:58 ` Olof Johansson
2018-12-10 7:46 ` [GIT PULL 6/7] Freescale arm64 device tree update " Shawn Guo
2018-12-12 21:00 ` Olof Johansson
2018-12-10 7:46 ` Shawn Guo [this message]
2018-12-12 21:47 ` [GIT PULL 7/7] i.MX defconfig " Olof Johansson
2018-12-12 21:33 ` [GIT PULL 1/7] i.MX drivers changes " 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=20181210074638.27873-7-shawnguo@kernel.org \
--to=shawnguo@kernel.org \
--cc=arm@kernel.org \
--cc=fabio.estevam@nxp.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
/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.