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-SoC Maintainers <arm@kernel.org>,
dl-linux-imx <linux-imx@nxp.com>,
Sascha Hauer <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
Linux ARM Mailing List <linux-arm-kernel@lists.infradead.org>
Subject: Re: [GIT PULL 7/7] i.MX defconfig changes for 5.3
Date: Thu, 27 Jun 2019 10:14:25 +0800 [thread overview]
Message-ID: <CAOesGMiWqgBdxZ+XRexxLSEkZ_WuegxgqLmJ4=iBvhTxAJ_okQ@mail.gmail.com> (raw)
In-Reply-To: <20190626020213.GF16146@dragon>
On Wed, Jun 26, 2019 at 10:02 AM Shawn Guo <shawnguo@kernel.org> wrote:
>
> On Tue, Jun 25, 2019 at 05:32:34AM -0700, Olof Johansson wrote:
> > > 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.
>
> Hmm, soc_device_match() comes out of SoC bus subsystem and will be used
> by device drivers to identify SoC.
Ah, yes of course. But don't we usually use compatible for this?
> >
> >
> > > 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.
>
> Sorry for not making it clear in the commit log. This basically enables
> the access to SoC fuses, where various system information are stored
> there, like CPU speed grading which is needed by cpufreq support.
Having hardware self-describe is nice, not having to populate DT
entries from the bootloader.
> I will rework the patch by putting above info into commit log, and
> resend the PR.
Thanks!
-Olof
_______________________________________________
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-06-27 6:50 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
2019-06-26 2:02 ` Shawn Guo
2019-06-27 2:14 ` Olof Johansson [this message]
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='CAOesGMiWqgBdxZ+XRexxLSEkZ_WuegxgqLmJ4=iBvhTxAJ_okQ@mail.gmail.com' \
--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).