From: Boris BREZILLON <boris.brezillon@free-electrons.com>
To: Johan Hovold <johan@kernel.org>
Cc: Nicolas Ferre <nicolas.ferre@atmel.com>,
Jean-Christophe Plagniol-Villard <plagnioj@jcrosoft.com>,
Alexandre Belloni <alexandre.belloni@free-electrons.com>,
Andrew Victor <linux@maxim.org.za>,
Alessandro Zummo <a.zummo@towertech.it>,
rtc-linux@googlegroups.com, Rob Herring <robh+dt@kernel.org>,
Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 5/5] rtc: at91sam9: add DT bindings documentation
Date: Wed, 10 Sep 2014 17:31:14 +0200 [thread overview]
Message-ID: <20140910173114.593dd132@bbrezillon> (raw)
In-Reply-To: <20140910150702.GK2974@localhost>
On Wed, 10 Sep 2014 17:07:02 +0200
Johan Hovold <johan@kernel.org> wrote:
> 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@ffffff20 {
>
> rtt
>
> > compatible = "atmel,at91sam9260-rtt";
> > reg = <0xfffffd20 0x10>;
> > interrupts = <1 4 7>;
> > clocks = <&clk32k>;
> > atmel,time-reg = <&gpbr 0x0>;
> > };
> >
> > gpbr: syscon@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?
Yep, that's one of the concern I had with the syscon/regmap
approach :-(, but I guess I'll give this solution a try and post a new
version of this series ;-).
Can we just leave the rtt as an rtc problem on the side for now and bind
it to the rtc-at91sam9 driver.
If we ever decide to add a new driver using the RTT for another purpose
we will still be able to reference the RTT block like this (and keep
the existing rtt node definition):
rtt-based-rtc {
compatible = "atmel,rtt-rtc";
atmel,rtt = <&rtt>;
atmel,time-reg = <&gpbr 0x0>;
}
rtt-based-xdev {
compatible = "atmel,rtt-xdev";
atmel,rtt = <&rtt>;
/*...*/
}
Regards,
Boris
--
Boris Brezillon, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-09-10 15:31 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
[not found] ` <1409733934-14465-2-git-send-email-boris.brezillon-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
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
[not found] ` <1409733934-14465-5-git-send-email-boris.brezillon-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
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
[not found] ` <1409733934-14465-6-git-send-email-boris.brezillon-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
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
2014-09-10 15:31 ` Boris BREZILLON [this message]
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
[not found] ` <1409733934-14465-1-git-send-email-boris.brezillon-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
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=20140910173114.593dd132@bbrezillon \
--to=boris.brezillon@free-electrons.com \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@free-electrons.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=johan@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@maxim.org.za \
--cc=mark.rutland@arm.com \
--cc=nicolas.ferre@atmel.com \
--cc=pawel.moll@arm.com \
--cc=plagnioj@jcrosoft.com \
--cc=robh+dt@kernel.org \
--cc=rtc-linux@googlegroups.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 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).