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.
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 int
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]
https://lore.kernel.org/lkml/15
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?
If you have other suggestion I am open to try it.
Thank you,
Claudiu Beznea
On 26.09.2019 11:42, Claudiu Beznea wrote:
>
>
> On 25.09.2019
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 16:08:26+010
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 progress
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 can'
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 e
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
> *why
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
>> CL
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 hardwar
11 matches
Mail list logo
