linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Olof Johansson <olof@lixom.net>
To: Shawn Guo <shawnguo@kernel.org>
Cc: Stefan Agner <stefan@agner.ch>, Li Yang <leoyang.li@nxp.com>,
	arm@kernel.org, linux-imx@nxp.com, kernel@pengutronix.de,
	Fabio Estevam <festevam@gmail.com>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL 7/7] i.MX defconfig changes for 5.3
Date: Tue, 25 Jun 2019 05:32:34 -0700	[thread overview]
Message-ID: <20190625123234.ytva26bkeyqevtwc@localhost> (raw)
In-Reply-To: <20190625075305.29082-7-shawnguo@kernel.org>

On Tue, Jun 25, 2019 at 03:53:05PM +0800, Shawn Guo wrote:
> Hi,
> 
> The change set is a little bigger than expected.  This is because that
> half of the changes were for 5.2, but unfortunately they missed the
> merge window.  So we have changes for two development cycles combined
> here.  Please pull, thanks!
> 
> Shawn
> 
> 
> The following changes since commit a188339ca5a396acc588e5851ed7e19f66b0ebd9:
> 
>   Linux 5.2-rc1 (2019-05-19 15:47:09 -0700)
> 
> are available in the Git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux.git tags/imx-defconfig-5.3
> 
> for you to fetch changes up to 8bbc2b3a7f80b61c05b87606c2acd82a62d304b0:
> 
>   arm64: defconfig: Enable CONFIG_KEYBOARD_SNVS_PWRKEY as module (2019-06-25 15:15:59 +0800)
> 
> ----------------------------------------------------------------
> i.MX defconfig changes for 5.3:
>  * imx_v6_v7_defconfig:
>    - PCF857X GPIO expander
>    - SIOX bus driver
>    - thermal statistics
>    - TPM PWM driver
>    - OV2680 camera driver
>    - SNVS LPGPR NVMEM driver
>    - i.MX DT based cpufreq driver
>  * arm64 defconfig built-in:
>    - i.MX8MM pinctrl and clock
>    - i.MX LPI2C driver
>    - ROHM_BD718XX PMIC
>    - OCOTP NVMEM support
>    - i.MX SCU based SoC bus driver
>  * arm64 defconfig modules:
>    - i.MX SPI driver
>    - i.MX system controller watchdog
>    - SNVS RTC driver
>    - ISL29018 light and proximity sensor driver
>    - MPL3115 pressure sensor driver
>    - i.MX8 DT based cpufreq support
>    - QorIQ Thermal Monitoring Unit driver
>    - SNVS power key driver
> 
> ----------------------------------------------------------------
> Abel Vesa (1):
>       arm64: defconfig: Enable RTC_DRV_SNVS
> 
> Adam Ford (1):
>       ARM: imx_v6_v7_defconfig: Add GPIO_PCF857X
> 
> Anson Huang (6):
>       arm64: defconfig: add support for i.MX system controller watchdog
>       ARM: imx_v6_v7_defconfig: Enable CONFIG_THERMAL_STATISTICS
>       ARM: imx_v6_v7_defconfig: Add TPM PWM support by default
>       arm64: defconfig: Enable CONFIG_QORIQ_THERMAL
>       arm64: defconfig: Add i.MX SCU SoC info driver

An SoC info driver shouldn't need to be =y, I think? It exports no in-kernel
interfaces, so it should do just fine as a module.


>       arm64: defconfig: Enable CONFIG_KEYBOARD_SNVS_PWRKEY as module
> 
> Fabio Estevam (3):
>       arm64: defconfig: Enable CONFIG_SPI_IMX
>       ARM: imx_v6_v7_defconfig: Enable the OV2680 camera driver
>       ARM: imx_v6_v7_defconfig: Select CONFIG_NVMEM_SNVS_LPGPR
> 
> Leonard Crestez (6):
>       arm64: defconfig: Enable imx8mm clk/pinctrl
>       arm64: defconfig: Enable lpi2c for imx8qxp and sensors
>       arm64: defconfig: Enable ROHM_BD718XX PMIC for imx8mm-evk
>       arm64: defconfig: NVMEM_IMX_OCOTP=y for imx8m

And why does this need to be =y? Patch doesn't say.

>       arm64: defconfig: ARM_IMX_CPUFREQ_DT=m
>       ARM: imx_v6_v7_defconfig: Enable CONFIG_ARM_IMX_CPUFREQ_DT
> 
> Peng Fan (1):
>       defconfig: arm64: enable i.MX8 SCU octop driver
> 
> Uwe Kleine-König (1):
>       ARM: imx_v6_v7_defconfig: Enable SIOX bus
> 
>  arch/arm/configs/imx_v6_v7_defconfig |  9 +++++++++
>  arch/arm64/configs/defconfig         | 17 +++++++++++++++++
>  2 files changed, 26 insertions(+)


Not merged until above is clarified.


Thanks!


-Olof


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

  reply	other threads:[~2019-06-25 13:07 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-25  7:52 [GIT PULL 1/7] i.MX drivers change for 5.3 Shawn Guo
2019-06-25  7:53 ` [GIT PULL 2/7] i.MX SoC changes " Shawn Guo
2019-06-25 12:52   ` Olof Johansson
2019-06-25  7:53 ` [GIT PULL 3/7] i.MX DT bindings update " Shawn Guo
2019-06-25 11:51   ` Olof Johansson
2019-06-25  7:53 ` [GIT PULL 4/7] i.MX DT changes with new clock " Shawn Guo
2019-06-25 11:52   ` Olof Johansson
2019-06-25  7:53 ` [GIT PULL 5/7] i.MX arm32 DT changes " Shawn Guo
2019-06-25 11:52   ` Olof Johansson
2019-06-25  7:53 ` [GIT PULL 6/7] i.MX arm64 " Shawn Guo
2019-06-25 11:53   ` Olof Johansson
2019-06-25  7:53 ` [GIT PULL 7/7] i.MX defconfig " Shawn Guo
2019-06-25 12:32   ` Olof Johansson [this message]
2019-06-26  2:02     ` Shawn Guo
2019-06-27  2:14       ` Olof Johansson
2019-06-27 13:25         ` Shawn Guo
2019-06-25 12:45 ` [GIT PULL 1/7] i.MX drivers change " Olof Johansson
2019-06-26  1:48   ` 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=20190625123234.ytva26bkeyqevtwc@localhost \
    --to=olof@lixom.net \
    --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=shawnguo@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).