linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@kernel.org>
Cc: linux-kernel@vger.kernel.org
Subject: [GIT PULL] clockevents for 4.10
Date: Tue, 22 Nov 2016 10:43:00 +0100	[thread overview]
Message-ID: <20161122094300.GA2017@mai> (raw)

Hi Thomas, Ingo,

This pull request contains a few changes.

 - Unmap the region obtained by of_iomap in case of error in the init path for
   the bcm2835 timer (Arvind Yadav).

 - Add a boolean property in the DT for the arch_arm_timer in order to tell the
   driver the hardware implementation has an error because it does not belong
   to an always-on power domain (Brian Norris).

 - Replace of_iomap() by of_io_request_and_map() for the arch_arm_timer
   (Stephen Boyd).

Thanks !

  -- Daniel


The following changes since commit baa73d9e478ff32d62f3f9422822b59dd9a95a21:

  posix-timers: Make them configurable (2016-11-16 09:26:35 +0100)

are available in the git repository at:

  https://git.linaro.org/people/daniel.lezcano/linux.git 

for you to fetch changes up to 84c39b8b7d46883f7a7514c7d55909831aa846fd:

  clocksource/drivers/bcm2835_timer: Unmap region obtained by of_iomap (2016-11-22 09:22:59 +0100)

----------------------------------------------------------------
Arvind Yadav (1):
      clocksource/drivers/bcm2835_timer: Unmap region obtained by of_iomap

Brian Norris (2):
      clocksource/drivers/arm_arch_timer: Don't assume clock runs in suspend
      arm64: dts: rockchip: Arch counter doesn't tick in system suspend

Stephen Boyd (1):
      clocksource/drivers/arm_arch_timer: Map frame with of_io_request_and_map()

 Documentation/devicetree/bindings/arm/arch_timer.txt |  5 +++++
 arch/arm64/boot/dts/rockchip/rk3399.dtsi             |  1 +
 drivers/clocksource/arm_arch_timer.c                 | 14 +++++++++++---
 drivers/clocksource/bcm2835_timer.c                  | 14 ++++++++++----
 4 files changed, 27 insertions(+), 7 deletions(-)



-- 

 <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:[~2016-11-22  9:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-22  9:43 Daniel Lezcano [this message]
2016-11-22  9:44 ` [PATCH 1/4] clocksource/drivers/arm_arch_timer: Don't assume clock runs in suspend Daniel Lezcano
2016-11-22  9:44   ` [PATCH 2/4] arm64: dts: rockchip: Arch counter doesn't tick in system suspend Daniel Lezcano
2016-11-22 15:02     ` Heiko Stübner
2016-11-22  9:44   ` [PATCH 3/4] clocksource/drivers/arm_arch_timer: Map frame with of_io_request_and_map() Daniel Lezcano
2016-11-22  9:44   ` [PATCH 4/4] clocksource/drivers/bcm2835_timer: Unmap region obtained by of_iomap Daniel Lezcano
2016-11-23 23:07   ` [PATCH 1/4] clocksource/drivers/arm_arch_timer: Don't assume clock runs in suspend Rob Herring
2016-11-22  9:51 ` [GIT PULL] clockevents for 4.10 Ingo Molnar
2016-11-22  9:57   ` Daniel Lezcano

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=20161122094300.GA2017@mai \
    --to=daniel.lezcano@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --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: 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).