From: Alexandre Belloni <alexandre.belloni@free-electrons.com>
To: Gregory CLEMENT <gregory.clement@free-electrons.com>
Cc: Alessandro Zummo <a.zummo@towertech.it>,
rtc-linux@googlegroups.com, Jason Cooper <jason@lakedaemon.net>,
Andrew Lunn <andrew@lunn.ch>,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
linux-arm-kernel@lists.infradead.org,
Haim Boot <hayim@marvell.com>
Subject: [rtc-linux] Re: [PATCH v2 0/3] Extend rtc-armada38x support for Armada 7K/8K
Date: Mon, 20 Feb 2017 18:36:33 +0100 [thread overview]
Message-ID: <20170220173633.d4ke4eohaacgsw3h@piout.net> (raw)
In-Reply-To: <87tw7oaj24.fsf@free-electrons.com>
On 20/02/2017 at 18:06:11 +0100, Gregory CLEMENT wrote:
> On ven., f=C3=A9vr. 17 2017, Gregory CLEMENT <gregory.clement@free-elect=
rons.com> wrote:
>=20
> > 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.
>=20
> 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:
>=20
> devmem2 0xf428401c w 0
> devmem2 0xf4284018 w 0x2000
The question being what does that do and whether it could be done in the
driver instead.
--=20
Alexandre Belloni, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
--=20
You received this message because you are subscribed to "rtc-linux".
Membership options at http://groups.google.com/group/rtc-linux .
Please read http://groups.google.com/group/rtc-linux/web/checklist
before submitting a driver.
---=20
You received this message because you are subscribed to the Google Groups "=
rtc-linux" group.
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to rtc-linux+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
WARNING: multiple messages have this Message-ID (diff)
From: alexandre.belloni@free-electrons.com (Alexandre Belloni)
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:36:33 +0100 [thread overview]
Message-ID: <20170220173633.d4ke4eohaacgsw3h@piout.net> (raw)
In-Reply-To: <87tw7oaj24.fsf@free-electrons.com>
On 20/02/2017 at 18:06:11 +0100, Gregory CLEMENT wrote:
> 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
The question being what does that do and whether it could be done in the
driver instead.
--
Alexandre Belloni, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-02-20 17:36 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-17 10:19 [rtc-linux] [PATCH v2 0/3] Extend rtc-armada38x support for Armada 7K/8K Gregory CLEMENT
2017-02-17 10:19 ` Gregory CLEMENT
2017-02-17 10:19 ` [rtc-linux] [PATCH v2 1/3] rtc: armada38x: Prepare driver to manage different versions Gregory CLEMENT
2017-02-17 10:19 ` Gregory CLEMENT
2017-02-17 10:19 ` [rtc-linux] [PATCH v2 2/3] rtc: armada38x: Add support for Armada 7K/8K Gregory CLEMENT
2017-02-17 10:19 ` Gregory CLEMENT
2017-02-17 10:19 ` [rtc-linux] [PATCH v2 3/3] arm64: dts: marvell: add RTC description " Gregory CLEMENT
2017-02-17 10:19 ` Gregory CLEMENT
2017-02-20 17:06 ` [rtc-linux] Re: [PATCH v2 0/3] Extend rtc-armada38x support " Gregory CLEMENT
2017-02-20 17:06 ` Gregory CLEMENT
2017-02-20 17:27 ` [rtc-linux] " Russell King - ARM Linux
2017-02-20 17:27 ` Russell King - ARM Linux
2017-02-20 17:36 ` [rtc-linux] " Gregory CLEMENT
2017-02-20 17:36 ` Gregory CLEMENT
2017-02-20 17:42 ` [rtc-linux] " Russell King - ARM Linux
2017-02-20 17:42 ` Russell King - ARM Linux
2017-02-20 17:36 ` Alexandre Belloni [this message]
2017-02-20 17:36 ` Alexandre Belloni
2017-02-20 17:43 ` [rtc-linux] " Gregory CLEMENT
2017-02-20 17:43 ` Gregory CLEMENT
2017-02-20 17:50 ` [rtc-linux] " Russell King - ARM Linux
2017-02-20 17:50 ` Russell King - ARM Linux
2017-02-20 18:17 ` [rtc-linux] " Alexandre Belloni
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=20170220173633.d4ke4eohaacgsw3h@piout.net \
--to=alexandre.belloni@free-electrons.com \
--cc=a.zummo@towertech.it \
--cc=andrew@lunn.ch \
--cc=gregory.clement@free-electrons.com \
--cc=hayim@marvell.com \
--cc=jason@lakedaemon.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=rtc-linux@googlegroups.com \
--cc=sebastian.hesselbarth@gmail.com \
--cc=thomas.petazzoni@free-electrons.com \
/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 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.