From: Guiting Shen <aarongt.shen@gmail.com>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: claudiu.beznea@microchip.com, u.kleine-koenig@pengutronix.de,
nicolas.ferre@microchip.com, alexandre.belloni@bootlin.com,
linux-arm-kernel@lists.infradead.org, linux-pwm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6] pwm: atmel: Enable clk when pwm already enabled in bootloader
Date: Fri, 21 Jul 2023 11:23:15 +0800 [thread overview]
Message-ID: <c79d5a16-2716-6cd8-8b6a-f0e5916a65cf@gmail.com> (raw)
In-Reply-To: <ZLlO3vGr-ECdnmKA@orome>
On Thu, Jul 20, 2023 at 23:12:30PM GMT+8, Thierry Reding wrote:
> On Sun, Jul 16, 2023 at 10:06:52AM +0800, Guiting Shen wrote:
>> The driver would never call clk_enable() if the PWM channel was already
>> enabled in bootloader which lead to dump the warning message "the PWM
>> clock already disabled" when turning off the PWM channel.
>>
>> Add atmel_pwm_enable_clk_if_on() in probe function to enable clock if
>> the PWM channel was already enabled in bootloader.
>>
>> Signed-off-by: Guiting Shen <aarongt.shen@gmail.com>
>> ---
>> drivers/pwm/pwm-atmel.c | 47 +++++++++++++++++++++++++++++++++++++++--
>> 1 file changed, 45 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/pwm/pwm-atmel.c b/drivers/pwm/pwm-atmel.c
>> index cdbc23649032..fc89282db645 100644
>> --- a/drivers/pwm/pwm-atmel.c
>> +++ b/drivers/pwm/pwm-atmel.c
>> @@ -36,7 +36,7 @@
>> #define PWM_SR 0x0C
>> #define PWM_ISR 0x1C
>> /* Bit field in SR */
>> -#define PWM_SR_ALL_CH_ON 0x0F
>> +#define PWM_SR_ALL_CH_MASK 0x0F
>>
>> /* The following register is PWM channel related registers */
>> #define PWM_CH_REG_OFFSET 0x200
>> @@ -464,6 +464,42 @@ static const struct of_device_id atmel_pwm_dt_ids[] = {
>> };
>> MODULE_DEVICE_TABLE(of, atmel_pwm_dt_ids);
>>
>> +static int atmel_pwm_enable_clk_if_on(struct atmel_pwm_chip *atmel_pwm, bool on)
>> +{
>> + unsigned int i, cnt = 0;
>> + int ret = 0;
>> + u32 sr;
>> +
>> + sr = atmel_pwm_readl(atmel_pwm, PWM_SR) & PWM_SR_ALL_CH_MASK;
>> + if (!sr)
>> + return 0;
>> +
>> + cnt = bitmap_weight((unsigned long *)&sr, atmel_pwm->chip.npwm);
>
> Tiny nit here: not sure if that cast is safe to do. You've got a 32-bit
> variable, but if you cast &sr to unsigned long * on a 64-bit machine it
> would cause hweight64() to get called and that would then read 64 bits
> from a 32-bit variable. This probably works most of the time because we
> don't read any of the upper bits, but it is strictly an illegal access
> and could be unaligned as well.
I found that the CONFIG_PWM_ATMEL was only in arch/arm/configs directory
which seems that the pwm-atmel driver only run in 32-bit soc machine.
> Should we just turn sr into an unsigned long to be safe here? No need to
> resend, I can make that change when I apply.
Yes, It is safer by doing this. Thank you.
--
Regards,
Guiting Shen
next prev parent reply other threads:[~2023-07-21 3:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-16 2:06 Guiting Shen
2023-07-16 13:17 ` claudiu beznea
2023-07-20 15:12 ` Thierry Reding
2023-07-21 3:23 ` Guiting Shen [this message]
2023-07-21 5:49 ` Uwe Kleine-König
2023-07-21 12:39 ` Thierry Reding
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=c79d5a16-2716-6cd8-8b6a-f0e5916a65cf@gmail.com \
--to=aarongt.shen@gmail.com \
--cc=alexandre.belloni@bootlin.com \
--cc=claudiu.beznea@microchip.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=nicolas.ferre@microchip.com \
--cc=thierry.reding@gmail.com \
--cc=u.kleine-koenig@pengutronix.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®