From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Hans Ulli Kroll <linux@ulli-kroll.de>,
Linus Walleij <linusw@kernel.org>,
Bjorn Andersson <andersson@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, linux-gpio@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] pinctrl: qcom: ipq806x: mark pci reset as a GPIO pin function
Date: Mon, 20 Jul 2026 10:28:31 +0200 [thread overview]
Message-ID: <fec76d4a-c370-449a-a6c9-910703c70bfb@oss.qualcomm.com> (raw)
In-Reply-To: <20260719134548.8830-3-linux@ulli-kroll.de>
On 7/19/26 3:36 PM, Hans Ulli Kroll wrote:
> The qcom pinctrl core supports marking functions that represent GPIO mode
> via PINCTRL_GPIO_PINFUNCTION(), so that strict pinmuxing does not reject
> GPIO requests for pins that are muxed to the GPIO function.
>
> Mark PCIe reset as GPIO pin function
>
> This allows ipq806x to keep the PCIe-reset related configuration in DTS
> without tripping over strict pinmux ownership checks.
Could you expand on what the issue is? We haven't seen this being
necessary on other platforms
Konrad
next prev parent reply other threads:[~2026-07-20 8:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-19 13:35 [PATCH 0/2] pinctrl: qcom: ipq806x: mark gpio and pcie-reset as GPIO Hans Ulli Kroll
2026-07-19 13:35 ` [PATCH 1/2] pinctrl: qcom: ipq806x: mark gpio as a GPIO pin function Hans Ulli Kroll
2026-07-20 8:29 ` Konrad Dybcio
2026-07-22 13:22 ` Dmitry Baryshkov
2026-07-25 9:42 ` Linus Walleij
2026-07-19 13:36 ` [PATCH 2/2] pinctrl: qcom: ipq806x: mark pci reset " Hans Ulli Kroll
2026-07-20 8:28 ` Konrad Dybcio [this message]
2026-07-22 13:22 ` Dmitry Baryshkov
2026-07-25 9:42 ` Linus Walleij
2026-07-25 9:20 ` [PATCH 0/2] pinctrl: qcom: ipq806x: mark gpio and pcie-reset as GPIO Linus Walleij
2026-07-28 9:11 ` Bartosz Golaszewski
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=fec76d4a-c370-449a-a6c9-910703c70bfb@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--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 \
--cc=linux@ulli-kroll.de \
/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®