devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vladimir Oltean <vladimir.oltean@nxp.com>
To: "Y.b. Lu" <yangbo.lu@nxp.com>
Cc: Michael Walle <michael@walle.cc>, Shawn Guo <shawnguo@kernel.org>,
	Leo Li <leoyang.li@nxp.com>, Rob Herring <robh+dt@kernel.org>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	Adrian Hunter <adrian.hunter@intel.com>,
	Ulf Hansson <ulf.hansson@linaro.org>,
	"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Ashish Kumar <ashish.kumar@nxp.com>
Subject: Re: [PATCH] arm64: dts: ls1028a: make the eMMC and SD card controllers use fixed indices
Date: Tue, 24 Nov 2020 11:28:22 +0000	[thread overview]
Message-ID: <20201124112822.2ui57jmoc73top35@skbuf> (raw)
In-Reply-To: <AM7PR04MB688567CA698191E2DB73DEF5F8FB0@AM7PR04MB6885.eurprd04.prod.outlook.com>

On Tue, Nov 24, 2020 at 11:15:19AM +0000, Y.b. Lu wrote:
> > > Not matter it's SD card or eMMC card, if it's on esdhc0, use /dev/mmcblk0.
> > > Not matter it's SD card or eMMC card, if it's on esdhc1, use /dev/mmcblk1.
> >
> > With the note here that you can't actually connect an SD card to eSDHC1,
> > due to the lack of pins for CD/WP.
>
> CD/WP is not essential to support SD card. Both SD/eMMC are supported on both eSDHC controllers.

Let's keep that discussion separate. While in theory you might be right,
I think the real-life complications associated with connecting an eMMC
to eSDHC0 and an SD card to eSDHC1 will make everyone avoid that. So in
practice they are still single-purpose.

> > But it is also natural for a customer to define the indices according to
> > their schematics and what they use. If, say, there is a board that only
> > uses eMMC, I would expect that for the lay person, no one would even bat
> > an eye if that was called /dev/mmcblk0. Whereas, if it was called
> > /dev/mmcblk1 (and there was no /dev/mmcblk0 in the system), maybe you'd
> > have to come up with some explanations which could be avoided.
>
> To make a product friendly to users, it makes sense to define different alias for controller in board dts.
> But it's not the reason to remove the default/natural alias in soc dtsi for two controllers.
> What needs to be done after removing them? Add the same to all other board files?

Yes.
In fact, this is also the reason why we prefer to have:
/soc {
	esdhc: mmc@2140000 {
		status = "disabled";
	};
};
in fsl-ls1028a.dtsi
and
&esdhc {
	status = "okay";
};
in fsl-ls1028a-rdb.dts
and not the other way around:

/soc {
	esdhc: mmc@2140000 {
		status = "okay";
	};
};
in fsl-ls1028a.dtsi
and
&esdhc {
	status = "disabled";
};
in fsl-ls1028a-rdb.dts

So, in line with that, I think that the entity that enables the node
should also define the alias.

It's weird to use /delete-property/ if it can be avoided.

  reply	other threads:[~2020-11-24 11:28 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-19 15:50 [PATCH] arm64: dts: ls1028a: make the eMMC and SD card controllers use fixed indices Vladimir Oltean
2020-11-19 16:08 ` Michael Walle
2020-11-19 16:32   ` Vladimir Oltean
2020-11-20  2:04 ` Y.b. Lu
2020-11-20  9:30   ` Vladimir Oltean
2020-11-23 11:09     ` Michael Walle
2020-11-24  7:41     ` Y.b. Lu
2020-11-24  8:03       ` Michael Walle
2020-11-24  8:47         ` Y.b. Lu
2020-11-24  8:55           ` Michael Walle
2020-11-24  9:02             ` Y.b. Lu
2020-11-24  9:08               ` Michael Walle
2020-11-24  9:22                 ` Y.b. Lu
2020-11-24  9:43                   ` Michael Walle
2020-11-24 10:22                     ` Y.b. Lu
2020-11-24 10:31               ` Vladimir Oltean
2020-11-24 11:15                 ` Y.b. Lu
2020-11-24 11:28                   ` Vladimir Oltean [this message]
2020-11-25  2:59                     ` Y.b. Lu
2020-11-25  8:25                       ` Michael Walle
2020-11-30 14:29                         ` Shawn Guo
2020-12-01  2:38                           ` Y.b. Lu

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=20201124112822.2ui57jmoc73top35@skbuf \
    --to=vladimir.oltean@nxp.com \
    --cc=adrian.hunter@intel.com \
    --cc=ashish.kumar@nxp.com \
    --cc=devicetree@vger.kernel.org \
    --cc=leoyang.li@nxp.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=michael@walle.cc \
    --cc=robh+dt@kernel.org \
    --cc=shawnguo@kernel.org \
    --cc=ulf.hansson@linaro.org \
    --cc=yangbo.lu@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 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).