From: johan@kernel.org (Johan Hovold)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 5/5] rtc: at91sam9: add DT bindings documentation
Date: Wed, 10 Sep 2014 17:07:02 +0200 [thread overview]
Message-ID: <20140910150702.GK2974@localhost> (raw)
In-Reply-To: <20140910152019.111c4c01@bbrezillon>
On Wed, Sep 10, 2014 at 03:20:19PM +0200, Boris BREZILLON wrote:
> On Wed, 10 Sep 2014 14:14:24 +0200
> Johan Hovold <johan@kernel.org> wrote:
> > This does not describe the hardware, but rather a specific software
> > configuration.
> >
> > The RTT is first of all not an RTC (although it can be used as one in a
> > specific software configuration). And the second register resource above
> > is not an RTT register, but a general-purpose backup register could be
> > used for other purposes (which register to use is currently configurable
> > for legacy booting using CONFIG_RTC_DRV_AT91SAM9_GPBR).
>
> We could use a syscon device (which exposes a regmap) for the GPBR
> block.
>
> rtc at ffffff20 {
rtt
> compatible = "atmel,at91sam9260-rtt";
> reg = <0xfffffd20 0x10>;
> interrupts = <1 4 7>;
> clocks = <&clk32k>;
> atmel,time-reg = <&gpbr 0x0>;
> };
>
> gpbr: syscon at fffffd50 {
> compatible = "atmel,at91sam9260-gpbr", "syscon";
> reg = <0xfffffd50 0x10>;
>
> };
Yes, this essentially what I suggested in the thread (and my last reply)
and relying on syscon rather than a custom driver seems like a good
idea. It would allow early access to the registers too with the recently
proposed changes. It would not guarantee any kind of exclusivity,
though, but I guess that's tolerable?
Johan
next prev parent reply other threads:[~2014-09-10 15:07 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-03 8:45 [PATCH 0/5] rtc: at91sam9: add DT support Boris BREZILLON
2014-09-03 8:45 ` [PATCH 1/5] rtc: at91sam9: remove references to mach specific headers Boris BREZILLON
2014-09-08 17:32 ` Alexandre Belloni
2014-09-03 8:45 ` [PATCH 2/5] rtc: at91sam9: use standard readl/writel functions instead of raw versions Boris BREZILLON
2014-09-03 8:45 ` [PATCH 3/5] rtc: at91sam9: add DT support Boris BREZILLON
2014-09-03 8:45 ` [PATCH 4/5] rtc: at91sam9: retain slow clock and check its rate Boris BREZILLON
2014-09-08 17:33 ` Alexandre Belloni
2014-09-08 19:22 ` Boris BREZILLON
2014-09-08 19:37 ` Boris BREZILLON
2014-09-09 8:36 ` Nicolas Ferre
2014-09-03 8:45 ` [PATCH 5/5] rtc: at91sam9: add DT bindings documentation Boris BREZILLON
2014-09-10 12:14 ` Johan Hovold
2014-09-10 12:43 ` Boris BREZILLON
2014-09-10 13:16 ` Johan Hovold
2014-09-10 13:20 ` Boris BREZILLON
2014-09-10 15:07 ` Johan Hovold [this message]
2014-09-10 15:31 ` Boris BREZILLON
2014-09-10 15:52 ` Johan Hovold
2014-09-10 16:55 ` Nicolas Ferre
2014-09-10 15:35 ` Boris BREZILLON
2014-09-10 15:57 ` Johan Hovold
2014-09-03 9:31 ` [PATCH 0/5] rtc: at91sam9: add DT support Boris BREZILLON
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=20140910150702.GK2974@localhost \
--to=johan@kernel.org \
--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).