From: Julien Thierry <julien.thierry@arm.com>
To: Benjamin Gaignard <benjamin.gaignard@linaro.org>,
robh+dt@kernel.org, mark.rutland@arm.com, linux@armlinux.org.uk,
mcoquelin.stm32@gmail.com, alexandre.torgue@st.com,
daniel.lezcano@linaro.org, tglx@linutronix.de,
ludovic.barre@st.com
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 2/4] clocksource: stm32: only use 32 bits timers
Date: Wed, 18 Oct 2017 09:21:50 +0100 [thread overview]
Message-ID: <78e4bf06-7e95-d863-3b3d-c7362643da90@arm.com> (raw)
In-Reply-To: <1508312614-27750-3-git-send-email-benjamin.gaignard@linaro.org>
On 18/10/17 08:43, Benjamin Gaignard wrote:
> 16 bits hardware are not enough accure to be used.
> Do no allow them to be probed by tested max counter value.
>
> Signed-off-by: Benjamin Gaignard <benjamin.gaignard@linaro.org>
> ---
> drivers/clocksource/timer-stm32.c | 23 +++++++++--------------
> 1 file changed, 9 insertions(+), 14 deletions(-)
>
> diff --git a/drivers/clocksource/timer-stm32.c b/drivers/clocksource/timer-stm32.c
> index abff21c..f7e4eec 100644
> --- a/drivers/clocksource/timer-stm32.c
> +++ b/drivers/clocksource/timer-stm32.c
> @@ -81,9 +81,9 @@ static irqreturn_t stm32_clock_event_handler(int irq, void *dev_id)
> static int __init stm32_clockevent_init(struct device_node *node)
> {
> struct reset_control *rstc;
> - unsigned long max_delta;
> - int ret, bits, prescaler = 1;
> + unsigned long max_arr;
> struct timer_of *to;
> + int ret;
>
> to = kzalloc(sizeof(*to), GFP_KERNEL);
> if (!to)
> @@ -113,26 +113,21 @@ static int __init stm32_clockevent_init(struct device_node *node)
>
> /* Detect whether the timer is 16 or 32 bits */
> writel_relaxed(~0U, timer_of_base(to) + TIM_ARR);
> - max_delta = readl_relaxed(timer_of_base(to) + TIM_ARR);
> - if (max_delta == ~0U) {
> - prescaler = 1;
> - bits = 32;
> - } else {
> - prescaler = 1024;
> - bits = 16;
> + max_arr = readl_relaxed(timer_of_base(to) + TIM_ARR);
> + if (max_arr != ~0U) {
> + pr_err("32 bits timer is needed\n");
> + return -EINVAL;
Same as with previous patch, I think "to" should get freed.
Also, why is there no function to undo what timer_of_init did? Shouldn't
we be able to free the irqs and unmap the timer io base here?
Cheers,
--
Julien Thierry
next prev parent reply other threads:[~2017-10-18 8:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-18 7:43 [PATCH v5 0/4] stm32 clocksource driver rework Benjamin Gaignard
2017-10-18 7:43 ` [PATCH v5 1/4] clocksource: stm32: convert driver to timer_of Benjamin Gaignard
2017-10-18 8:10 ` Julien Thierry
2017-10-18 7:43 ` [PATCH v5 2/4] clocksource: stm32: only use 32 bits timers Benjamin Gaignard
2017-10-18 8:21 ` Julien Thierry [this message]
2017-10-18 12:25 ` Benjamin Gaignard
2017-10-18 7:43 ` [PATCH v5 3/4] clocksource: stm32: add clocksource support Benjamin Gaignard
2017-10-18 7:43 ` [PATCH v5 4/4] arm: dts: stm32: remove useless clocksource nodes Benjamin Gaignard
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=78e4bf06-7e95-d863-3b3d-c7362643da90@arm.com \
--to=julien.thierry@arm.com \
--cc=alexandre.torgue@st.com \
--cc=benjamin.gaignard@linaro.org \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=ludovic.barre@st.com \
--cc=mark.rutland@arm.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=robh+dt@kernel.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
all inboxes | Powered by JetHome®