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>,
Lorenzo Bianconi <lorenzo@kernel.org>,
Sean Wang <sean.wang@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Paul Cercueil <paul@crapouillou.net>,
Luca Weiss <luca.weiss@fairphone.com>
Cc: linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org,
linux-mediatek@lists.infradead.org,
linux-arm-kernel@lists.infradead.org, linux-mips@vger.kernel.org,
Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Subject: Re: [PATCH v2 11/12] pinctrl: qcom: mark the `gpio` and `egpio` pins function as non-strict functions
Date: Wed, 9 Jul 2025 20:03:30 +0200 [thread overview]
Message-ID: <68dfc6b7-1083-44dc-bdaf-4fc09e944671@oss.qualcomm.com> (raw)
In-Reply-To: <20250709-pinctrl-gpio-pinfuncs-v2-11-b6135149c0d9@linaro.org>
On 7/9/25 4:39 PM, Bartosz Golaszewski wrote:
> From: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
>
> Allow pins muxed to the "gpio" or "egpio" 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>
> ---
Reviewed-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
heads up for +Luca, I'm not sure how your Milos addition will
stack up chronologically
Konrad
next prev parent reply other threads:[~2025-07-09 21:58 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-09 14:38 [PATCH v2 00/12] pinctrl: introduce the concept of a GPIO pin function category Bartosz Golaszewski
2025-07-09 14:38 ` [PATCH v2 01/12] pinctrl: pinmux: open-code PINCTRL_FUNCTION_DESC() Bartosz Golaszewski
2025-07-10 20:37 ` Bjorn Andersson
2025-07-09 14:38 ` [PATCH v2 02/12] pinctrl: provide pinmux_generic_add_pinfunction() Bartosz Golaszewski
2025-07-09 14:38 ` [PATCH v2 03/12] pinctrl: equilibrium: use pinmux_generic_add_pinfunction() Bartosz Golaszewski
2025-07-09 14:39 ` [PATCH v2 04/12] pinctrl: airoha: " Bartosz Golaszewski
2025-07-09 14:39 ` [PATCH v2 05/12] pinctrl: mediatek: moore: " Bartosz Golaszewski
2025-07-09 14:39 ` [PATCH v2 06/12] pinctrl: keembay: " Bartosz Golaszewski
2025-07-09 14:39 ` [PATCH v2 07/12] pinctrl: ingenic: " Bartosz Golaszewski
2025-07-09 21:25 ` Paul Cercueil
2025-07-09 14:39 ` [PATCH v2 08/12] pinctrl: qcom: use generic pin function helpers Bartosz Golaszewski
2025-07-10 12:25 ` Konrad Dybcio
2025-07-10 13:38 ` Bartosz Golaszewski
2025-07-11 12:19 ` Konrad Dybcio
2025-07-11 18:37 ` Linus Walleij
2025-07-13 8:43 ` Bartosz Golaszewski
2025-07-09 14:39 ` [PATCH v2 09/12] pinctrl: allow to mark pin functions as requestable GPIOs Bartosz Golaszewski
2025-07-14 11:29 ` Heiko Stübner
2025-07-09 14:39 ` [PATCH v2 10/12] pinctrl: qcom: add infrastructure for marking pin functions as GPIOs Bartosz Golaszewski
2025-07-09 18:04 ` Konrad Dybcio
2025-07-09 14:39 ` [PATCH v2 11/12] pinctrl: qcom: mark the `gpio` and `egpio` pins function as non-strict functions Bartosz Golaszewski
2025-07-09 18:03 ` Konrad Dybcio [this message]
2025-07-09 14:39 ` [PATCH v2 12/12] pinctrl: qcom: make the pinmuxing strict Bartosz Golaszewski
2025-07-10 12:26 ` Konrad Dybcio
2025-07-19 16:02 ` [PATCH v2 00/12] pinctrl: introduce the concept of a GPIO pin function category 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=68dfc6b7-1083-44dc-bdaf-4fc09e944671@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=alexey.klimov@linaro.org \
--cc=andersson@kernel.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=bartosz.golaszewski@linaro.org \
--cc=brgl@bgdev.pl \
--cc=konradybcio@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-mips@vger.kernel.org \
--cc=lorenzo@kernel.org \
--cc=luca.weiss@fairphone.com \
--cc=matthias.bgg@gmail.com \
--cc=paul@crapouillou.net \
--cc=sean.wang@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