linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: heiko@sntech.de (Heiko Stuebner)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 1/4] rockchip soc-driver changes for 4.6
Date: Thu, 11 Feb 2016 15:49:12 +0100	[thread overview]
Message-ID: <2006551.mXAMdNYBE2@phil> (raw)
In-Reply-To: <1734524.3yNt5L3F1F@phil>

Hi Arnd, Olof, Kevin,

This one change enables the rockchip timer driver on 64bit socs as well,
after it got fixed to actually work on 64bit in 4.5-rc1.
 
Thanks
Heiko


The following changes since commit 92e963f50fc74041b5e9e744c330dca48e04f08d:

  Linux 4.5-rc1 (2016-01-24 13:06:47 -0800)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/mmind/linux-rockchip.git tags/v4.6-rockchip-soc64-1

for you to fetch changes up to c840f28bbf643c361c463bcb8fb815d0b2dad4e8:

  arm64: Enable the timer on Rockchip architecture (2016-01-24 23:33:14 +0100)

----------------------------------------------------------------
Enable the rockchip-specific timers on arm64 rockchip platforms.
The driver got reworked to not use arm32-specific dsb calls in
4.5-rc1, so now we can safely enable it.

----------------------------------------------------------------
Caesar Wang (1):
      arm64: Enable the timer on Rockchip architecture

 arch/arm64/Kconfig.platforms | 1 +
 1 file changed, 1 insertion(+)

  reply	other threads:[~2016-02-11 14:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-11 14:47 [GIT PULL 1/4] rockchip soc-driver changes for 4.6 Heiko Stuebner
2016-02-11 14:49 ` Heiko Stuebner [this message]
2016-02-11 14:50 ` [GIT PULL 2/4] rockchip arm64 " Heiko Stuebner
2016-02-24 21:51   ` Olof Johansson
2016-02-11 14:52 ` [GIT PULL 3/4] rockchip dts64 " Heiko Stuebner
2016-02-24 21:52   ` Olof Johansson
2016-02-11 15:12 ` [GIT PULL 4/4] rockchip dts32 " Heiko Stuebner
2016-02-24 21:53   ` Olof Johansson
2016-02-24 21:50 ` [GIT PULL 1/4] rockchip soc-driver " Olof Johansson

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=2006551.mXAMdNYBE2@phil \
    --to=heiko@sntech.de \
    --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).