From: "Heiko Stübner" <heiko@sntech.de>
To: Michael Riesch <michael.riesch@wolfvision.net>,
linux-rockchip@lists.infradead.org,
Sjoerd Simons <sjoerd@collabora.com>
Cc: kernel@collabora.com, Akash Gajjar <akash@openedev.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] arm64: dts: rockchip: rock-pi-s add more peripherals
Date: Wed, 08 Jun 2022 14:19:55 +0200 [thread overview]
Message-ID: <2759751.88bMQJbFj6@diego> (raw)
In-Reply-To: <3576f2af98a0d9e7128568777d85af3bfbab801d.camel@collabora.com>
Am Mittwoch, 8. Juni 2022, 14:07:33 CEST schrieb Sjoerd Simons:
> Hey Michael,
>
> On Mon, 2022-06-06 at 14:00 +0200, Michael Riesch wrote:
> >
> > > + aliases {
> > > + ethernet0 = &gmac;
> > > + mmc0 = &emmc;
> > > + mmc1 = &sdmmc;
> >
> > Sure? emmc is at address ff49000 which is larger than sdmmc's address
> > ff480000. I believe the aliases should be sorted w.r.t. addresses.
>
> Do you have a reference about this sorting requirement?
I do believe we used that mmcx -> *mmc-device sorted by address
when the aliases still were in the main soc dtsi. Simply because one
couldn't really know what was available on a specific board
(no emmc for example).
I guess now on a per-board level we could actually do that more relaxed
and let that be the decision of the board submitter ;-) .
Heiko
> Also do you mean that mmc0 should be &sdmmc *or* that the aliases
> should have mmc1 listed first.
>
> For reference the reason is that mmc0 is emmc is because it seems more
> logical to have the builtin devices come first (e.g. as mmcblk0)
>
>
> > Best regards,
> > Michael
> >
> > > + };
> > > +
> > > chosen {
> > > stdout-path = "serial0:1500000n8";
> > > };
> > > @@ -132,6 +138,15 @@ &emmc {
> > > status = "okay";
> > > };
> > >
> > > +&gmac {
> > > + clock_in_out = "output";
> > > + phy-supply = <&vcc_io>;
> > > + snps,reset-gpio = <&gpio0 RK_PA7 GPIO_ACTIVE_LOW>;
> > > + snps,reset-active-low;
> > > + snps,reset-delays-us = <0 50000 50000>;
> > > + status = "okay";
> > > +};
> > > +
> > > &i2c1 {
> > > status = "okay";
> > > };
> > > @@ -195,10 +210,47 @@ &sdmmc {
> > > status = "okay";
> > > };
> > >
> > > +&u2phy {
> > > + status = "okay";
> > > +
> > > + u2phy_host: host-port {
> > > + phy-supply = <&vcc5v0_otg>;
> > > + status = "okay";
> > > + };
> > > +
> > > + u2phy_otg: otg-port {
> > > + phy-supply = <&vcc5v0_otg>;
> > > + status = "okay";
> > > + };
> > > +};
> > > +
> > > &uart0 {
> > > status = "okay";
> > > };
> > >
> > > &uart4 {
> > > status = "okay";
> > > +
> > > + bluetooth {
> > > + compatible = "realtek,rtl8723bs-bt";
> > > + device-wake-gpios = <&gpio4 RK_PB3
> > > GPIO_ACTIVE_HIGH>;
> > > + host-wake-gpios = <&gpio4 RK_PB4 GPIO_ACTIVE_HIGH>;
> > > + };
> > > +};
> > > +
> > > +&usb_host_ehci {
> > > + status = "okay";
> > > +};
> > > +
> > > +&usb_host_ohci {
> > > + status = "okay";
> > > +};
> > > +
> > > +&usb20_otg {
> > > + dr_mode = "peripheral";
> > > + status = "okay";
> > > +};
> > > +
> > > +&wdt {
> > > + status = "okay";
> > > };
>
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-06-08 12:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-06 8:26 [PATCH 0/2] Add support for Radxa ROCK Pi S Sjoerd Simons
2022-06-06 8:26 ` [PATCH 1/2] arm64: dts: rockchip: add ROCK Pi S DTS support Sjoerd Simons
2022-06-09 17:50 ` Rob Herring
2022-06-06 8:26 ` [PATCH 2/2] arm64: dts: rockchip: rock-pi-s add more peripherals Sjoerd Simons
2022-06-06 12:00 ` Michael Riesch
2022-06-08 12:07 ` Sjoerd Simons
2022-06-08 12:19 ` Heiko Stübner [this message]
2022-06-08 13:08 ` Michael Riesch
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=2759751.88bMQJbFj6@diego \
--to=heiko@sntech.de \
--cc=akash@openedev.com \
--cc=devicetree@vger.kernel.org \
--cc=kernel@collabora.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=michael.riesch@wolfvision.net \
--cc=robh+dt@kernel.org \
--cc=sjoerd@collabora.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).