From: Zijun Hu <zijun.hu@oss.qualcomm.com>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Cc: Jingyi Wang <jingyi.wang@oss.qualcomm.com>,
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>,
aiqun.yu@oss.qualcomm.com, tingwei.zhang@oss.qualcomm.com,
trilok.soni@oss.qualcomm.com, yijie.yang@oss.qualcomm.com,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
20260224-knp-dts-misc-v6-0-79d20dab8a60@oss.qualcomm.com
Subject: Re: [PATCH 4/6] arm64: dts: qcom: kaanapali-mtp: Enable bluetooth and Wifi
Date: Wed, 1 Apr 2026 18:39:19 +0800 [thread overview]
Message-ID: <bf1df5d9-787c-40e9-93db-536612982427@oss.qualcomm.com> (raw)
In-Reply-To: <ohg7jn4lozqw3lhwmhpx7qyiuw2pmjl7zwv6cbbjmbr2vnnw2e@qz6wbrjynbta>
On 3/30/2026 7:53 PM, Dmitry Baryshkov wrote:
>>> - Is the pin defined in the schema?
>> schema define property 'swctrl-gpios' with description
>> "GPIO line indicating the state of the clock supply to the BT module"
>>
>>> - Is the pin wired in the hardware?
>> pin SW_CTRL is wired in hardware.
> Granted your three answers, it can and should be described in the DT.
>
>> i have below confusions about 'swctrl-gpios' of 'qcom,wcn7850-pmu'
>> which WCN7850 pin is 'swctrl-gpios' mean for ?
>> Why to introduce 'swctrl-gpios' ?
>> what problem does it solve ?
>> how to solve the problem ?
> Please descibe the hardware in the DT. Problem solving belongs to the
> driver.
sorry for not agreeing with your points here.
it is better to correct or remove 'swctrl-gpios' within DT binding spec at least
for 'qcom,wcn7850-pmu' with below reasons:
1) provided that 'swctrl-gpios' is for pin SW_CTRL of datasheet, binding spec's
both description and its expected usage are wrong.
2) its driver does not parse and use the property 'swctrl-gpios', moreover, the
property have no user within upstream DT tree.
3) the property is not mandatory based on binding spec.
4) upstream DT tree have had many such usages as mine which just set default pin
configuration and not specify 'swctrl-gpios' explicitly.
5) kaanapali-mtp is originally preinstalled with android OS which supports some
qualcomm specific feature which have not been supported by up-stream kernel.
so kaanapali-mtp H/W has some wired pins which is not used by up-stream
kernel sometimes
next prev parent reply other threads:[~2026-04-01 10:39 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-23 6:19 [PATCH 0/6] arm64: dts: qcom: kaanapali: Add PMIC dependent features Jingyi Wang
2026-03-23 6:19 ` [PATCH 1/6] arm64: dts: qcom: kaanapali: Add PMIC devices Jingyi Wang
2026-03-24 1:12 ` Dmitry Baryshkov
2026-03-25 11:04 ` Jishnu Prakash
2026-03-23 6:19 ` [PATCH 2/6] arm64: dts: qcom: kaanapali-mtp: Add PMIC support Jingyi Wang
2026-03-24 1:13 ` Dmitry Baryshkov
2026-03-25 11:05 ` Jishnu Prakash
2026-03-23 6:19 ` [PATCH 3/6] arm64: dts: qcom: kaanapali-qrd: " Jingyi Wang
2026-03-24 1:14 ` Dmitry Baryshkov
2026-03-23 6:19 ` [PATCH 4/6] arm64: dts: qcom: kaanapali-mtp: Enable bluetooth and Wifi Jingyi Wang
2026-03-24 1:16 ` Dmitry Baryshkov
2026-03-25 6:40 ` Zijun Hu
2026-03-25 7:08 ` Dmitry Baryshkov
2026-03-25 10:59 ` Zijun Hu
2026-03-25 11:40 ` Dmitry Baryshkov
2026-03-26 3:19 ` Zijun Hu
2026-03-26 4:10 ` Dmitry Baryshkov
2026-03-26 5:15 ` Zijun Hu
2026-03-30 11:53 ` Dmitry Baryshkov
2026-04-01 10:39 ` Zijun Hu [this message]
2026-04-01 11:08 ` Dmitry Baryshkov
2026-04-01 13:34 ` Zijun Hu
2026-04-01 14:07 ` Dmitry Baryshkov
2026-04-07 6:49 ` Zijun Hu
2026-03-23 6:19 ` [PATCH 5/6] arm64: dts: qcom: kaanapali: add display hardware devices Jingyi Wang
2026-03-24 1:20 ` Dmitry Baryshkov
2026-03-26 2:37 ` yuanjiey
2026-03-26 4:11 ` Dmitry Baryshkov
2026-03-23 6:19 ` [PATCH 6/6] arm64: dts: qcom: kaanapali-mtp: Enable display DSI devices Jingyi Wang
2026-03-24 1:25 ` Dmitry Baryshkov
2026-03-26 3:13 ` yuanjiey
2026-03-26 4:22 ` Dmitry Baryshkov
2026-03-23 14:38 ` [PATCH 0/6] arm64: dts: qcom: kaanapali: Add PMIC dependent features Bjorn Andersson
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=bf1df5d9-787c-40e9-93db-536612982427@oss.qualcomm.com \
--to=zijun.hu@oss.qualcomm.com \
--cc=20260224-knp-dts-misc-v6-0-79d20dab8a60@oss.qualcomm.com \
--cc=aiqun.yu@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=jingyi.wang@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=robh@kernel.org \
--cc=tingwei.zhang@oss.qualcomm.com \
--cc=trilok.soni@oss.qualcomm.com \
--cc=yijie.yang@oss.qualcomm.com \
/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