From: Andrei-Alexandru Bleortu <me@andrei-z.com>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Cc: Bjorn Andersson <andersson@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Jeff Johnson <jjohnson@kernel.org>,
Johannes Berg <johannes@sipsolutions.net>,
Konrad Dybcio <konradybcio@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Rob Herring <robh@kernel.org>, <ath11k@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-arm-msm@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH v2 3/3] arm64: dts: qcom: ipq5018: add Ubiquiti UniFi U6 Enterprise
Date: Fri, 23 Oct 2026 16:28:54 +0300 [thread overview]
Message-ID: <20261023132854.3641937-1-me@andrei-z.com> (raw)
In-Reply-To: <bd062ae7-74c2-486e-9413-15ca8c943055@oss.qualcomm.com>
On 10/21/26 3:44 PM, Konrad Dybcio wrote:
> On 10/4/26 1:10 PM, Andrei-Alexandru Bleortu wrote:
>> + button-reset {
>> + label = "reset";
>
> Normally we do sentence case here, i.e. "Reset"
Will do in v3.
>> +&blsp1_i2c3 {
>> + pinctrl-0 = <&i2c_pins>;
>> + pinctrl-names = "default";
>> + status = "okay";
>
> Please keep a \n before 'status', file-wide for consistency
Will do, for &blsp1_i2c3, &blsp1_spi1 and &sdhc_1.
>> +&pcie0_port0 {
>> + reset-gpios = <&tlmm 15 GPIO_ACTIVE_LOW>;
>
> No wake-gpios?
Not that I can find. The vendor device tree gives only PERST# for the
two radios (GPIO15 and GPIO18) and configures nothing on GPIO16, 17 or
19, where a reference-design WAKE# would be. Without a schematic I
can't tell whether WAKE# is routed at all, so I'd rather leave it out
than copy the RDP's GPIO16. Both radios work without it.
>> + wifi@0,0 {
>> + compatible = "pci17cb,1104";
>> + reg = <0x10000 0x0 0x0 0x0 0x0>;
>> + qcom,calibration-variant = "Ubiquiti-U6-Enterprise-5G";
>
> Does the same calibration work for both radios?
No, they need different board data: the 6 GHz radio below pcie1_port0
has "Ubiquiti-U6-Enterprise-6G". The two QCN9074s are otherwise
indistinguishable to ath11k: both are 17cb:1104 with subsystem
17cb:1104, and both report chip-id 0 and board-id 255 (unprogrammed
OTP). So the variant is the only part of the board name that differs:
bus=pci,qmi-chip-id=0,qmi-board-id=255,variant=Ubiquiti-U6-Enterprise-5G
bus=pci,qmi-chip-id=0,qmi-board-id=255,variant=Ubiquiti-U6-Enterprise-6G
The stock firmware also ships a separate board file per band. Both
board files went to the ath11k list under these names.
>> +&prng {
>> + status = "okay";
>> +};
>
> Please add a preceding patch to enable it in the SoC DTSI, this should
> never really need to be disabled
Will do; v3 drops the status from the dtsi, as ipq5332 and ipq9574
have it, and the board no longer touches &prng.
Thanks for the review!
Andrei
prev parent reply other threads:[~2026-10-23 13:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-04 11:10 [PATCH v2 0/3] " Andrei-Alexandru Bleortu
2026-10-04 11:10 ` [PATCH v2 1/3] dt-bindings: net: wireless: qcom,ath11k-pci: add QCN9074 Andrei-Alexandru Bleortu
2026-10-04 11:10 ` [PATCH v2 2/3] dt-bindings: arm: qcom: add Ubiquiti UniFi U6 Enterprise Andrei-Alexandru Bleortu
2026-10-04 11:10 ` [PATCH v2 3/3] arm64: dts: qcom: ipq5018: " Andrei-Alexandru Bleortu
2026-10-21 12:44 ` Konrad Dybcio
2026-10-23 13:28 ` Andrei-Alexandru Bleortu [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=20261023132854.3641937-1-me@andrei-z.com \
--to=me@andrei-z.com \
--cc=andersson@kernel.org \
--cc=ath11k@lists.infradead.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jjohnson@kernel.org \
--cc=johannes@sipsolutions.net \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@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®