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

2019-10-21 Thread Claudiu.Beznea
Hi Daniel, On 18.10.2019 23:24, Daniel Lezcano wrote: > Hi Claudiu, > > On 15/10/2019 11:23, claudiu.bez...@microchip.com wrote: > > [ ... ] > >> The timer clock source could be divided by MR.PRES + 1. >> >> So, I used the clock-frequency DT binding to let user choose the timer's >> frequency.

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

2019-10-15 Thread Claudiu.Beznea
Hi Daniel, On 13.10.2019 21:16, Daniel Lezcano wrote: > Hi Claudiu, > > sorry for the delay, I was OoO again. No problem, thank you for your reply. > > On 03/10/2019 12:43, claudiu.bez...@microchip.com wrote: >> >> >> On 02.10.2019 16:35, Claudiu Beznea wrote: >>> Hi Daniel, >>> >>> Taking

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

2019-10-03 Thread Claudiu.Beznea
On 02.10.2019 16:35, Claudiu Beznea wrote: > Hi Daniel, > > Taking into account that Rob doesn't agree with the solution proposed in > this series do you think there is a chance to merge this driver as is? Sorry, I was talking here about the driver at [1]. [1]

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

2019-10-02 Thread Claudiu.Beznea
On 30.09.2019 17:32, Rob Herring wrote: > On Wed, Sep 11, 2019 at 07:18:07AM +, claudiu.bez...@microchip.com wrote: >> >> >> On 11.09.2019 03:03, Linus Walleij wrote: >>> External E-Mail >>> >>> >>> On Tue, Sep 10, 2019 at 4:11 PM Alexandre Belloni >>> wrote: On 10/09/2019

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

2019-09-26 Thread Claudiu.Beznea
On 25.09.2019 20:19, Daniel Lezcano wrote: > External E-Mail > > > Hi Claudiu, > > On 10/09/2019 15:47, Claudiu Beznea wrote: >> Hi, >> >> This series adds support to permit the selection of clocksource/clockevent >> via DT. > > Thanks for the proposal and taking care of making some

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

2019-09-11 Thread Claudiu.Beznea
On 11.09.2019 03:03, Linus Walleij wrote: > External E-Mail > > > 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

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

2019-09-11 Thread Claudiu.Beznea
On 11.09.2019 02:48, Linus Walleij wrote: > External E-Mail > > > 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

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

2019-09-11 Thread Claudiu.Beznea
On 10.09.2019 19:05, John Stultz wrote: > External E-Mail > > > 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 >

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

2019-09-10 Thread Claudiu.Beznea
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

2019-09-10 Thread Claudiu.Beznea
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