From: Bjorn Andersson <andersson@kernel.org>
To: linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, agross@kernel.org,
krzysztof.kozlowski@linaro.org, linus.walleij@linaro.org,
robh+dt@kernel.org, linux-arm-msm@vger.kernel.org,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Konrad Dybcio <konrad.dybcio@somainline.org>
Subject: Re: (subset) [PATCH v2 1/4] arm64: dts: qcom: sdm630: add UART pin functions
Date: Mon, 17 Oct 2022 22:05:38 -0500 [thread overview]
Message-ID: <166606235861.3553294.8390135332228667844.b4-ty@kernel.org> (raw)
In-Reply-To: <20221011190231.76784-1-krzysztof.kozlowski@linaro.org>
On Tue, 11 Oct 2022 15:02:28 -0400, Krzysztof Kozlowski wrote:
> Configure UART1 and UART2 pins to respective functions in default state,
> otherwise the pins might stay as GPIOs.
>
>
Applied, thanks!
[1/4] arm64: dts: qcom: sdm630: add UART pin functions
commit: 804ec4dad48c4fc7844c66b5febe9dbc6198f8b5
[2/4] arm64: dts: qcom: sdm630: correct I2C8 pin functions
commit: 06783c3ae8899aa71abc795d3d6490a4afa9ed99
[3/4] arm64: dts: qcom: sdm630: align TLMM pin configuration with DT schema
commit: 048a765ac5712397cb58e374a7e1087c34875b5f
Best regards,
--
Bjorn Andersson <andersson@kernel.org>
prev parent reply other threads:[~2022-10-18 3:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-11 19:02 [PATCH v2 1/4] arm64: dts: qcom: sdm630: add UART pin functions Krzysztof Kozlowski
2022-10-11 19:02 ` [PATCH v2 2/4] arm64: dts: qcom: sdm630: correct I2C8 " Krzysztof Kozlowski
2022-10-11 19:02 ` [PATCH v2 3/4] arm64: dts: qcom: sdm630: align TLMM pin configuration with DT schema Krzysztof Kozlowski
2022-10-11 19:02 ` [PATCH v2 4/4] dt-bindings: pinctrl: qcom,sdm630: convert to dtschema Krzysztof Kozlowski
2022-10-17 22:51 ` Bjorn Andersson
2022-10-17 23:01 ` (subset) " Krzysztof Kozlowski
2022-10-18 3:05 ` Bjorn Andersson [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=166606235861.3553294.8390135332228667844.b4-ty@kernel.org \
--to=andersson@kernel.org \
--cc=agross@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@somainline.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@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 \
/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).