From: Krzysztof Kozlowski <krzk@kernel.org>
To: Ajay Kumar Nandam <ajay.nandam@oss.qualcomm.com>,
Bjorn Andersson <andersson@kernel.org>,
Linus Walleij <linusw@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, linux-gpio@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] pinctrl: qcom: lpass-lpi: drop unused runtime-PM write helper
Date: Wed, 10 Jun 2026 10:25:02 +0200 [thread overview]
Message-ID: <f03850f6-186d-4988-a450-e6e95f24a551@kernel.org> (raw)
In-Reply-To: <20260610080809.2588640-1-ajay.nandam@oss.qualcomm.com>
On 10/06/2026 10:08, Ajay Kumar Nandam wrote:
> lpi_gpio_write() became unused after the PM clock runtime conversion
> switched write paths to __lpi_gpio_write() inside callers that already
> hold an active runtime-PM reference.
>
> With -Werror this triggers:
> error: 'lpi_gpio_write' defined but not used [-Wunused-function]
>
> Remove the dead wrapper.
>
> Fixes: b719ede389d8 ("pinctrl: qcom: lpass-lpi: Switch to PM clock framework for runtime PM")
Please add Reported-by credits, at least Nathan as he bisected it.
> Signed-off-by: Ajay Kumar Nandam <ajay.nandam@oss.qualcomm.com>
> ---
> drivers/pinctrl/qcom/pinctrl-lpass-lpi.c | 14 --------------
> 1 file changed, 14 deletions(-)
>
> diff --git a/drivers/pinctrl/qcom/pinctrl-lpass-lpi.c b/drivers/pinctrl/qcom/pinctrl-lpass-lpi.c
> index 4d758fd117c4..fe7ec0176081 100644
> --- a/drivers/pinctrl/qcom/pinctrl-lpass-lpi.c
> +++ b/drivers/pinctrl/qcom/pinctrl-lpass-lpi.c
> @@ -79,20 +79,6 @@ static int lpi_gpio_read(struct lpi_pinctrl *state, unsigned int pin,
> return pm_runtime_put_autosuspend(state->dev);
> }
>
> -static int lpi_gpio_write(struct lpi_pinctrl *state, unsigned int pin,
> - unsigned int addr, unsigned int val)
So why do we need __lpi_gpio_write()?
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-06-10 8:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-10 8:08 Ajay Kumar Nandam
2026-06-10 8:25 ` Krzysztof Kozlowski [this message]
2026-06-10 8:57 ` Ajay Kumar Nandam
2026-06-10 9:00 ` Krzysztof Kozlowski
2026-06-10 9:14 ` Ajay Kumar Nandam
2026-06-10 18:11 ` Ajay Kumar Nandam
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=f03850f6-186d-4988-a450-e6e95f24a551@kernel.org \
--to=krzk@kernel.org \
--cc=ajay.nandam@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 \
/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®