From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Nizat Mikayilli <nacht@dxdmail.cc>,
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>
Cc: Abel Vesa <abelvesa@kernel.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/2] arm64: dts: qcom: sm8550: Add support for Samsung Galaxy Tab S9 Wi-Fi
Date: Mon, 19 Oct 2026 14:33:11 +0200 [thread overview]
Message-ID: <c2f7946b-ba31-4f0c-bd84-fae3481f2965@oss.qualcomm.com> (raw)
In-Reply-To: <f7ba4d5a-0e8c-417d-a1fd-5b5e392df71a@dxdmail.cc>
On 10/15/26 11:06 PM, Nizat Mikayilli wrote:
> On 10/12/26 4:14 PM, Konrad Dybcio wrote:
>> On 10/5/26 9:47 PM, Nizat Mikayilli via B4 Relay wrote:
>>> amplifiers and the VA macro probing. The microSD slot is described but
>>> not yet tested; audio playback and capture were not exercised.
>>
>> Please test them!
>
> Done: microSD works (UHS-I SDR104, read/write verified, card detect
> works), and so do speaker playback and DMIC capture. I'll update the
> commit message in v3.
>
>>> The display panel, touch, pen digitizer, cameras, battery/charging and
>>> the wireless module are not described here; the latter needs additional
>>> power sequencing and follows as a separate series.
>>
>> Wi-Fi/BT should be a low-hanging fruit, see e.g. sm8550-qrd.dts
>
> I tried a qrd-style description (wcn6855-pmu, PCIe0 with wifi@0, BT on
> uart14). From a cold boot the chip doesn't come up: all PMU rails are on
> and wlan-en is high, but there's no PCIe link and BT times out.
>
> It works with the same nodes once the 11 WLAN PDC messages from the
> downstream qcom,pdc_init_table are sent to AOP over the AOSS QMP during
> power-up (tested with a hacked-up pwrseq-qcom-wcn). So this needs a
> driver change first, and I'd like to send it separately.
Sure!
> Any preference on how to model that? I'd rather not put the raw strings
> in DT, so a table in the driver seems better, but I'm not sure what to
> key it on, since other boards don't need it.
Please show me what your current diff is, on other platforms we didn't
have to go through these hoops..
Konrad
next prev parent reply other threads:[~2026-10-19 12:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-05 19:47 [PATCH v2 0/2] Add Samsung Galaxy Tab S9 Wi-Fi (SM-X710) support Nizat Mikayilli via B4 Relay
2026-10-05 19:47 ` [PATCH v2 1/2] dt-bindings: arm: qcom: Add Samsung Galaxy Tab S9 Wi-Fi Nizat Mikayilli via B4 Relay
2026-10-09 8:51 ` Krzysztof Kozlowski
2026-10-05 19:47 ` [PATCH v2 2/2] arm64: dts: qcom: sm8550: Add support for " Nizat Mikayilli via B4 Relay
2026-10-12 14:14 ` Konrad Dybcio
2026-10-15 21:06 ` Nizat Mikayilli
2026-10-19 12:33 ` Konrad Dybcio [this message]
2026-10-19 22:40 ` Nizat Mikayilli
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=c2f7946b-ba31-4f0c-bd84-fae3481f2965@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=abelvesa@kernel.org \
--cc=andersson@kernel.org \
--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=nacht@dxdmail.cc \
--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®