From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Konrad Dybcio <konrad.dybcio@linaro.org>,
Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Vinod Koul <vkoul@kernel.org>,
linux-arm-msm@vger.kernel.org, linux-gpio@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] arm64: dts: qcom: sm8350-hdk: correct LT9611 pin function
Date: Thu, 2 Feb 2023 10:36:17 +0100 [thread overview]
Message-ID: <b9d56f59-ad43-1a09-0c9c-b85b732c7d99@linaro.org> (raw)
In-Reply-To: <87f4ba93-e566-821b-8f12-8765436e0791@linaro.org>
On 01/02/2023 16:47, Konrad Dybcio wrote:
>
>
> On 1.02.2023 16:43, Krzysztof Kozlowski wrote:
>> SM8350 pin controller does not have "normal" pin function, so use
>> "gpio".
>>
>> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
>> ---
> Makes one wonder if it was ever tested, as this would have probably
> failed when setting pinctrl settings..
>
> Reviewed-by: Konrad Dybcio <konrad.dybcio@linaro.org>
Fixes: d96d8f9192be ("arm64: dts: qcom: sm8350-hdk: Enable lt9611uxc dsi-hdmi bridge")
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-02-02 9:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-01 15:43 [PATCH 1/3] arm64: dts: qcom: sm8350-hdk: align pin config node names with bindings Krzysztof Kozlowski
2023-02-01 15:43 ` [PATCH 2/3] arm64: dts: qcom: sm8350-hdk: correct LT9611 pin function Krzysztof Kozlowski
2023-02-01 15:47 ` Konrad Dybcio
2023-02-02 9:36 ` Krzysztof Kozlowski [this message]
2023-02-01 15:43 ` [PATCH 3/3] dt-bindings: pinctrl: qcom,sm8350: add input-disable Krzysztof Kozlowski
2023-02-02 23:47 ` Rob Herring
2023-02-03 7:17 ` (subset) " Krzysztof Kozlowski
2023-02-01 15:46 ` [PATCH 1/3] arm64: dts: qcom: sm8350-hdk: align pin config node names with bindings Konrad Dybcio
2023-02-02 9:36 ` Krzysztof Kozlowski
2023-02-09 4:23 ` (subset) " 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=b9d56f59-ad43-1a09-0c9c-b85b732c7d99@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.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=robh+dt@kernel.org \
--cc=vkoul@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).