devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: FUKAUMI Naoki <naoki@radxa.com>
To: jagan@amarulasolutions.com
Cc: abbaraju.manojsai@amarulasolutions.com,
	devicetree@vger.kernel.org, heiko@sntech.de,
	krzysztof.kozlowski+dt@linaro.org,
	linux-amarula@amarulasolutions.com,
	linux-arm-kernel@lists.infradead.org,
	linux-rockchip@lists.infradead.org, naoki@radxa.com,
	robh+dt@kernel.org, stephen@radxa.com
Subject: Re: [PATCH 2/2] arm64: dts: rockchip: rk3399: Radxa ROCK 4C+
Date: Tue, 30 Aug 2022 05:35:39 +0000	[thread overview]
Message-ID: <20220830053539.181707-1-naoki@radxa.com> (raw)
In-Reply-To: <CAMty3ZAEetiD4kTLeRVved2wb_uK-MqZ3h3TQByQa-0j9TQqRg@mail.gmail.com>

> > > +     aliases {
> > > +             mmc0 = &sdmmc;
> >
> > please add
> >
> >                 mmc1 = &sdhci;
> >
> > as like as other ROCK (Pi) 4 series.
> 
> are you sure? other use the same.
> 
> mmc0 = &sdmmc;
> mmc1 = &sdhci;

well... I asked "please do the same", i.e.

mmc0 = &sdmmc;
mmc1 = &sdhci;

is there any problem?

Best regards,

--
FUKAUMI Naoki

  reply	other threads:[~2022-08-30  5:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-24  8:09 [PATCH 1/2] dt-bindings: arm: rockchip: Document Radxa ROCK 4C+ Jagan Teki
2022-08-24  8:09 ` [PATCH 2/2] arm64: dts: rockchip: rk3399: " Jagan Teki
2022-08-24 12:46   ` Krzysztof Kozlowski
2022-08-29 20:17   ` FUKAUMI Naoki
2022-08-29 20:28     ` Jagan Teki
2022-08-29 21:01       ` FUKAUMI Naoki
2022-08-30  5:33         ` Jagan Teki
2022-08-30  5:43           ` FUKAUMI Naoki
2022-08-30  6:19             ` Jagan Teki
2022-08-30  4:56     ` Jagan Teki
2022-08-30  5:35       ` FUKAUMI Naoki [this message]
2022-08-24 12:42 ` [PATCH 1/2] dt-bindings: arm: rockchip: Document " Krzysztof Kozlowski

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=20220830053539.181707-1-naoki@radxa.com \
    --to=naoki@radxa.com \
    --cc=abbaraju.manojsai@amarulasolutions.com \
    --cc=devicetree@vger.kernel.org \
    --cc=heiko@sntech.de \
    --cc=jagan@amarulasolutions.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-amarula@amarulasolutions.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=robh+dt@kernel.org \
    --cc=stephen@radxa.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).