From: Stephen Boyd <swboyd@chromium.org>
To: "Joseph S. Barrera III" <joebar@chromium.org>,
LKML <linux-kernel@vger.kernel.org>
Cc: Douglas Anderson <dianders@chromium.org>,
Alexandru M Stan <amstan@chromium.org>,
Andy Gross <agross@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH v4 1/5] arm64: dts: qcom: sc7180: Add wormdingler dts files
Date: Tue, 10 May 2022 10:40:48 -0700 [thread overview]
Message-ID: <CAE-0n511S7dNPetX0dHp2RSPUZQjwGtXM8nMTF0bf03JjbPwfg@mail.gmail.com> (raw)
In-Reply-To: <20220505104024.v4.1.Id769ddc5dbf570ccb511db96da59f97d08f75a9c@changeid>
Quoting Joseph S. Barrera III (2022-05-05 10:41:12)
> diff --git a/arch/arm64/boot/dts/qcom/sc7180-trogdor-wormdingler.dtsi b/arch/arm64/boot/dts/qcom/sc7180-trogdor-wormdingler.dtsi
> new file mode 100644
> index 000000000000..e947e01d0b3b
> --- /dev/null
> +++ b/arch/arm64/boot/dts/qcom/sc7180-trogdor-wormdingler.dtsi
> @@ -0,0 +1,417 @@
[...]
> +
> +/* PINCTRL - board-specific pinctrl */
> +
> +&tlmm {
> + gpio-line-names = "HUB_RST_L",
[...]
> +
> + vdd_reset_1800: vdd-reset-1800 {
> + pinmux {
> + pins = "gpio87";
> + function = "gpio";
> + };
> +
> + pinconf {
> + pins = "gpio87";
> + drive-strength = <2>;
> + bias-disable;
> + };
> + };
> +
> + avdd_lcd_en: avdd-lcd-en {
> + pinmux {
> + pins = "gpio88";
> + function = "gpio";
> + };
> +
> + pinconf {
> + pins = "gpio88";
> + drive-strength = <2>;
> + bias-disable;
> + };
> + };
> +
> + avee_lcd_en: avee-lcd_en {
avee-lcd-en
No underscores in node names please.
> + pinmux {
> + pins = "gpio21";
> + function = "gpio";
> + };
> +
> + pinconf {
> + pins = "gpio21";
> + drive-strength = <2>;
> + bias-disable;
> + };
> + };
Are these supposed to be sorted by node name? Or gpio number? Please do
one of those.
> +
> + mipi_1800_en: mipi-1800-en {
> + pinmux {
> + pins = "gpio86";
> + function = "gpio";
> + };
> +
> + pinconf {
> + pins = "gpio86";
> + drive-strength = <2>;
> + bias-disable;
> + };
> + };
> +};
prev parent reply other threads:[~2022-05-10 17:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-05 17:41 [PATCH v4 1/5] arm64: dts: qcom: sc7180: Add wormdingler dts files Joseph S. Barrera III
2022-05-05 17:41 ` [PATCH v4 2/5] arm64: dts: qcom: sc7180: Add mrbland " Joseph S. Barrera III
2022-05-10 17:45 ` Stephen Boyd
2022-05-05 17:41 ` [PATCH v4 3/5] arm64: dts: qcom: sc7180: Add quackingstick " Joseph S. Barrera III
2022-05-10 17:49 ` Stephen Boyd
2022-05-05 17:41 ` [PATCH v4 4/5] arm64: dts: qcom: sc7180: Add pazquel " Joseph S. Barrera III
2022-05-05 17:41 ` [PATCH v4 5/5] arm64: dts: qcom: sc7180: Add kingoftown " Joseph S. Barrera III
2022-05-05 21:44 ` [PATCH v4 1/5] arm64: dts: qcom: sc7180: Add wormdingler " Doug Anderson
2022-05-10 17:40 ` Stephen Boyd [this message]
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=CAE-0n511S7dNPetX0dHp2RSPUZQjwGtXM8nMTF0bf03JjbPwfg@mail.gmail.com \
--to=swboyd@chromium.org \
--cc=agross@kernel.org \
--cc=amstan@chromium.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=joebar@chromium.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.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).