From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Alexander Koskovich <akoskovich@pm.me>
Cc: Bjorn Andersson <andersson@kernel.org>,
Linus Walleij <linusw@kernel.org>,
linux-arm-msm@vger.kernel.org, linux-gpio@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC 1/2] pinctrl: qcom: eliza: Fix HDMI_RCV_DET function slot
Date: Mon, 8 Jun 2026 12:06:44 +0200 [thread overview]
Message-ID: <bfe4049e-d84e-4359-81b9-a4e68851b32d@oss.qualcomm.com> (raw)
In-Reply-To: <P33wW6i3eN15uYIbIb8LfIVRvmL0zVdiI_FOKDoMIM_KFi01m_7PMaZmU1z3YJl9mGN2kDtSvXUujD-TWaXXiSOZeEH-kwj3JSjmIRfRb54=@pm.me>
On 5/28/26 7:24 PM, Alexander Koskovich wrote:
> On Thursday, April 23rd, 2026 at 7:08 PM, Konrad Dybcio <konrad.dybcio@oss.qualcomm.com> wrote:
>
>> On 4/23/26 6:51 AM, Alexander Koskovich wrote:
>>> The hdmi_rcv_det function was placed at alt function slot 2, but the
>>> correct mux value for this function on GPIO 19 is slot 3. Move it
>>> accordingly and leave slot 2 unassigned.
>>
>> No, 2 is the desired one per docs
>>
>> 0 -> GPIO
>> 1 -> QUP2_SE5_L3
>> 2 -> HDMI_RCV_DET
>
> Is it possible that CQ7790S is a special case? The pin assignment I have for it
> here is:
>
> 0 -> GPIO
> 1 -> QUP2_SE5_L3
> 2 -> N/A
> 3 -> GP_PDM_MIRA[0]/HDMI_RCV_DET
I'll try to find an answer, even though I doubt it
Konrad
next prev parent reply other threads:[~2026-06-08 10:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-23 4:51 [PATCH RFC 0/2] pinctrl: qcom: eliza: Couple misc fixes Alexander Koskovich
2026-04-23 4:51 ` [PATCH RFC 1/2] pinctrl: qcom: eliza: Fix HDMI_RCV_DET function slot Alexander Koskovich
2026-04-23 8:47 ` Konrad Dybcio
2026-05-28 17:24 ` Alexander Koskovich
2026-06-08 10:06 ` Konrad Dybcio [this message]
2026-06-08 11:31 ` Konrad Dybcio
2026-06-08 18:41 ` Alexander Koskovich
2026-06-16 13:10 ` Konrad Dybcio
2026-04-23 4:51 ` [PATCH RFC 2/2] pinctrl: qcom: eliza: Fix QDSS trace clock/control pingroup names Alexander Koskovich
2026-04-23 8:49 ` Konrad Dybcio
2026-04-28 9:36 ` Linus Walleij
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=bfe4049e-d84e-4359-81b9-a4e68851b32d@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=akoskovich@pm.me \
--cc=andersson@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®