From: Bartosz Golaszewski <brgl@bgdev.pl> To: Sekhar Nori <nsekhar@ti.com>, Kevin Hilman <khilman@kernel.org>, Daniel Lezcano <daniel.lezcano@linaro.org>, Thomas Gleixner <tglx@linutronix.de>, David Lechner <david@lechnology.com> Cc: linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, Bartosz Golaszewski <bgolaszewski@baylibre.com> Subject: [RFC v2 0/2] clocksource: davinci-timer: new driver Date: Thu, 23 May 2019 14:58:11 +0200 [thread overview] Message-ID: <20190523125813.29506-1-brgl@bgdev.pl> (raw) From: Bartosz Golaszewski <bgolaszewski@baylibre.com> Hi Daniel, this is another try at the davinci clocksource driver. Changes in regard to v1 listed below. As before, the driver is split into two parts (one for clockevent and one for clocksource). v1 -> v2: - changed the format of the copyright notice - removed all mentiones of the periodic timer setting - added caching of the TCR register value so that its updating doesn't require a read - split the timer configuration for clock events into the set_state_oneshot() and set_state_shutdown() callbacks 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 | 355 ++++++++++++++++++++++++++++ include/clocksource/timer-davinci.h | 44 ++++ 4 files changed, 405 insertions(+) create mode 100644 drivers/clocksource/timer-davinci.c create mode 100644 include/clocksource/timer-davinci.h -- 2.21.0
WARNING: multiple messages have this Message-ID (diff)
From: Bartosz Golaszewski <brgl@bgdev.pl> To: Sekhar Nori <nsekhar@ti.com>, Kevin Hilman <khilman@kernel.org>, Daniel Lezcano <daniel.lezcano@linaro.org>, Thomas Gleixner <tglx@linutronix.de>, David Lechner <david@lechnology.com> Cc: Bartosz Golaszewski <bgolaszewski@baylibre.com>, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org Subject: [RFC v2 0/2] clocksource: davinci-timer: new driver Date: Thu, 23 May 2019 14:58:11 +0200 [thread overview] Message-ID: <20190523125813.29506-1-brgl@bgdev.pl> (raw) From: Bartosz Golaszewski <bgolaszewski@baylibre.com> Hi Daniel, this is another try at the davinci clocksource driver. Changes in regard to v1 listed below. As before, the driver is split into two parts (one for clockevent and one for clocksource). v1 -> v2: - changed the format of the copyright notice - removed all mentiones of the periodic timer setting - added caching of the TCR register value so that its updating doesn't require a read - split the timer configuration for clock events into the set_state_oneshot() and set_state_shutdown() callbacks 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 | 355 ++++++++++++++++++++++++++++ include/clocksource/timer-davinci.h | 44 ++++ 4 files changed, 405 insertions(+) create mode 100644 drivers/clocksource/timer-davinci.c create mode 100644 include/clocksource/timer-davinci.h -- 2.21.0 _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2019-05-23 12:58 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-05-23 12:58 Bartosz Golaszewski [this message] 2019-05-23 12:58 ` [RFC v2 0/2] clocksource: davinci-timer: new driver Bartosz Golaszewski 2019-05-23 12:58 ` [RFC v2 1/2] clocksource: davinci-timer: add support for clockevents Bartosz Golaszewski 2019-05-23 12:58 ` Bartosz Golaszewski 2019-05-23 16:38 ` Daniel Lezcano 2019-05-23 16:38 ` Daniel Lezcano 2019-05-24 7:28 ` Bartosz Golaszewski 2019-05-24 7:28 ` Bartosz Golaszewski 2019-05-24 8:59 ` Daniel Lezcano 2019-05-24 8:59 ` Daniel Lezcano 2019-05-24 11:53 ` Bartosz Golaszewski 2019-05-24 11:53 ` Bartosz Golaszewski 2019-05-25 14:16 ` Daniel Lezcano 2019-05-25 14:16 ` Daniel Lezcano 2019-05-26 8:16 ` Bartosz Golaszewski 2019-05-26 8:16 ` Bartosz Golaszewski 2019-05-31 12:21 ` Bartosz Golaszewski 2019-05-31 12:21 ` Bartosz Golaszewski 2019-05-23 12:58 ` [RFC v2 2/2] clocksource: timer-davinci: add support for clocksource Bartosz Golaszewski 2019-05-23 12:58 ` Bartosz Golaszewski
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=20190523125813.29506-1-brgl@bgdev.pl \ --to=brgl@bgdev.pl \ --cc=bgolaszewski@baylibre.com \ --cc=daniel.lezcano@linaro.org \ --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 \ /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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.