mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bjorn Andersson <andersson@kernel.org>
To: Konrad Dybcio <konradybcio@kernel.org>,
	Stephan Gerhold <stephan.gerhold@linaro.org>
Cc: Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, Sam Day <me@samcday.com>,
	Casey Connolly <casey.connolly@linaro.org>,
	Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Subject: Re: [PATCH v2 0/6] arm64: dts: qcom: msm8916/39: Cleanup/fix UART console pinctrl
Date: Wed,  7 May 2025 09:38:34 -0700	[thread overview]
Message-ID: <174663591263.3531.885721976162259110.b4-ty@kernel.org> (raw)
In-Reply-To: <20250422-msm8916-console-pinctrl-v2-0-f345b7a53c91@linaro.org>


On Tue, 22 Apr 2025 13:03:47 +0200, Stephan Gerhold wrote:
> At the moment, msm8916/39.dtsi have two inconsistent UART pinctrl templates
> that are used by all the boards:
> 
>  - &blsp_uart1_default configures all 4 pins (TX, RX, CTS, RTS), some
>    boards then limit this to just TX and RX
>  - &blsp_uart2_default only configures 2 pins (TX, RX), even though UART2
>    also supports CTS/RTS
> 
> [...]

Applied, thanks!

[1/6] arm64: dts: qcom: msm8916/39: Move UART pinctrl to board files
      commit: 8d88f6c9c5e774420673a37510b22015b1edd569
[2/6] arm64: dts: qcom: msm8916/39: Introduce new UART console pinctrl
      commit: 5c0c8b7a315ff63e01e9a608f78dea16daa57aed
[3/6] arm64: dts: qcom: msm8919/39: Use UART2 console pinctrl where appropriate
      commit: 2b8d22ef1687768e4b572d01cd2432eb86340dd1
[4/6] arm64: dts: qcom: msm8916-motorola: Use UART1 console pinctrl
      commit: fe848d64cc6516cd56f38d23cfb544a68231a6e8
[5/6] arm64: dts: qcom: msm8916: Drop generic UART pinctrl templates
      commit: 979b65d8f416353c6b44ec5c0ddc837b2d20ab47
[6/6] arm64: dts: qcom: msm8939: Drop generic UART pinctrl templates
      commit: f7f65536124db6a5666992f0d6fd9595fbbf067a

Best regards,
-- 
Bjorn Andersson <andersson@kernel.org>

      parent reply	other threads:[~2025-05-07 16:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-22 11:03 Stephan Gerhold
2025-04-22 11:03 ` [PATCH v2 1/6] arm64: dts: qcom: msm8916/39: Move UART pinctrl to board files Stephan Gerhold
2025-04-22 11:03 ` [PATCH v2 2/6] arm64: dts: qcom: msm8916/39: Introduce new UART console pinctrl Stephan Gerhold
2025-04-22 11:03 ` [PATCH v2 3/6] arm64: dts: qcom: msm8919/39: Use UART2 console pinctrl where appropriate Stephan Gerhold
2025-04-22 11:03 ` [PATCH v2 4/6] arm64: dts: qcom: msm8916-motorola: Use UART1 console pinctrl Stephan Gerhold
2025-04-22 11:03 ` [PATCH v2 5/6] arm64: dts: qcom: msm8916: Drop generic UART pinctrl templates Stephan Gerhold
2025-04-22 11:03 ` [PATCH v2 6/6] arm64: dts: qcom: msm8939: " Stephan Gerhold
2025-05-07 16:38 ` 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=174663591263.3531.885721976162259110.b4-ty@kernel.org \
    --to=andersson@kernel.org \
    --cc=casey.connolly@linaro.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=konrad.dybcio@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=me@samcday.com \
    --cc=robh@kernel.org \
    --cc=stephan.gerhold@linaro.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®