From: Tony Lindgren <tony@atomide.com>
To: Ivaylo Dimitrov <ivo.g.dimitrov.75@gmail.com>
Cc: daniel.lezcano@linaro.org, tglx@linutronix.de,
linux-kernel@vger.kernel.org, sean@mess.org
Subject: Re: [PATCH] drivers/clocksource/timer-ti-dm: Don't call clk_get_rate() in stop function
Date: Tue, 3 Oct 2023 10:57:08 +0300 [thread overview]
Message-ID: <20231003075708.GA34982@atomide.com> (raw)
In-Reply-To: <1696312220-11550-1-git-send-email-ivo.g.dimitrov.75@gmail.com>
* Ivaylo Dimitrov <ivo.g.dimitrov.75@gmail.com> [231003 05:50]:
> clk_get_rate() might sleep, and that prevents dm-timer based PWM from being
> used from atomic context.
>
> Fix that by getting fclk rate in probe() and using a notifier in case rate
> changes.
Makes sense to me:
Reviewed-by: Tony Lindgren <tony@atomide.com>
next prev parent reply other threads:[~2023-10-03 7:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-03 5:50 [PATCH] drivers/clocksource/timer-ti-dm: Don't call clk_get_rate() in stop function Ivaylo Dimitrov
2023-10-03 7:57 ` Tony Lindgren [this message]
2023-10-27 18:23 ` [tip: timers/core] " tip-bot2 for Ivaylo Dimitrov
2024-01-13 16:26 ` [PATCH] " Sean Young
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=20231003075708.GA34982@atomide.com \
--to=tony@atomide.com \
--cc=daniel.lezcano@linaro.org \
--cc=ivo.g.dimitrov.75@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sean@mess.org \
--cc=tglx@linutronix.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