linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: benjamin.gaignard@linaro.org (Benjamin Gaignard)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v9 0/6] stm32 clocksource driver rework
Date: Fri,  8 Dec 2017 12:32:44 +0100	[thread overview]
Message-ID: <20171208113250.359-1-benjamin.gaignard@st.com> (raw)

version 9:
 - rebased on timer/master where timer_of_cleanup() exist
 - fix the comments done by Daniel on v8
 - reword commits message to be more explicit about 16 bits counter issue
 - add one patch about copyrights and licences
   
version 8:
 - rebased on timers/core
 - change timer_of_exit() name to timer_of_cleanup()
 - update stm32 clocksource driver to use this function

version 7:
 - reword "clocksource: stm32: only use 32 bits timers" commit message
   to give more details about why 16 bits are problematics.

version 6:
 - add dedicated patch min delta change
 - rework commit messages, I hope it will be better now
 - change new function name from timer_of_deinit to timer_of_exit
 - make stm32_clock_event_set_next_event() safer like done in other
   drivers

version 6:
- add timer_of_deinit function in core
- rework failure cases in probe function

version 5:
- rebase on top of timer/core branch
- rework commit message of the first patch

version 4:
- split patch in 3 parts
  - convert code to timer_of
  - only use 32 bits timers
  - add clocksource support

version 3:
- fix comments done by Daniel
- use timer_of helper functions

version 2:
- fix uninitialized variable

Benjamin Gaignard (6):
  clocksource: stm32: convert driver to timer_of
  clocksource: stm32: increase min delta value
  clocksource: stm32: only use 32 bits timers
  clocksource: stm32: add clocksource support
  clocksource: stm32: Update license and copyright
  arm: dts: stm32: remove useless clocksource nodes

 arch/arm/boot/dts/stm32f429.dtsi  |  32 -----
 arch/arm/boot/dts/stm32f746.dtsi  |  32 -----
 drivers/clocksource/Kconfig       |   1 +
 drivers/clocksource/timer-stm32.c | 253 +++++++++++++++++++++-----------------
 4 files changed, 139 insertions(+), 179 deletions(-)

-- 
2.15.0

             reply	other threads:[~2017-12-08 11:32 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-08 11:32 Benjamin Gaignard [this message]
2017-12-08 11:32 ` [PATCH v9 1/6] clocksource: stm32: convert driver to timer_of Benjamin Gaignard
2017-12-08 11:32 ` [PATCH v9 2/6] clocksource: stm32: increase min delta value Benjamin Gaignard
2017-12-08 11:32 ` [PATCH v9 3/6] clocksource: stm32: only use 32 bits timers Benjamin Gaignard
2017-12-08 12:51   ` Daniel Lezcano
2017-12-08 13:05     ` Benjamin Gaignard
2017-12-08 13:47       ` Daniel Lezcano
2017-12-08 11:32 ` [PATCH v9 4/6] clocksource: stm32: add clocksource support Benjamin Gaignard
2017-12-08 13:46   ` Daniel Lezcano
2017-12-08 14:04     ` Benjamin Gaignard
2017-12-08 14:08       ` Daniel Lezcano
2017-12-08 14:19         ` Benjamin Gaignard
2017-12-08 11:32 ` [PATCH v9 5/6] clocksource: stm32: Update license and copyright Benjamin Gaignard
2017-12-08 13:46   ` Philippe Ombredanne
2017-12-08 11:32 ` [PATCH v9 6/6] arm: dts: stm32: remove useless clocksource nodes Benjamin Gaignard

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=20171208113250.359-1-benjamin.gaignard@st.com \
    --to=benjamin.gaignard@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).