From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Bjorn Andersson <bjorn.andersson@oss.qualcomm.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] arm64: dts: qcom: qcm6490: Introduce the Particle Tachyon
Date: Fri, 12 Sep 2025 13:13:17 +0200 [thread overview]
Message-ID: <ec31257b-fe10-4de7-8fb6-d649677f680e@oss.qualcomm.com> (raw)
In-Reply-To: <20250910-tachyon-v1-3-5090bfd133e0@oss.qualcomm.com>
On 9/11/25 1:05 AM, Bjorn Andersson wrote:
> The Particle Tachyon is a single board computer with 5G connectivity
> with AI accelerator, based on the Qualcomm QCM6490 platform.
>
> Introduce the board, with support for UFS, USB, USB Type-C PD and
> altmode (DisplayPort), GPU, charger/battery status, PCIe shield,
> SD-card, and remoteprocs.
>
> Signed-off-by: Bjorn Andersson <bjorn.andersson@oss.qualcomm.com>
> ---
[...]
> + leds {
> + compatible = "gpio-leds";
> +
> + pinctrl-names = "default";
> + pinctrl-0 = <&activity_led_state>;
property-n
property-names
is preferred, file-wide (you currently have a mixture)
[...]
> +
> +&i2c1 {
> + status = "okay";
This likely results in a "falling back to 100 KHz" warning/notice,
please specify the bus speed explicitly
[...]
> +&mdss_dp_out {
> + data-lanes = <0 1>;
Is 2 lanes a hw limitation?
[...]
> +&pmk8350_rtc {
I see no reason for RTC not to be enabled by default
[...]
> +&pon_pwrkey {
Same here> + status = "okay";
> +};
> +&uart7 {
> + /delete-property/interrupts;
/delete-property/(space)interrupts, please
(yes we desperately need a formatter)
[...]
> +&usb_1_qmpphy {
> + vdda-phy-supply = <&vreg_l6b_1p2>;
> + vdda-pll-supply = <&vreg_l1b_0p912>;
> +
> + orientation-switch;
This is specified in the SoC DTSI
[...]
> +&usb_dp_qmpphy_dp_in {
> + remote-endpoint = <&mdss_dp_out>;
> +};
And so is this link
> +
> +&usb_dp_qmpphy_out {
> + remote-endpoint = <&pmic_glink_ss_in>;
> +};
> +
> +&usb_dp_qmpphy_usb_ss_in {
> + remote-endpoint = <&usb_1_dwc3_ss>;
> +};
And this one
Konrad
next prev parent reply other threads:[~2025-09-12 11:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-10 23:05 [PATCH 0/3] arm64: dts: qcom: qcm6490: Introduce " Bjorn Andersson
2025-09-10 23:05 ` [PATCH 1/3] dt-bindings: vendor-prefixes: Add Particle Industries Bjorn Andersson
2025-09-15 0:28 ` Rob Herring (Arm)
2025-09-10 23:05 ` [PATCH 2/3] dt-bindings: arm: qcom: Add Particle Tachyon Bjorn Andersson
2025-09-15 0:29 ` Rob Herring (Arm)
2025-09-10 23:05 ` [PATCH 3/3] arm64: dts: qcom: qcm6490: Introduce the " Bjorn Andersson
2025-09-11 19:37 ` Bjorn Andersson
2025-09-12 11:13 ` Konrad Dybcio [this message]
2025-09-16 4:08 ` Bjorn Andersson
2025-09-11 0:01 ` [PATCH 0/3] arm64: dts: qcom: qcm6490: Introduce " Dmitry Baryshkov
2025-09-11 19:19 ` Bjorn Andersson
2025-09-12 1:22 ` Dmitry Baryshkov
2025-09-16 3:26 ` Bjorn Andersson
2025-09-16 10:30 ` Dmitry Baryshkov
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=ec31257b-fe10-4de7-8fb6-d649677f680e@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=bjorn.andersson@oss.qualcomm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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®