From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: jens.glathe@oldschoolsolutions.biz,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Kalle Valo <kvalo@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, Merck Hung <merckhung@gmail.com>
Subject: Re: [PATCH v6 3/3] arm64: dts: qcom: sc8280xp-blackrock: dt definition for WDK2023
Date: Thu, 31 Oct 2024 21:15:36 +0100 [thread overview]
Message-ID: <0bceeb9c-1604-408a-a465-e7ac4d05b3f3@oss.qualcomm.com> (raw)
In-Reply-To: <20241030-jg-blackrock-for-upstream-v6-3-7cd7f7d8d97c@oldschoolsolutions.biz>
On 30.10.2024 12:02 PM, Jens Glathe via B4 Relay wrote:
> From: Jens Glathe <jens.glathe@oldschoolsolutions.biz>
>
> Device tree for the Microsoft Windows Dev Kit 2023. This work
> is based on the initial work of Merck Hung <merckhung@gmail.com>.
>
> Original work: https://github.com/merckhung/linux_ms_dev_kit/blob/ms-dev-kit-2023-v6.3.0/arch/arm64/boot/dts/qcom/sc8280xp-microsoft-dev-kit-2023.dts
>
> The Windows Dev Kit 2023 is a nice little desktop based on sc8280xp.
> Link: https://learn.microsoft.com/en-us/windows/arm/dev-kit/
>
> Supported features:
> - USB type-c and type-a ports
> - minidp connector
> - built-in r8152 Ethernet adapter
> - PCIe devices
> - nvme
> - ath11k WiFi (WCN6855)
> - WCN6855 Bluetooth
> - A690 GPU
> - ADSP and CDSP
> - GPIO keys
> - Audio definition (works via USB)
>
> Signed-off-by: Jens Glathe <jens.glathe@oldschoolsolutions.biz>
> ---
[...]
> + wcn6855-pmu {
> + compatible = "qcom,wcn6855-pmu";
> +
> + pinctrl-0 = <&bt_default>, <&wlan_en>;
> + pinctrl-names = "default";
> +
> + wlan-enable-gpios = <&tlmm 134 GPIO_ACTIVE_HIGH>;
> + bt-enable-gpios = <&tlmm 133 GPIO_ACTIVE_HIGH>;
> +
> + vddio-supply = <&vreg_s10b>;
> + vddaon-supply = <&vreg_s12b>;
> + vddpmu-supply = <&vreg_s12b>;
> + vddrfa0p95-supply = <&vreg_s12b>;
> + vddrfa1p3-supply = <&vreg_s11b>;
> + vddrfa1p9-supply = <&vreg_s1c>;
> + vddpcie1p3-supply = <&vreg_s11b>;
> + vddpcie1p9-supply = <&vreg_s1c>;
Please update this atop
<20241018-sc8280xp-pwrseq-v6-0-8da8310d9564@linaro.org>
most notably including a new supply (which will likely be identical)
> + compatible = "qcom,sc8280xp-sndcard";
> + model = "microsoft/blackrock";
> + audio-routing =
Please don't break the line, see e.g. x1e80100-crd.dts
> + "SpkrLeft IN", "WSA_SPK1 OUT",
> + "SpkrRight IN", "WSA_SPK2 OUT",
Oh, this thing has a speaker!
[...]
> +&pmc8280_1_gpios {
> + edp_bl_en: edp-bl-en-state {
> + pins = "gpio8";
> + function = "normal";
> + };
> +
> + edp_bl_reg_en: edp-bl-reg-en-state {
> + pins = "gpio9";
> + function = "normal";
> + };
> +
> + misc_3p3_reg_en: misc-3p3-reg-en-state {
> + pins = "gpio1";
> + function = "normal";
> + };
Sorting GPIOs by their number is preferred
https://docs.kernel.org/devicetree/bindings/dts-coding-style.html#order-of-nodes
[...]
> +&tlmm {
> + gpio-reserved-ranges = <70 2>, <74 6>, <125 2>, <128 2>, <154 4>;
Do we know what these are for? If so, please describe it (also
like in x1e80100-crd.dts)
Konrad
next prev parent reply other threads:[~2024-10-31 20:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-30 11:02 [PATCH v6 0/3] arm64: dts: qcom: sc8280xp-blackrock: dt definition for Windows Dev Kit 2023 Jens Glathe via B4 Relay
2024-10-30 11:02 ` [PATCH v6 1/3] dt-bindings: arm: qcom: Add Microsoft " Jens Glathe via B4 Relay
2024-10-30 11:02 ` [PATCH v6 2/3] firmware: qcom: scm: Allow QSEECOM for " Jens Glathe via B4 Relay
2024-10-30 11:02 ` [PATCH v6 3/3] arm64: dts: qcom: sc8280xp-blackrock: dt definition for WDK2023 Jens Glathe via B4 Relay
2024-10-31 18:54 ` Krishna Kurapati
2024-10-31 19:24 ` Jens Glathe
2024-10-31 20:15 ` Konrad Dybcio [this message]
2024-10-31 20:22 ` Jens Glathe
2024-10-30 11:48 ` [PATCH v6 0/3] arm64: dts: qcom: sc8280xp-blackrock: dt definition for Windows Dev Kit 2023 Kalle Valo
2024-10-30 17:04 ` Rob Herring (Arm)
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=0bceeb9c-1604-408a-a465-e7ac4d05b3f3@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jens.glathe@oldschoolsolutions.biz \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=kvalo@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=merckhung@gmail.com \
--cc=robh@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
all inboxes | Powered by JetHome®