From: boris.brezillon@free-electrons.com (Boris BREZILLON)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v7 06/10] rtc: at91sam9: rework the Kconfig description
Date: Tue, 23 Sep 2014 12:11:44 +0200 [thread overview]
Message-ID: <20140923121144.0fd5d3c8@bbrezillon> (raw)
In-Reply-To: <542146AF.3060807@atmel.com>
On Tue, 23 Sep 2014 12:08:47 +0200
Nicolas Ferre <nicolas.ferre@atmel.com> wrote:
> On 23/09/2014 11:38, Boris BREZILLON :
> > Remove all references to AT91CAP9 SoC which has been removed.
> > Rework the help message to remove any specific references to AT91SAM9 SoCs.
> >
> > Signed-off-by: Boris BREZILLON <boris.brezillon@free-electrons.com>
> > ---
> > drivers/rtc/Kconfig | 17 +++++++++--------
> > 1 file changed, 9 insertions(+), 8 deletions(-)
> >
> > diff --git a/drivers/rtc/Kconfig b/drivers/rtc/Kconfig
> > index 7d76da8..455f2c3 100644
> > --- a/drivers/rtc/Kconfig
> > +++ b/drivers/rtc/Kconfig
> > @@ -1079,17 +1079,18 @@ config RTC_DRV_AT91RM9200
> > this is powered by the backup power supply.
> >
> > config RTC_DRV_AT91SAM9
> > - tristate "AT91SAM9x/AT91CAP9 RTT as RTC"
> > + tristate "AT91SAM9 RTT as RTC"
> > depends on ARCH_AT91 && !(ARCH_AT91RM9200 || ARCH_AT91X40)
> > select MFD_SYSCON
> > help
> > - RTC driver for the Atmel AT91SAM9x and AT91CAP9 internal RTT
> > - (Real Time Timer). These timers are powered by the backup power
> > - supply (such as a small coin cell battery), but do not need to
> > - be used as RTCs.
> > -
> > - (On AT91SAM9rl and AT91SAM9G45 chips you probably want to use the
> > - dedicated RTC module and leave the RTT available for other uses.)
> > + Some AT91SAM9 SoCs provide an RTT (Real Time Timer) block which
> > + can be used as an RTC thanks to the backup power supply (e.g. a
> > + small coin cell battery) which keeps this block and the GPBR
> > + (General Purpose Backup Registers) block powered when the device
> > + is shutdown.
> > + Some AT91SAM9 SoCs provide a real RTC block, on those ones you'd
> > + probably want to use the real RTC block instead of the RTT as an
> > + RTT driver.
>
> You mean:
> "instead of the RTT as an RTC"
Yep, that's what I meant.
>
> With that, good description: thanks!
>
> Acked-by: Nicolas Ferre <nicolas.ferre@atmel.com>
>
> So, now we can think of what to do with the series:
>
> - Johan, do you want to "Ack" it?
> - may I take it through the arm-soc git tree (likely for the 3.19 dev.
> phase).
>
> Your thoughts?
>
> Bye,
>
> >
> > config RTC_DRV_AT91SAM9_RTT
> > int
> >
>
>
--
Boris Brezillon, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-09-23 10:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-23 9:38 [PATCH v7 00/10] rtc: at91sam9: add DT support Boris BREZILLON
2014-09-23 9:38 ` [PATCH v7 01/10] rtc: at91sam9: remove references to mach specific headers Boris BREZILLON
2014-09-23 9:38 ` [PATCH v7 02/10] rtc: at91sam9: use standard readl/writel functions instead of raw versions Boris BREZILLON
2014-09-23 9:38 ` [PATCH v7 03/10] rtc: at91sam9: replace devm_ioremap by devm_ioremap_resource Boris BREZILLON
2014-09-23 9:38 ` [PATCH v7 04/10] rtc: at91sam9: add DT support Boris BREZILLON
2014-09-23 9:38 ` [PATCH v7 05/10] rtc: at91sam9: make use of syscon/regmap to access GPBR registers Boris BREZILLON
2014-09-23 9:38 ` [PATCH v7 06/10] rtc: at91sam9: rework the Kconfig description Boris BREZILLON
2014-09-23 10:08 ` Nicolas Ferre
2014-09-23 10:11 ` Boris BREZILLON [this message]
2014-09-23 10:39 ` Johan Hovold
2014-09-23 9:38 ` [PATCH v7 07/10] ARM: at91: add clk_lookup entry for RTT devices Boris BREZILLON
2014-09-23 9:38 ` [PATCH v7 08/10] rtc: at91sam9: use clk API instead of relying on AT91_SLOW_CLOCK Boris BREZILLON
2014-09-23 10:33 ` Johan Hovold
2014-09-23 11:05 ` Boris BREZILLON
2014-09-23 9:38 ` [PATCH v7 09/10] rtc: at91sam9: add DT bindings documentation Boris BREZILLON
2014-09-23 9:38 ` [PATCH v7 10/10] mfd: syscon: add Atmel GPBR DT bindings documention 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=20140923121144.0fd5d3c8@bbrezillon \
--to=boris.brezillon@free-electrons.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).