[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <acd3f8ca-8ed7-f86a-9bdf-24e4e6e9a6a4@ti.com>
Date: Fri, 8 Feb 2019 18:07:35 +0530
From: Sekhar Nori <nsekhar@...com>
To: Bartosz Golaszewski <bgolaszewski@...libre.com>
CC: 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>,
arm-soc <linux-arm-kernel@...ts.infradead.org>,
LKML <linux-kernel@...r.kernel.org>,
linux-devicetree <devicetree@...r.kernel.org>
Subject: Re: [PATCH v2 05/12] ARM: davinci: da850: switch to using the
clocksource driver
On 08/02/19 6:04 PM, Bartosz Golaszewski wrote:
> pt., 8 lut 2019 o 13:06 Sekhar Nori <nsekhar@...com> napisaĆ(a):
>>
>> On 04/02/19 10:47 PM, Bartosz Golaszewski wrote:
>>> +static const struct davinci_timer_cfg da850_timer_cfg = {
>>> + .reg = {
>>> + .start = DA8XX_TIMER64P0_BASE,
>>> + .end = DA8XX_TIMER64P0_BASE + SZ_4K,
>>
>> SZ_4K - 1
>>
>> This should have prevented watchdog timer from getting registered.
>>
>> Thanks,
>> Sekhar
>
> My clocksource driver doesn't call request_region() so a subsequent
> devm_ioremap_resource() in the watchdog driver would still succeed. I
> now fixed both the missing call and the value here.
Ah, got it. Perhaps a call to request_region() should be added to catch
issues?
Thanks,
Sekhar
Powered by blists - more mailing lists