LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: Linux ARM <linux-arm-kernel@lists.infradead.org>,
	Sekhar Nori <nsekhar@ti.com>,
	David Lechner <david@lechnology.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Kevin Hilman <khilman@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Bartosz Golaszewski <bgolaszewski@baylibre.com>
Subject: Re: [RFC 0/2] clocksource: davinci-timer: new driver
Date: Mon, 13 May 2019 10:04:25 +0200	[thread overview]
Message-ID: <861538a7-9ee4-307d-433e-54e51a54fb98@linaro.org> (raw)
In-Reply-To: <CAMRc=MdhfEM_CndCjCkY9kWeu+3VPTA7tmTy5PH=2XforZ6aLw@mail.gmail.com>

On 13/05/2019 09:54, Bartosz Golaszewski wrote:
> śr., 17 kwi 2019 o 16:47 Bartosz Golaszewski <brgl@bgdev.pl> napisał(a):
>>
>> From: Bartosz Golaszewski <bgolaszewski@baylibre.com>
>>
>> Hi Daniel,
>>
>> as discussed - this is the davinci timer driver split into the clockevent
>> and clocksource parts.
>>
>> Since it won't work without all the other (left out for now) changes, I'm
>> marking it as RFC.
>>
>> The code has been simplified as requested, the duplicated enums and the
>> davinci_timer structure have been removed.
>>
>> Please let me know if that's better. I retested it on da850-lcdk, da830-evm
>> and dm365-evm.
>>
>> Bartosz Golaszewski (2):
>>   clocksource: davinci-timer: add support for clockevents
>>   clocksource: timer-davinci: add support for clocksource
>>
>>  drivers/clocksource/Kconfig         |   5 +
>>  drivers/clocksource/Makefile        |   1 +
>>  drivers/clocksource/timer-davinci.c | 342 ++++++++++++++++++++++++++++
>>  include/clocksource/timer-davinci.h |  44 ++++
>>  4 files changed, 392 insertions(+)
>>  create mode 100644 drivers/clocksource/timer-davinci.c
>>  create mode 100644 include/clocksource/timer-davinci.h
>>
>> --
>> 2.21.0
>>
> 
> Hi Daniel,
> 
> it's been almost a month so a gentle ping. Any comments on that?

Oh right, I've been distracted with other things, sorry for that. Let me
review it today.


-- 
 <http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs

Follow Linaro:  <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog


      reply	other threads:[~2019-05-13  8:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-17 14:47 Bartosz Golaszewski
2019-04-17 14:47 ` [RFC 1/2] clocksource: davinci-timer: add support for clockevents Bartosz Golaszewski
2019-05-14 19:55   ` Daniel Lezcano
2019-05-23 12:58     ` Bartosz Golaszewski
2019-05-23 13:25       ` Daniel Lezcano
2019-05-23 15:34         ` Bartosz Golaszewski
2019-04-17 14:47 ` [RFC 2/2] clocksource: timer-davinci: add support for clocksource Bartosz Golaszewski
2019-05-13  7:54 ` [RFC 0/2] clocksource: davinci-timer: new driver Bartosz Golaszewski
2019-05-13  8:04   ` Daniel Lezcano [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=861538a7-9ee4-307d-433e-54e51a54fb98@linaro.org \
    --to=daniel.lezcano@linaro.org \
    --cc=bgolaszewski@baylibre.com \
    --cc=brgl@bgdev.pl \
    --cc=david@lechnology.com \
    --cc=khilman@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nsekhar@ti.com \
    --cc=tglx@linutronix.de \
    --subject='Re: [RFC 0/2] clocksource: davinci-timer: new driver' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).