From: Scott Wood <scottwood@freescale.com>
To: Yangbo Lu <yangbo.lu@freescale.com>,
linux-mmc@vger.kernel.org, ulf.hansson@linaro.org
Cc: X.Xie@freescale.com, LeoLi@freescale.com
Subject: Re: [v3, 4/5] powerpc: dts: t4240: add syscon support for DCFG node
Date: Tue, 8 Dec 2015 11:46:21 -0600 [thread overview]
Message-ID: <1449596781.15946.126.camel@freescale.com> (raw)
In-Reply-To: <1448594417-22515-5-git-send-email-yangbo.lu@freescale.com>
On Fri, 2015-11-27 at 11:20 +0800, Yangbo Lu wrote:
> Add syscon support for DCFG node, so that the driver could use
> syscon regmap interface to access the device config module registers.
> And the CONFIG_MFD_SYSCON should be enabled for this.
>
> Signed-off-by: Yangbo Lu <yangbo.lu@freescale.com>
> ---
> Changes for v2:
> - None
> Changes for v3:
> - Added this patch
> ---
> arch/powerpc/boot/dts/fsl/t4240si-post.dtsi | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/arch/powerpc/boot/dts/fsl/t4240si-post.dtsi
> b/arch/powerpc/boot/dts/fsl/t4240si-post.dtsi
> index 68c4ead..5f148b2 100644
> --- a/arch/powerpc/boot/dts/fsl/t4240si-post.dtsi
> +++ b/arch/powerpc/boot/dts/fsl/t4240si-post.dtsi
> @@ -941,7 +941,9 @@
> /include/ "qoriq-mpic4.3.dtsi"
>
> guts: global-utilities@e0000 {
> - compatible = "fsl,t4240-device-config", "fsl,qoriq-device
> -config-2.0";
> + compatible = "fsl,t4240-device-config",
> + "fsl,qoriq-device-config-2.0",
> + "syscon";
I really don't like changing the device tree based on Linux internals. It
also means that the workaround wouldn't work for users that don't upgrade
their device tree. I definitely don't like one QorIQ chip having "syscon" on
the dcfg node but others not having it.
The guts driver should just maintain a list of compatibles to match. Why do
we need to use syscon, rather than a guts driver that exports an fsl_get_svr()
function?
-Scott
next prev parent reply other threads:[~2015-12-08 18:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-27 3:20 [v3, 0/5] eSDHC patches introduction Yangbo Lu
2015-11-27 3:20 ` [v3, 1/5] powerpc/fsl: move mpc85xx.h to include/linux Yangbo Lu
2015-12-08 13:49 ` Ulf Hansson
2015-12-08 17:38 ` Scott Wood
2015-12-08 17:44 ` Scott Wood
2015-11-27 3:20 ` [v3, 2/5] mmc: sdhci-of-esdhc: get SVR from global utilities registers Yangbo Lu
2015-12-08 17:45 ` Scott Wood
2015-11-27 3:20 ` [v3, 3/5] mmc: kconfig: select MFD_SYSCON for MMC_SDHCI_OF_ESDHC Yangbo Lu
2015-12-08 13:49 ` Ulf Hansson
2015-12-08 17:40 ` Scott Wood
2015-11-27 3:20 ` [v3, 4/5] powerpc: dts: t4240: add syscon support for DCFG node Yangbo Lu
2015-12-08 17:46 ` Scott Wood [this message]
[not found] ` <BLUPR0301MB2065B5878A43F66982D6B30BF2E80@BLUPR0301MB2065.namprd03.prod.outlook.com>
2015-12-09 4:33 ` Scott Wood
[not found] ` <BLUPR0301MB206558CB317D48AC5CEF3642F2E80@BLUPR0301MB2065.namprd03.prod.outlook.com>
2015-12-09 17:00 ` Scott Wood
2015-12-11 8:26 ` Ulf Hansson
2015-12-11 8:29 ` Scott Wood
[not found] ` <BLUPR0301MB2065A179DCAF428EB79785B7F2E80@BLUPR0301MB2065.namprd03.prod.outlook.com>
2015-12-09 17:01 ` Scott Wood
2015-11-27 3:20 ` [v3, 5/5] mmc: sdhci-of-esdhc: fix host version for T4240-R1.0-R2.0 Yangbo Lu
2015-12-08 13:59 ` [v3, 0/5] eSDHC patches introduction Ulf Hansson
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=1449596781.15946.126.camel@freescale.com \
--to=scottwood@freescale.com \
--cc=LeoLi@freescale.com \
--cc=X.Xie@freescale.com \
--cc=linux-mmc@vger.kernel.org \
--cc=ulf.hansson@linaro.org \
--cc=yangbo.lu@freescale.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox