From: Bjorn Andersson <andersson@kernel.org>
To: Andrew Halaney <ahalaney@redhat.com>
Cc: konrad.dybcio@linaro.org, quic_shazhuss@quicinc.com,
agross@kernel.org, devicetree@vger.kernel.org,
bmasney@redhat.com, robh+dt@kernel.org,
linux-kernel@vger.kernel.org, krzysztof.kozlowski+dt@linaro.org,
linux-arm-msm@vger.kernel.org
Subject: Re: (subset) [PATCH v2 1/2] arm64: dts: qcom: sa8540p-ride: Fix some i2c pinctrl settings
Date: Wed, 8 Feb 2023 20:22:35 -0800 [thread overview]
Message-ID: <167591660368.1230100.10469557592442274107.b4-ty@kernel.org> (raw)
In-Reply-To: <20230130154823.117542-1-ahalaney@redhat.com>
On Mon, 30 Jan 2023 09:48:22 -0600, Andrew Halaney wrote:
> Some of the pinctrl groups were invalid for the selected pins. Select
> the proper qup group to fix these warnings:
>
> [ 6.523566] sc8280xp-tlmm f100000.pinctrl: invalid group "gpio135" for function "qup15"
> [ 6.535042] sc8280xp-tlmm f100000.pinctrl: invalid group "gpio136" for function "qup15"
> [ 6.597536] sc8280xp-tlmm f100000.pinctrl: invalid group "gpio158" for function "qup15"
> [ 6.597544] sc8280xp-tlmm f100000.pinctrl: invalid group "gpio159" for function "qup15"
> [ 6.597991] sc8280xp-tlmm f100000.pinctrl: invalid group "gpio0" for function "qup15"
> [ 6.597996] sc8280xp-tlmm f100000.pinctrl: invalid group "gpio1" for function "qup15"
>
> [...]
Applied, thanks!
[1/2] arm64: dts: qcom: sa8540p-ride: Fix some i2c pinctrl settings
commit: f187e989305a2d57dc0f750ebb63959151b66924
[2/2] arm64: dts: qcom: sa8540p-ride: Document i2c busses
commit: f1d6f9d227a0fe887d6a5cc7773425b267e4deff
Best regards,
--
Bjorn Andersson <andersson@kernel.org>
prev parent reply other threads:[~2023-02-09 4:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-30 15:48 [PATCH v2 1/2] arm64: dts: qcom: sa8540p-ride: Fix some i2c pinctrl settings Andrew Halaney
2023-01-30 15:48 ` [PATCH v2 2/2] arm64: dts: qcom: sa8540p-ride: Document i2c busses Andrew Halaney
2023-01-31 21:34 ` Eric Chanudet
2023-02-09 4:22 ` 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=167591660368.1230100.10469557592442274107.b4-ty@kernel.org \
--to=andersson@kernel.org \
--cc=agross@kernel.org \
--cc=ahalaney@redhat.com \
--cc=bmasney@redhat.com \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_shazhuss@quicinc.com \
--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