From: Michael Walle <michael@walle.cc>
To: "Y.b. Lu" <yangbo.lu@nxp.com>
Cc: Vladimir Oltean <vladimir.oltean@nxp.com>,
Shawn Guo <shawnguo@kernel.org>, Leo Li <leoyang.li@nxp.com>,
Rob Herring <robh+dt@kernel.org>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
Adrian Hunter <adrian.hunter@intel.com>,
Ulf Hansson <ulf.hansson@linaro.org>,
linux-mmc@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 09:03:00 +0100 [thread overview]
Message-ID: <71a86b0fbc95892f8fd240e0919e7e23@walle.cc> (raw)
In-Reply-To: <VI1PR04MB6896C22F6B304F365C3BA626F8FB0@VI1PR04MB6896.eurprd04.prod.outlook.com>
Am 2020-11-24 08:41, schrieb Y.b. Lu:
> Hi Vladimir,
>
>> -----Original Message-----
>> From: Vladimir Oltean <vladimir.oltean@nxp.com>
>> Sent: Friday, November 20, 2020 5:30 PM
>> To: Y.b. Lu <yangbo.lu@nxp.com>
>> Cc: Shawn Guo <shawnguo@kernel.org>; Leo Li <leoyang.li@nxp.com>; Rob
>> Herring <robh+dt@kernel.org>; linux-arm-kernel@lists.infradead.org;
>> devicetree@vger.kernel.org; Adrian Hunter <adrian.hunter@intel.com>;
>> Ulf
>> Hansson <ulf.hansson@linaro.org>; linux-mmc@vger.kernel.org;
>> linux-kernel@vger.kernel.org; Ashish Kumar <ashish.kumar@nxp.com>;
>> Michael Walle <michael@walle.cc>
>> Subject: Re: [PATCH] arm64: dts: ls1028a: make the eMMC and SD card
>> controllers use fixed indices
>>
>> On Fri, Nov 20, 2020 at 02:04:02AM +0000, Y.b. Lu wrote:
>> > Hi Vladimir,
>> >
>> > I have already upstreamed a patch for all affected layerscape boards.
>> >
>> https://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux.git/commit/?
>> h=imx/dt64&id=342ab37ecaf8c1b10dd3ca9a1271db29a6af0705
>> >
>> > Please check whether it works for you.
>>
>> Thanks, one can tell that I haven't done my due diligence of checking
>> Shawn's tree first. I'll cherry-pick that patch and carry on with my
>> work.
>>
>> However, the fact still remains that Michael has expressed his opinion
>> regarding mmcblk0 vs mmcblk1. Do you think that we could make the
>> aliases a per-board option instead of per-SoC? Consider that there
>> might
>> even be boards that only use SD card. It would be strange for the
>> block
>> device in that case to be called /dev/mmcblk1.
>
> I don't think it's a problem in board dts to define board specific
> thing, like re-defining alias, and disabling any IP it not using.
First, why would you put it in the architecture include anyway? That
is really board-specific. That is like you would say, we enable all
devices and a board could potentially disable it. TBH it seems that
this will fit your reference boards and you don't care about the
other ones which uses that include.
And as Vladimir pointed out, what do you do if you just have the eMMC
on the LS1028A. It will be mmcblk1 unless you do something like the
following in the board dts:
mmc0 = &esdhc;
/delete-property/ mmc1;
That is really cumbersome, isnt it?
-michael
next prev parent reply other threads:[~2020-11-24 8:03 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 [this message]
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
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=71a86b0fbc95892f8fd240e0919e7e23@walle.cc \
--to=michael@walle.cc \
--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=robh+dt@kernel.org \
--cc=shawnguo@kernel.org \
--cc=ulf.hansson@linaro.org \
--cc=vladimir.oltean@nxp.com \
--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).