From: "Alexey Klimov" <alexey.klimov@linaro.org>
To: "Bjorn Andersson" <andersson@kernel.org>
Cc: "Konrad Dybcio" <konrad.dybcio@oss.qualcomm.com>,
"Linus Walleij" <linus.walleij@linaro.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Konrad Dybcio" <konradybcio@kernel.org>,
"Srinivas Kandagatla" <srini@kernel.org>,
"Dmitry Baryshkov" <dmitry.baryshkov@oss.qualcomm.com>,
<linux-arm-msm@vger.kernel.org>, <linux-gpio@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-sound@vger.kernel.org>
Subject: Re: [PATCH v2 3/4] arm64: dts: qcom: qcm2290: add LPASS LPI pin controller
Date: Tue, 21 Oct 2025 13:56:09 +0100 [thread overview]
Message-ID: <DDO0LYS7UTEW.3A9WGTAA5DKVO@linaro.org> (raw)
In-Reply-To: <zmi5grjg2znxddqzfsdsr35ad5olj3xgwwt6hvkiaynxzm5z33@gsgrdguj563n>
On Fri Oct 17, 2025 at 11:42 PM BST, Bjorn Andersson wrote:
> On Fri, Oct 10, 2025 at 01:29:38PM +0100, Alexey Klimov wrote:
>> On Tue Oct 7, 2025 at 1:39 PM BST, Konrad Dybcio wrote:
>> > On 10/7/25 4:03 AM, Alexey Klimov wrote:
>> >> Add the Low Power Audio SubSystem Low Power Island (LPASS LPI) pin
>> >> controller device node required for audio subsystem on Qualcomm
>> >> QRB2210 RB1. QRB2210 is based on qcm2290 which is based on sm6115.
>> >>
>> >> While at this, also add description of lpi_i2s2 pins (active state)
>> >> required for audio playback via HDMI/I2S.
>> >>
>> >> Cc: Srinivas Kandagatla <srini@kernel.org>
>> >> Signed-off-by: Alexey Klimov <alexey.klimov@linaro.org>
>> >> ---
>> >
>> > [...]
>> >
>> >> + lpi_i2s2_active: lpi-i2s2-active-state {
>> >> + data-pins {
>> >> + pins = "gpio12";
>> >> + function = "i2s2_data";
>> >> + bias-disable;
>> >> + drive-strength = <8>;
>> >> + output-high;
>> >
>> > I.. doubt output-high is what you want?
>>
>> Why? Or is it because of some in-kernel gpiod?
>>
>
> What does "output-high" mean for a non-gpio function?
This is not efficient. It will be more useful to go straight to
the point.
This description of pins was taken from Qualcomm downstream code
and the similar patch was applied (see provided URL in the prev email).
The same problem here and no response:
https://lore.kernel.org/linux-arm-msm/d8e202fb-f494-4b5e-bfb9-c94c1fd3af4d@linaro.org/
After looking at
https://lore.kernel.org/linux-arm-msm/39ebaf4e-e91f-4568-8de6-9fc1f805a1e4@oss.qualcomm.com/
I guess the output-high should removed at all (if it is the case) but it
will be more efficient to provide that as a feedback rather than vague
responses.
Back to your question -- does it matter here if it is gpio or non-gpio
function?
Best regards,
Alexey.
next prev parent reply other threads:[~2025-10-21 12:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-07 2:03 [PATCH v2 0/4] qrb2210-rb1: HDMI/I2S audio playback support Alexey Klimov
2025-10-07 2:03 ` [PATCH v2 1/4] dt-bindings: pinctrl: qcom,sm6115-lpass-lpi: add QCM2290 compatible Alexey Klimov
2025-10-13 12:29 ` Linus Walleij
2025-10-07 2:03 ` [PATCH v2 2/4] arm64: dts: qcom: qcm2290: add APR and its services Alexey Klimov
2025-10-07 2:03 ` [PATCH v2 3/4] arm64: dts: qcom: qcm2290: add LPASS LPI pin controller Alexey Klimov
2025-10-07 12:39 ` Konrad Dybcio
2025-10-10 12:29 ` Alexey Klimov
2025-10-17 22:42 ` Bjorn Andersson
2025-10-21 12:56 ` Alexey Klimov [this message]
2025-10-21 13:03 ` Dmitry Baryshkov
2025-10-21 13:13 ` Srinivas Kandagatla
2025-10-22 16:52 ` Alexey Klimov
2025-10-21 15:42 ` Alexey Klimov
2025-10-07 2:03 ` [PATCH v2 4/4] arm64: dts: qcom: qrb2210-rb1: add HDMI/I2S audio playback support Alexey Klimov
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=DDO0LYS7UTEW.3A9WGTAA5DKVO@linaro.org \
--to=alexey.klimov@linaro.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=robh@kernel.org \
--cc=srini@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;
as well as URLs for NNTP newsgroup(s).