[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <bb0bc61a-8c2b-affa-c58a-1e7c14f9390d@ti.com>
Date: Fri, 8 Feb 2019 18:04:43 +0530
From: Sekhar Nori <nsekhar@...com>
To: Bartosz Golaszewski <brgl@...ev.pl>,
Kevin Hilman <khilman@...nel.org>,
Daniel Lezcano <daniel.lezcano@...aro.org>,
Rob Herring <robh+dt@...nel.org>,
Mark Rutland <mark.rutland@....com>,
Thomas Gleixner <tglx@...utronix.de>
CC: <linux-arm-kernel@...ts.infradead.org>,
<linux-kernel@...r.kernel.org>, <devicetree@...r.kernel.org>,
Bartosz Golaszewski <bgolaszewski@...libre.com>
Subject: Re: [PATCH v2 08/12] ARM: davinci: dm355: switch to using the
clocksource driver
On 04/02/19 10:47 PM, Bartosz Golaszewski wrote:
> -/*
> - * T0_BOT: Timer 0, bottom: clockevent source for hrtimers
> - * T0_TOP: Timer 0, top : clocksource for generic timekeeping
> - * T1_BOT: Timer 1, bottom: (used by DSP in TI DSPLink code)
> - * T1_TOP: Timer 1, top : <unused>
Documenting this timer division is important because DSP usage and
unused timers are not immediately clear from kernel code alone. Can you
retain these comments in all patches of this series (I guess T0_BOT etc.
terminology is changed, so feel free to adjust the comment text).
> - */
> -static struct davinci_timer_info dm355_timer_info = {
> - .timers = davinci_timer_instance,
> - .clockevent_id = T0_BOT,
> - .clocksource_id = T0_TOP,
> +static const struct davinci_timer_cfg dm355_timer_cfg = {
> + .reg = {
> + .start = DAVINCI_TIMER0_BASE,
> + .end = DAVINCI_TIMER0_BASE + SZ_4K,
Here and other places too, SZ_4K - 1
Thanks,
Sekhar
Powered by blists - more mailing lists