linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: jhovold@gmail.com (Johan Hovold)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC 1/5] ARM: at91: add general purpose backup register (GPBR) support
Date: Mon, 8 Apr 2013 10:46:18 +0200	[thread overview]
Message-ID: <20130408084618.GB25605@localhost> (raw)
In-Reply-To: <20130408073329.GO20693@game.jcrosoft.org>

On Mon, Apr 08, 2013 at 09:33:29AM +0200, Jean-Christophe PLAGNIOL-VILLARD wrote:
> On 17:12 Sun 07 Apr     , Johan Hovold wrote:
> > 
> > Add General Purpose Backup Register (GPBR) support.
> > 
> > Most at91 SoCs have at least four 32-bit General Purpose Backup
> > Registers (GPBR) powered by backup-power (VDDBU). One such register is
> > currently used by rtc-at91sam9 driver to store the RTC time base.
> > 
> > Make sure the registers are mapped by arch setup code and add generic
> > accessors for in-kernel use.
> > 
> > This is a step in adding device-tree support to the rtc-at91sam9 driver.
> > 
> This is a regression
> 
> we loose the tracking of what request and use the GPBR

Implementing the GPBR accessors using a simple global resource was one
quick way forward to decouple and generalise the GPBR. Of course, this
could be turned into a more elaborate framework or driver where
registers are requested and released by other drivers and possibly also
by user-space.

Thanks,
Johan

  reply	other threads:[~2013-04-08  8:46 UTC|newest]

Thread overview: 24+ 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 13:25   ` Douglas Gilbert
2013-04-04 14:08     ` Nicolas Ferre
2013-04-04 19:14       ` Douglas Gilbert
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  8:46             ` Johan Hovold [this message]
2013-04-08 10:04               ` Jean-Christophe PLAGNIOL-VILLARD
2013-04-11 12:39                 ` Johan Hovold
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
     [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  9:00               ` Johan Hovold
2013-04-08  9:57                 ` Nicolas Ferre
2013-04-08 10:03                   ` Jean-Christophe PLAGNIOL-VILLARD
2013-04-08 10:42                     ` Nicolas Ferre
2013-04-08 11:02                       ` Jean-Christophe PLAGNIOL-VILLARD
2013-04-08 10:48                     ` Johan Hovold
2013-04-08 11:08                       ` Jean-Christophe PLAGNIOL-VILLARD
2013-04-08 10:38                   ` Johan Hovold
2013-04-08 11:11                     ` Jean-Christophe PLAGNIOL-VILLARD
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=20130408084618.GB25605@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 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).