From: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
To: linux-amlogic@lists.infradead.org, khilman@baylibre.com
Cc: Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
jianxin.pan@amlogic.com, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, ccaione@baylibre.com
Subject: [PATCH 0/3] Meson8b: add support for the RTC on EC-100 and Odroid-C1
Date: Sat, 13 Apr 2019 18:34:20 +0200 [thread overview]
Message-ID: <20190413163423.15149-1-martin.blumenstingl@googlemail.com> (raw)
This adds support for the RTC on the Meson8b EC-100 and Odroid-C1
boards. Example kernel log snippet while booting my EC-100:
[ 5.713750] meson-rtc c8100740.rtc: setting system clock to 2019-04-13T16:21:48 UTC (1555172508)
I am only 99% sure about the naming of the clock in patch 2 and 3.
The public S805 datasheet from Hardkernel shows (on page 24 for example)
that clk81 can use "XTAL/32khz" as clock input. That "XTAL/32khz" clock
is described as a mux between 24MHz (our main XTAL) and 32kHz ("that
other XTAL").
I believe that this other 32kHz XTAL is NOT the RTC32K crystal because:
- schematics of the EC-100 and Odroid-C1 clearly show that the SoC input
for the RTC32K clock is labeled RTC32K_XI / RTC32K_XO
- GPIOAO_6 has a CLK_32KIN function (shows in EC-100 and Odroid-C1
schematics as well as the public S805 datasheet)
- Always On domain PWR_CNTL0[11:10] (public S805 datasheet page 19)
describes it as "Alternate 32khz input clock select from GPIO pad"
Thus I believe that the naming of the RTC32K clock is correct, but I
wanted to point out that I'm only 99% (instead of 100%) sure.
Jianxin, please let me know if you disagree with my findings.
Martin Blumenstingl (3):
ARM: dts: meson: add support for the RTC
ARM: dts: meson8b: ec100: enable the RTC
ARM: dts: meson8b: odroid-c1: prepare support for the RTC
arch/arm/boot/dts/meson.dtsi | 9 +++++++++
arch/arm/boot/dts/meson8.dtsi | 5 +++++
arch/arm/boot/dts/meson8b-ec100.dts | 14 ++++++++++++++
arch/arm/boot/dts/meson8b-odroidc1.dts | 14 ++++++++++++++
arch/arm/boot/dts/meson8b.dtsi | 5 +++++
5 files changed, 47 insertions(+)
--
2.21.0
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next reply other threads:[~2019-04-13 16:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-13 16:34 Martin Blumenstingl [this message]
2019-04-13 16:34 ` [PATCH 1/3] ARM: dts: meson: add support for the RTC Martin Blumenstingl
2019-04-13 16:34 ` [PATCH 2/3] ARM: dts: meson8b: ec100: enable " Martin Blumenstingl
2019-04-13 16:34 ` [PATCH 3/3] ARM: dts: meson8b: odroid-c1: prepare support for " Martin Blumenstingl
2019-04-16 19:00 ` Kevin Hilman
2019-04-16 19:01 ` [PATCH 0/3] Meson8b: add support for the RTC on EC-100 and Odroid-C1 Kevin Hilman
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=20190413163423.15149-1-martin.blumenstingl@googlemail.com \
--to=martin.blumenstingl@googlemail.com \
--cc=ccaione@baylibre.com \
--cc=jianxin.pan@amlogic.com \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.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).