From: Alexander Kurz <akurz@blala.de>
To: Vladimir Zapolskiy <vz@mleia.com>
Cc: Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <kernel@pengutronix.de>,
Fabio Estevam <fabio.estevam@nxp.com>,
Lucas Stach <l.stach@pengutronix.de>,
linux-mmc@vger.kernel.org
Subject: Re: [PATCH] ARM: dts: imx50: imx50-esdhc use imx53-esdhc
Date: Sun, 9 Oct 2016 23:09:28 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.00.1610092241410.19531@blala.de> (raw)
In-Reply-To: <5eae97cb-7a15-9bcf-f732-6141f99f0990@mleia.com>
On Sun, 9 Oct 2016, Vladimir Zapolskiy wrote:
> Hi Alexander,
>
> On 09.10.2016 18:34, Alexander Kurz wrote:
> > According to the reference manuals, both imx50/imx53 SOC seem to share
> > the same eSDHC controller, especially the section on "Multi-block Read"
> > mentioned in commit 361b8482026c ("mmc: sdhci-esdhc-imx: fix multiblock
> > reads on i.MX53") is identical for both SOC.
> > Hence, let imx50 use imx53-esdhc.
> >
> > Signed-off-by: Alexander Kurz <akurz@blala.de>
> > ---
> > arch/arm/boot/dts/imx50.dtsi | 8 ++++----
> > 1 file changed, 4 insertions(+), 4 deletions(-)
> >
> > diff --git a/arch/arm/boot/dts/imx50.dtsi b/arch/arm/boot/dts/imx50.dtsi
> > index e245713..769eac7 100644
> > --- a/arch/arm/boot/dts/imx50.dtsi
> > +++ b/arch/arm/boot/dts/imx50.dtsi
> > @@ -99,7 +99,7 @@
> > ranges;
> >
> > esdhc1: esdhc@50004000 {
> > - compatible = "fsl,imx50-esdhc";
> > + compatible = "fsl,imx50-esdhc", "fsl,imx53-esdhc";
>
> Instead of this change please add "fsl,imx50-esdhc" compatible to a list found in
> drivers/mmc/host/sdhci-esdhc-imx.c
For me it looks like a typical usecase to be handled via DT.
>From the perspective of the reference manuals it looks like both SOC
feature exactly the same sdhc hardware.
Extra benefit: projects sharing the linux DT set (e.g. barebox) will
immediately profit from this change.
>
> Regarding DTS change if the controllers are the same I think it may
> have sense to add "fsl,imx50-esdhc" compatible to imx53.dtsi definitions,
> but not the other way round.
Is there some requirement for ascending numbers?
I guess, i.MX50 just got the smaller number (compared to i.MX51/53) for
marketing reasons (consumer-e-book reader vs "serious" industrial
applications). Also the mx50 is a younger design compared to the mx51.
The mx50 is an SOC for e-book readers and other battery powered gadgets
(e.g. battery powered wireless hard disk) - it never got the attention
like the industrial SOC series (mx51/53).
>
> --
> With best wishes,
> Vladimir
>
next prev parent reply other threads:[~2016-10-09 21:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-09 16:34 [PATCH] ARM: dts: imx50: imx50-esdhc use imx53-esdhc Alexander Kurz
2016-10-09 20:25 ` Vladimir Zapolskiy
2016-10-09 21:09 ` Alexander Kurz [this message]
2016-10-10 6:47 ` Uwe Kleine-König
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=alpine.DEB.2.00.1610092241410.19531@blala.de \
--to=akurz@blala.de \
--cc=fabio.estevam@nxp.com \
--cc=kernel@pengutronix.de \
--cc=l.stach@pengutronix.de \
--cc=linux-mmc@vger.kernel.org \
--cc=shawnguo@kernel.org \
--cc=vz@mleia.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