From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Dan Carpenter <dan.carpenter@linaro.org>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Alim Akhtar <alim.akhtar@samsung.com>,
Thierry Reding <thierry.reding@gmail.com>,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, linux-pwm@vger.kernel.org,
kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] pwm: samsung: Fix a bit test
Date: Tue, 24 Oct 2023 23:11:57 +0200 [thread overview]
Message-ID: <20231024211157.xv3vzqlmxmxwgvle@pengutronix.de> (raw)
In-Reply-To: <917e3890-7895-4b1c-bcee-4eecb3b7fe09@moroto.mountain>
[-- Attachment #1.1: Type: text/plain, Size: 2677 bytes --]
Hello Dan,
On Tue, Oct 17, 2023 at 05:04:08PM +0300, Dan Carpenter wrote:
> This code has two problems. First, it passes the wrong bit parameter to
> test_bit(). Second, it mixes using PWMF_REQUESTED in test_bit() and in
> open coded bit tests.
>
> The test_bit() function takes a bit number. In other words,
> "if (test_bit(0, &flags))" is the equivalent of "if (flags & (1 << 0))".
> Passing (1 << 0) to test_bit() is like writing BIT(BIT(0)). It's a
> double shift bug.
>
> In pwm_samsung_resume() these issues mean that the flag is never set and
> the function is essentially a no-op.
>
> Fixes: 4c9548d24c0d ("pwm: samsung: Put per-channel data into driver data")
> Signed-off-by: Dan Carpenter <dan.carpenter@linaro.org>
> ---
> From static analysis and not tested.
>
> drivers/pwm/pwm-samsung.c | 2 +-
> include/linux/pwm.h | 4 ++--
> 2 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/pwm/pwm-samsung.c b/drivers/pwm/pwm-samsung.c
> index 10fe2c13cd80..acf4a0d8d990 100644
> --- a/drivers/pwm/pwm-samsung.c
> +++ b/drivers/pwm/pwm-samsung.c
> @@ -630,7 +630,7 @@ static int pwm_samsung_resume(struct device *dev)
> struct pwm_device *pwm = &chip->pwms[i];
> struct samsung_pwm_channel *chan = &our_chip->channel[i];
>
> - if (!(pwm->flags & PWMF_REQUESTED))
> + if (!test_bit(PWMF_REQUESTED, &pwm->flags))
> continue;
>
> if (our_chip->variant.output_mask & BIT(i))
> diff --git a/include/linux/pwm.h b/include/linux/pwm.h
> index e3b437587b32..3eee5bf367fb 100644
> --- a/include/linux/pwm.h
> +++ b/include/linux/pwm.h
> @@ -41,8 +41,8 @@ struct pwm_args {
> };
>
> enum {
> - PWMF_REQUESTED = 1 << 0,
> - PWMF_EXPORTED = 1 << 1,
> + PWMF_REQUESTED = 0,
> + PWMF_EXPORTED = 1,
I'd want s/ / / here. Or even not assign explicit values at all?
> };
>
> /*
I'd say these are two separate issues, with the one in pwm-samsung being
bad and the one in <linux/pwm.h> "only" ugly.
I wonder how I could get the samsung part wrong. All current usages of
PMWF_REQUESTED (and also PWMF_EXPORTED) use test_bit (et al). Grepping
through history pwm-pca9685.c got this wrong in a similar way for some
time, but otherwise it was always used correctly.
The definition of the flags in <linux/pwm.h> is ugly since
f051c466cf69 ("pwm: Allow chips to support multiple PWMs") from 2011!
@Dan: Would you split the patch in two please?
Thanks for catching that!
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | https://www.pengutronix.de/ |
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-10-24 21:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-17 14:04 [PATCH] pwm: samsung: Fix a bit test Dan Carpenter
2023-10-24 21:11 ` Uwe Kleine-König [this message]
2023-10-25 4:18 ` Dan Carpenter
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=20231024211157.xv3vzqlmxmxwgvle@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=alim.akhtar@samsung.com \
--cc=dan.carpenter@linaro.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pwm@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=thierry.reding@gmail.com \
/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