From: Nicolas Ferre <nicolas.ferre@microchip.com>
To: Alexandre Belloni <alexandre.belloni@bootlin.com>,
Alessandro Zummo <a.zummo@towertech.it>,
Ludovic Desroches <ludovic.desroches@microchip.com>
Cc: <linux-rtc@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] rtc: at91rm9200: Add sam9x60 compatible
Date: Tue, 17 Nov 2020 16:48:28 +0100 [thread overview]
Message-ID: <1c5f0d70-93f5-0285-66df-43a9f3611e90@microchip.com> (raw)
In-Reply-To: <20201117133920.1229679-1-alexandre.belloni@bootlin.com>
On 17/11/2020 at 14:39, Alexandre Belloni wrote:
> Handle the sam9x60 RTC. While it can work with the at91sam9x5 fallback, it
> has crystal correction support and doesn't need to shadow IMR.
>
> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Acked-by: Nicolas Ferre <nicolas.ferre@microchip.com>
> ---
> drivers/rtc/rtc-at91rm9200.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/rtc/rtc-at91rm9200.c b/drivers/rtc/rtc-at91rm9200.c
> index 1eea187d9850..da24e68adcca 100644
> --- a/drivers/rtc/rtc-at91rm9200.c
> +++ b/drivers/rtc/rtc-at91rm9200.c
> @@ -437,6 +437,9 @@ static const struct of_device_id at91_rtc_dt_ids[] = {
> }, {
> .compatible = "atmel,sama5d2-rtc",
> .data = &sama5d4_config,
> + }, {
> + .compatible = "microchip,sam9x60-rtc",
> + .data = &sama5d4_config,
> }, {
> /* sentinel */
> }
> --
> 2.28.0
>
--
Nicolas Ferre
prev parent reply other threads:[~2020-11-17 15:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-17 13:39 [PATCH] rtc: at91rm9200: Add sam9x60 compatible Alexandre Belloni
2020-11-17 15:48 ` Nicolas Ferre [this message]
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=1c5f0d70-93f5-0285-66df-43a9f3611e90@microchip.com \
--to=nicolas.ferre@microchip.com \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@bootlin.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=ludovic.desroches@microchip.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).