public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: gregory.clement@free-electrons.com (Gregory CLEMENT)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/3] Extend rtc-armada38x support for Armada 7K/8K
Date: Mon, 20 Feb 2017 18:06:11 +0100	[thread overview]
Message-ID: <87tw7oaj24.fsf@free-electrons.com> (raw)
In-Reply-To: <20170217101907.8963-1-gregory.clement@free-electrons.com> (Gregory CLEMENT's message of "Fri, 17 Feb 2017 11:19:04 +0100")

Hi,
 
 On ven., f?vr. 17 2017, Gregory CLEMENT <gregory.clement@free-electrons.com> wrote:

> The Armada 7K/8K SoCs use the same RTC IP than the Armada 38x. However
> the SOC integration differs in 2 points:
>      - MBUS bridge timing initialization
>      - IRQ configuration at SoC level
>
> This patch set extends the driver support to these SoCs family.
>
> In this second version the device tree was updated allowing to use the
> RTC on Armada 80x0 SoCs. Indeed on the Armada 80x0, the RTC clock in
> CP master is not connected (by package) to the oscillator. So this one
> is disabled for the Armada 8020 and the Armada 8040. On these SoCs it
> will be the RTC clock in CP slave connected to the oscillator which
> will be used.

I saw on IRC than Russell managed to have a more coherent date with this
series on his 8040 based board. For the record, as the U-Boot on this
board didn't provide a "date reset" command for the RTC located on CP
slave, then Russell needed to do the following:

devmem2 0xf428401c w 0
devmem2 0xf4284018 w 0x2000
followed by:
date 021612342017; ntpdate ...; hwclock -uw

But this issue was related to the bootloader not to the kernel. The
other potential issue seen by Russell was about the GIC mapping for the
interrupt, but here again this mapping was done by the 1st stage
bootloader.

Given this information would it be OK to applied this series?

Thanks,

Gregory

>
> Thanks,
>
> Gregory
>
> Gregory CLEMENT (3):
>   rtc: armada38x: Prepare driver to manage different versions
>   rtc: armada38x: Add support for Armada 7K/8K
>   arm64: dts: marvell: add RTC description for Armada 7K/8K
>
>  .../devicetree/bindings/rtc/armada-380-rtc.txt     |   8 +-
>  arch/arm64/boot/dts/marvell/armada-8020.dtsi       |  10 +
>  arch/arm64/boot/dts/marvell/armada-8040.dtsi       |   9 +
>  .../boot/dts/marvell/armada-cp110-master.dtsi      |   7 +
>  .../arm64/boot/dts/marvell/armada-cp110-slave.dtsi |   7 +
>  drivers/rtc/rtc-armada38x.c                        | 217 ++++++++++++++++-----
>  6 files changed, 202 insertions(+), 56 deletions(-)
>
> -- 
> 2.11.0
>

-- 
Gregory Clement, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  parent reply	other threads:[~2017-02-20 17:06 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-17 10:19 [PATCH v2 0/3] Extend rtc-armada38x support for Armada 7K/8K Gregory CLEMENT
2017-02-17 10:19 ` [PATCH v2 1/3] rtc: armada38x: Prepare driver to manage different versions Gregory CLEMENT
2017-02-17 10:19 ` [PATCH v2 2/3] rtc: armada38x: Add support for Armada 7K/8K Gregory CLEMENT
2017-02-17 10:19 ` [PATCH v2 3/3] arm64: dts: marvell: add RTC description " Gregory CLEMENT
2017-02-20 17:06 ` Gregory CLEMENT [this message]
2017-02-20 17:27   ` [PATCH v2 0/3] Extend rtc-armada38x support " Russell King - ARM Linux
2017-02-20 17:36     ` Gregory CLEMENT
2017-02-20 17:42     ` Russell King - ARM Linux
2017-02-20 17:36   ` Alexandre Belloni
2017-02-20 17:43     ` Gregory CLEMENT
2017-02-20 17:50     ` Russell King - ARM Linux
2017-02-20 18:17       ` Alexandre Belloni

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=87tw7oaj24.fsf@free-electrons.com \
    --to=gregory.clement@free-electrons.com \
    --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