From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 1/1] arm64: dts: Add the arasan sdhc nodes in apm-storm.dtsi.
Date: Wed, 06 May 2015 10:40:03 +0200 [thread overview]
Message-ID: <2568634.iEosTvMJpM@wuerfel> (raw)
In-Reply-To: <5549C68B.9090602@xilinx.com>
On Wednesday 06 May 2015 09:45:15 Michal Simek wrote:
> On 05/06/2015 09:31 AM, Arnd Bergmann wrote:
> > On Wednesday 06 May 2015 10:41:07 Suman Tripathi wrote:
> >>>> @@ -533,6 +567,16 @@
> >>>> interrupts = <0x0 0x4f 0x4>;
> >>>> };
> >>>>
> >>>> + sdhc0: sdhc at 1c000000 {
> >>>> + device_type = "sdhc";
> >>>
> >>> device_type generally should not be used (there are a few exceptions).
> >>
> >> Okay !!
> >>
> >
> > While we're at it, please change sdhc at 1c000000 to mmc at 1c000000.
> > Even though Linux does not care, we try to use the standard device
> > names for consistency.
>
> Do we have a list of these names somewhere?
> Normally I do use ePARP - generic names recommendation but mmc or sdhci
> are not listed there.
> Both combination mmc@ or sdhci@ are used in the kernel.
>
> On zynq and zynqmp we do use shdci at .
>
Ah, I thought ePAPR listed mmc already. Using "sdhci" is a little too
specific here, since a lot of mmc hosts are not sdhci compliant, and
"sdhc" is completely wrong, because that identifies a specific card
type, but a host that supports SDHC cards will generally also work
with SD (less than 4GB) or SDXC (more than 48GB) cards.
Arnd
next prev parent reply other threads:[~2015-05-06 8:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1430817426-5241-1-git-send-email-stripathi@apm.com>
[not found] ` <1430817426-5241-2-git-send-email-stripathi@apm.com>
2015-05-05 10:34 ` [PATCH v5 1/1] arm64: dts: Add the arasan sdhc nodes in apm-storm.dtsi Ulf Hansson
2015-05-06 9:49 ` Ulf Hansson
2015-05-05 19:41 ` Rob Herring
2015-05-06 5:11 ` Suman Tripathi
2015-05-06 7:31 ` Arnd Bergmann
2015-05-06 7:45 ` Michal Simek
2015-05-06 8:40 ` Arnd Bergmann [this message]
2015-05-06 12:41 ` Michal Simek
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=2568634.iEosTvMJpM@wuerfel \
--to=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
/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).