From: jhovold@gmail.com (Johan Hovold)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC 4/5] RTC: rtc-at91sam9: add device-tree support
Date: Mon, 8 Apr 2013 12:48:23 +0200 [thread overview]
Message-ID: <20130408104823.GF25605@localhost> (raw)
In-Reply-To: <20130408100301.GS20693@game.jcrosoft.org>
On Mon, Apr 08, 2013 at 12:03:01PM +0200, Jean-Christophe PLAGNIOL-VILLARD wrote:
> On 11:57 Mon 08 Apr , Nicolas Ferre wrote:
> > On 04/08/2013 11:00 AM, Johan Hovold :
> > > On Mon, Apr 08, 2013 at 09:38:07AM +0200, Jean-Christophe PLAGNIOL-VILLARD wrote:
> > >> On 17:12 Sun 07 Apr , Johan Hovold wrote:
[...]
> > >> the RTT is a general purpose timer backuped that we use in linux as a
> > >> RTC with a gpbr to store the time
> > >>
> > >> you need 2 binding on for the RTT one the RTT-rtc
> > >
> > > As in adding some virtual hardware-node which uses the rtt and gpbr as
> > > resources?
> >
> > So, why not simply having a compatibility string that collects the uses
> > of this RTT node:
> >
> > compatible = "atmel,at91sam9260-rtt-as-rtc", "atmel,at91sam9260-rtt";
> >
> > And then "decide which device driver to bind to [the RTT] device"...
> > If the rtt-as-rtc driver is not selected, the device can still be used
> > as a simple "rtt". The board .dts can overload a compatibility string
> > according to the use, etc.
> >
> > Then the way do describe which GPBR to use has still to be discussed.
> > But for the RTT itself, I would keep it simple like that.
>
> no as infact the rtc-at91sam9 should not even exist
> as this is much more generic
>
> we use a backped register and a timer to emulate a RTC this can be unsed by
> any one
>
> and I can use any backuped timer
>
> we need to have frameworks
> where the gpbr are tracked and the rtt
>
> for you describe the resources
>
> rtt0: rtt at fffffd20 {
> compatible = "atmel,at91sam9260-rtt";
> reg = <0xfffffd20 0x10>;
> interrupts = <1 4 7>;
> };
>
> rtc-timer {
> compatible = "linux,rtc-timer";
> timer = <&rtt0>;
> backuped-register = <&gpbr 0>;
> };
>
> this need to SoC implemetation generic
This would indeed be a neat solution, albeit one that requires a lot
work to be realised as both a backup-register and backed-up-timer
framework would need to be implemented.
Thanks,
Johan
WARNING: multiple messages have this Message-ID (diff)
From: Johan Hovold <jhovold@gmail.com>
To: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
Cc: Johan Hovold <jhovold@gmail.com>,
dgilbert@interlog.com, Nicolas Ferre <nicolas.ferre@atmel.com>,
Robert Nelson <Robert.Nelson@digikey.com>,
devicetree-discuss@lists.ozlabs.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [RFC 4/5] RTC: rtc-at91sam9: add device-tree support
Date: Mon, 8 Apr 2013 12:48:23 +0200 [thread overview]
Message-ID: <20130408104823.GF25605@localhost> (raw)
In-Reply-To: <20130408100301.GS20693@game.jcrosoft.org>
On Mon, Apr 08, 2013 at 12:03:01PM +0200, Jean-Christophe PLAGNIOL-VILLARD wrote:
> On 11:57 Mon 08 Apr , Nicolas Ferre wrote:
> > On 04/08/2013 11:00 AM, Johan Hovold :
> > > On Mon, Apr 08, 2013 at 09:38:07AM +0200, Jean-Christophe PLAGNIOL-VILLARD wrote:
> > >> On 17:12 Sun 07 Apr , Johan Hovold wrote:
[...]
> > >> the RTT is a general purpose timer backuped that we use in linux as a
> > >> RTC with a gpbr to store the time
> > >>
> > >> you need 2 binding on for the RTT one the RTT-rtc
> > >
> > > As in adding some virtual hardware-node which uses the rtt and gpbr as
> > > resources?
> >
> > So, why not simply having a compatibility string that collects the uses
> > of this RTT node:
> >
> > compatible = "atmel,at91sam9260-rtt-as-rtc", "atmel,at91sam9260-rtt";
> >
> > And then "decide which device driver to bind to [the RTT] device"...
> > If the rtt-as-rtc driver is not selected, the device can still be used
> > as a simple "rtt". The board .dts can overload a compatibility string
> > according to the use, etc.
> >
> > Then the way do describe which GPBR to use has still to be discussed.
> > But for the RTT itself, I would keep it simple like that.
>
> no as infact the rtc-at91sam9 should not even exist
> as this is much more generic
>
> we use a backped register and a timer to emulate a RTC this can be unsed by
> any one
>
> and I can use any backuped timer
>
> we need to have frameworks
> where the gpbr are tracked and the rtt
>
> for you describe the resources
>
> rtt0: rtt@fffffd20 {
> compatible = "atmel,at91sam9260-rtt";
> reg = <0xfffffd20 0x10>;
> interrupts = <1 4 7>;
> };
>
> rtc-timer {
> compatible = "linux,rtc-timer";
> timer = <&rtt0>;
> backuped-register = <&gpbr 0>;
> };
>
> this need to SoC implemetation generic
This would indeed be a neat solution, albeit one that requires a lot
work to be realised as both a backup-register and backed-up-timer
framework would need to be implemented.
Thanks,
Johan
next prev parent reply other threads:[~2013-04-08 10:48 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-04 3:54 [PATCH] rtc: rtc-at91sam9.c add DT support Douglas Gilbert
2013-04-04 8:11 ` Nicolas Ferre
2013-04-04 8:11 ` Nicolas Ferre
2013-04-04 13:25 ` Douglas Gilbert
2013-04-04 13:25 ` Douglas Gilbert
2013-04-04 14:08 ` Nicolas Ferre
2013-04-04 14:08 ` Nicolas Ferre
2013-04-04 19:14 ` Douglas Gilbert
2013-04-04 19:14 ` Douglas Gilbert
2013-04-07 15:09 ` Johan Hovold
2013-04-07 15:09 ` Johan Hovold
[not found] ` <1365347572-14972-1-git-send-email-jhovold@gmail.com>
2013-04-08 7:33 ` [RFC 1/5] ARM: at91: add general purpose backup register (GPBR) support Jean-Christophe PLAGNIOL-VILLARD
2013-04-08 7:33 ` Jean-Christophe PLAGNIOL-VILLARD
2013-04-08 8:46 ` Johan Hovold
2013-04-08 8:46 ` Johan Hovold
2013-04-08 10:04 ` Jean-Christophe PLAGNIOL-VILLARD
2013-04-08 10:04 ` Jean-Christophe PLAGNIOL-VILLARD
2013-04-11 12:39 ` Johan Hovold
2013-04-11 12:39 ` Johan Hovold
2013-04-11 14:53 ` Jean-Christophe PLAGNIOL-VILLARD
2013-04-11 14:53 ` Jean-Christophe PLAGNIOL-VILLARD
[not found] ` <1365347572-14972-2-git-send-email-jhovold@gmail.com>
2013-04-08 7:35 ` [RFC 2/5] ARM: at91/dts: " Jean-Christophe PLAGNIOL-VILLARD
2013-04-08 7:35 ` Jean-Christophe PLAGNIOL-VILLARD
[not found] ` <1365347572-14972-4-git-send-email-jhovold@gmail.com>
2013-04-08 7:38 ` [RFC 4/5] RTC: rtc-at91sam9: add device-tree support Jean-Christophe PLAGNIOL-VILLARD
2013-04-08 7:38 ` Jean-Christophe PLAGNIOL-VILLARD
2013-04-08 9:00 ` Johan Hovold
2013-04-08 9:00 ` Johan Hovold
2013-04-08 9:57 ` Nicolas Ferre
2013-04-08 9:57 ` Nicolas Ferre
2013-04-08 10:03 ` Jean-Christophe PLAGNIOL-VILLARD
2013-04-08 10:03 ` Jean-Christophe PLAGNIOL-VILLARD
2013-04-08 10:42 ` Nicolas Ferre
2013-04-08 10:42 ` Nicolas Ferre
2013-04-08 11:02 ` Jean-Christophe PLAGNIOL-VILLARD
2013-04-08 11:02 ` Jean-Christophe PLAGNIOL-VILLARD
2013-04-08 10:48 ` Johan Hovold [this message]
2013-04-08 10:48 ` Johan Hovold
2013-04-08 11:08 ` Jean-Christophe PLAGNIOL-VILLARD
2013-04-08 11:08 ` Jean-Christophe PLAGNIOL-VILLARD
2013-04-08 10:38 ` Johan Hovold
2013-04-08 10:38 ` Johan Hovold
2013-04-08 11:11 ` Jean-Christophe PLAGNIOL-VILLARD
2013-04-08 11:11 ` Jean-Christophe PLAGNIOL-VILLARD
2013-04-11 12:57 ` Johan Hovold
2013-04-11 12:57 ` Johan Hovold
2013-04-04 8:16 ` [PATCH] rtc: rtc-at91sam9.c add DT support Johan Hovold
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=20130408104823.GF25605@localhost \
--to=jhovold@gmail.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 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.