[PATCH 6/7] drivers/clocksource/timer-of: keep declaration on one line

timer_of_init() declaration could be kept on one line (80 chars per line rule is not broken). Signed-off-by: Claudiu Beznea --- drivers/clocksource/timer-of.h | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/drivers/clocksource/timer-of.h b/drivers/clocksource/timer-of.h

[PATCH 7/7] clocksource/drivers/integrator-ap: parse the chosen node

From: Alexandre Belloni The driver currently uses aliases to know whether the timer is the clocksource or the clockevent. Add the /chosen/linux,clocksource and /chosen/linux,clockevent parsing while keeping backward compatibility. Signed-off-by: Alexandre Belloni Signed-off-by: Claudiu Beznea

Re: [PATCH 4/7] dt-bindings: chosen: Add clocksource and clockevent selection

On Tue, Sep 10, 2019 at 04:47:13PM +0300, Claudiu Beznea wrote: > From: Alexandre Belloni > > Some timer drivers may behave either as clocksource or clockevent > or both. Until now, in case of platforms with multiple hardware > resources of the same type, the drivers were chosing the first >

[PATCH 0/7] add support for clocksource/clockevent DT selection

Hi, This series adds support to permit the selection of clocksource/clockevent via DT. In [1] I proposed a solution other than the one in this series, with parsing DT bindings and at probe time and passing it to timer specific probe function. Looking forward though the clocksource/clockevent

Re: [PATCH 2/7] clocksource: change timer registration macros

[crazy Cc list, not sure it'll go anywhere] On Tue, 10 Sep 2019 14:47:11 +0100, Claudiu Beznea wrote: > > Change timer registration macros (TIMER_OF_DECLARE() and > CLOCKSOURCE_OF_DECLARE()) by adding a new argument. This new argument > is a pointer to an object of type struct timer_of and is

[PATCH 2/7] clocksource: change timer registration macros

Change timer registration macros (TIMER_OF_DECLARE() and CLOCKSOURCE_OF_DECLARE()) by adding a new argument. This new argument is a pointer to an object of type struct timer_of and is used in timer_probe(). Based on the flags filled in the struct timer_of object the probing process will parse

[PATCH 4/7] dt-bindings: chosen: Add clocksource and clockevent selection

From: Alexandre Belloni Some timer drivers may behave either as clocksource or clockevent or both. Until now, in case of platforms with multiple hardware resources of the same type, the drivers were chosing the first registered hardware resource as clocksource/clockevent and the next one as

[PATCH 3/7] clocksource/timer_of: use BIT() macro

Use BIT() macro for timer_of flags. Signed-off-by: Claudiu Beznea --- drivers/clocksource/timer-of.h | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/drivers/clocksource/timer-of.h b/drivers/clocksource/timer-of.h index ee467bb16ca3..df861ea2ec42 100644 ---

[PATCH 1/7] clocksource/drivers/c-sky: request timer_of_init only for probing CPU

timer_of_init() was initially called for all possible CPUs although it was requested clock with index 0 for the same device_node on behalf of all possible CPUs. This patch keeps the timer_of_init() only for probing CPU and use the information obtained by timer_of_init() to also initialize the

Re: [PATCH 7/7] clocksource/drivers/integrator-ap: parse the chosen node

On Tue, Sep 10, 2019 at 2:50 PM Claudiu Beznea wrote: > From: Alexandre Belloni > > The driver currently uses aliases to know whether the timer is the > clocksource or the clockevent. OK maybe that wasn't the most elegant solution. > Add the /chosen/linux,clocksource and >

Re: [PATCH 4/7] dt-bindings: chosen: Add clocksource and clockevent selection

On Tue, Sep 10, 2019 at 4:11 PM Alexandre Belloni wrote: > On 10/09/2019 16:08:26+0100, Sudeep Holla wrote: > > On Tue, Sep 10, 2019 at 02:51:50PM +, claudiu.bez...@microchip.com > > wrote: > > In that case, why can't we identify capability that with the compatibles > > for this timer IP ?

Re: [PATCH 4/7] dt-bindings: chosen: Add clocksource and clockevent selection

On 10/09/2019 16:08:26+0100, Sudeep Holla wrote: > On Tue, Sep 10, 2019 at 02:51:50PM +, claudiu.bez...@microchip.com wrote: > > > > > > On 10.09.2019 17:32, Sudeep Holla wrote: > > > External E-Mail > > > > > > > > > On Tue, Sep 10, 2019 at 04:47:13PM +0300, Claudiu Beznea wrote: > > >>

Re: [PATCH 2/7] clocksource: change timer registration macros

On 10.09.2019 17:49, Marc Zyngier wrote: > External E-Mail > > > [crazy Cc list, not sure it'll go anywhere] It is what get_maintainer.pl script returned to. > > On Tue, 10 Sep 2019 14:47:11 +0100, > Claudiu Beznea wrote: >> >> Change timer registration macros (TIMER_OF_DECLARE() and >>

Re: [PATCH 4/7] dt-bindings: chosen: Add clocksource and clockevent selection

On Tue, Sep 10, 2019 at 02:51:50PM +, claudiu.bez...@microchip.com wrote: > > > On 10.09.2019 17:32, Sudeep Holla wrote: > > External E-Mail > > > > > > On Tue, Sep 10, 2019 at 04:47:13PM +0300, Claudiu Beznea wrote: > >> From: Alexandre Belloni > >> > >> Some timer drivers may behave

Re: [PATCH 0/7] add support for clocksource/clockevent DT selection

On Tue, Sep 10, 2019 at 6:47 AM Claudiu Beznea wrote: > > This series adds support to permit the selection of clocksource/clockevent > via DT. Sorry about this, but could you try to include more of a rational for *why* this would be useful in your cover-letter/commit messages? I'm not sure I

Re: [PATCH 4/7] dt-bindings: chosen: Add clocksource and clockevent selection

On 10.09.2019 17:32, Sudeep Holla wrote: > External E-Mail > > > On Tue, Sep 10, 2019 at 04:47:13PM +0300, Claudiu Beznea wrote: >> From: Alexandre Belloni >> >> Some timer drivers may behave either as clocksource or clockevent >> or both. Until now, in case of platforms with multiple