From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Bartosz Golaszewski <brgl@bgdev.pl>,
Linus Walleij <linus.walleij@linaro.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Alexey Klimov <alexey.klimov@linaro.org>
Cc: linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org,
Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Subject: Re: [PATCH RFC 3/5] pinctrl: qcom: sm8650: mark the `gpio` pin function as a non-strict function
Date: Wed, 2 Jul 2025 12:55:01 +0200 [thread overview]
Message-ID: <9c4005b7-8c01-4880-b0dd-5be4841616c7@oss.qualcomm.com> (raw)
In-Reply-To: <20250702-pinctrl-gpio-pinfuncs-v1-3-ed2bd0f9468d@linaro.org>
On 7/2/25 10:45 AM, Bartosz Golaszewski wrote:
> From: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
>
> Allow pins muxed to the "gpio" function to be requested as GPIOs even if
> pinmux_ops say the controller should be strict.
>
> Signed-off-by: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
> ---
fwiw this simple change could be a single 'run sed on all files' if
we decide to go with this approach
Konrad
next prev parent reply other threads:[~2025-07-02 10:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-02 8:45 [PATCH RFC 0/5] pinctrl: introduce the concept of a GPIO pin function category Bartosz Golaszewski
2025-07-02 8:45 ` [PATCH RFC 1/5] pinctrl: allow to mark pin functions as requestable GPIOs Bartosz Golaszewski
2025-07-02 8:45 ` [PATCH RFC 2/5] pinctrl: qcom: add infrastructure for marking pin functions as GPIOs Bartosz Golaszewski
2025-07-02 8:45 ` [PATCH RFC 3/5] pinctrl: qcom: sm8650: mark the `gpio` pin function as a non-strict function Bartosz Golaszewski
2025-07-02 10:55 ` Konrad Dybcio [this message]
2025-07-02 22:50 ` Dmitry Baryshkov
2025-07-03 8:17 ` Bartosz Golaszewski
2025-07-04 16:50 ` Dmitry Baryshkov
2025-07-02 8:45 ` [PATCH RFC 4/5] pinctrl: qcom: sc8280xp: " Bartosz Golaszewski
2025-07-02 8:45 ` [PATCH RFC 5/5] pinctrl: qcom: make the pinmuxing strict Bartosz Golaszewski
2025-07-02 11:03 ` [PATCH RFC 0/5] pinctrl: introduce the concept of a GPIO pin function category Konrad Dybcio
2025-07-03 22:39 ` 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=9c4005b7-8c01-4880-b0dd-5be4841616c7@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=alexey.klimov@linaro.org \
--cc=andersson@kernel.org \
--cc=bartosz.golaszewski@linaro.org \
--cc=brgl@bgdev.pl \
--cc=konradybcio@kernel.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 \
/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®