From: Johan Jonker <jbx6244@gmail.com>
To: Samuel Holland <samuel@sholland.org>, Heiko Stuebner <heiko@sntech.de>
Cc: Alex Bee <knaerzche@gmail.com>, Chen-Yu Tsai <wenst@chromium.org>,
Levin Du <djw@t-chip.com.cn>, Liang Chen <cl@rock-chips.com>,
Peter Geis <pgwipeout@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Tianling Shen <cnsztl@gmail.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org
Subject: Re: [PATCH 3/3] arm64: dts: rockchip: Add Pine64 PineNote board
Date: Wed, 2 Feb 2022 12:01:37 +0100 [thread overview]
Message-ID: <242e35d7-6e4a-2e30-3739-1fca77587baf@gmail.com> (raw)
In-Reply-To: <153a5ddf-74d0-71e9-2694-5d1fc51472db@gmail.com>
On 2/2/22 11:41, Johan Jonker wrote:
> Hi Samuel,
> On 1/30/22 06:38, Samuel Holland wrote:
>> +/ {
>> + aliases {
>> + mmc0 = &sdhci;
sdmmc1 ??
MMC aliases should be sort on reg address, based on availability and
without number gap.
>> + };
>> +
[..]
>> +&sdhci {
>> + bus-width = <8>;
>> + mmc-hs200-1_8v;
>> + non-removable;
>> + pinctrl-0 = <&emmc_bus8>, <&emmc_clk>, <&emmc_cmd>, <&emmc_datastrobe>, <&emmc_rstnout>;
>> + pinctrl-names = "default";
>> + vmmc-supply = <&vcc_3v3>;
>> + vqmmc-supply = <&vcc_1v8>;
>> + status = "okay";
>> +};
>> +
>> +&sdmmc1 {
>> + bus-width = <4>;
>> + cap-sd-highspeed;
>> + cap-sdio-irq;
>
>> + disable-wp;
>
> From mmc-controller.yaml:
>
> disable-wp:
> $ref: /schemas/types.yaml#/definitions/flag
> description:
> When set, no physical write-protect line is present. This
> property should only be specified when the controller has a
> dedicated write-protect detection logic. If a GPIO is always used
> for the write-protect detection logic, it is sufficient to not
> specify the wp-gpios property in the absence of a write-protect
> line. Not used in combination with eMMC or SDIO.
>
>> + keep-power-in-suspend;
>> + mmc-pwrseq = <&sdio_pwrseq>;
>> + non-removable;
>> + pinctrl-0 = <&sdmmc1_bus4>, <&sdmmc1_clk>, <&sdmmc1_cmd>;
>> + pinctrl-names = "default";
>> + sd-uhs-sdr104;
>> + vmmc-supply = <&vcc_wl>;
>> + vqmmc-supply = <&vcca_1v8_pmu>;
>> + status = "okay";
>> +};
>> +
next prev parent reply other threads:[~2022-02-02 11:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-30 5:38 [PATCH 1/3] dt-bindings: arm: rockchip: Add Pine64 PineNote board Samuel Holland
2022-01-30 5:38 ` [PATCH 2/3] arm64: dts: rockchip: rk356x: Add pdm node Samuel Holland
2022-01-30 9:49 ` Michael Riesch
2022-01-30 5:38 ` [PATCH 3/3] arm64: dts: rockchip: Add Pine64 PineNote board Samuel Holland
2022-02-02 10:41 ` Johan Jonker
2022-02-02 11:01 ` Johan Jonker [this message]
2022-02-11 13:25 ` [PATCH 1/3] dt-bindings: arm: " Rob Herring
2022-02-12 0:23 ` Heiko Stuebner
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=242e35d7-6e4a-2e30-3739-1fca77587baf@gmail.com \
--to=jbx6244@gmail.com \
--cc=cl@rock-chips.com \
--cc=cnsztl@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=djw@t-chip.com.cn \
--cc=heiko@sntech.de \
--cc=knaerzche@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=pgwipeout@gmail.com \
--cc=robh+dt@kernel.org \
--cc=samuel@sholland.org \
--cc=wenst@chromium.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).