From: claudiu beznea <claudiu.beznea@tuxon.dev>
To: Alexander Dahl <ada@thorsis.com>, linux-clk@vger.kernel.org
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Codrin Ciubotariu <codrin.ciubotariu@microchip.com>,
Sandeep Sheriker Mallikarjun
<sandeepsheriker.mallikarjun@microchip.com>,
Nicolas Ferre <nicolas.ferre@microchip.com>,
Tudor Ambarus <tudor.ambarus@linaro.org>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] ARM: dts: microchip: sam9x60: Fix rtc/rtt clocks
Date: Sat, 24 Aug 2024 20:28:08 +0300 [thread overview]
Message-ID: <1f570dfd-ca07-4dfc-8c2b-de551cf24415@tuxon.dev> (raw)
In-Reply-To: <20240821055136.6858-1-ada@thorsis.com>
On 21.08.2024 08:51, Alexander Dahl wrote:
> The RTC and RTT peripherals use the "timing domain slow clock (TD_SLCK),
> sourced from the 32.768 kHz crystal oscillator.
>
> (The previously used Monitoring domain slow clock (MD_SLCK) is sourced
> from an internal RC oscillator which is most probably not precise enough
> for real time clock purposes.)
>
> Fixes: 1e5f532c2737 ("ARM: dts: at91: sam9x60: add device tree for soc and board")
> Fixes: 5f6b33f46346 ("ARM: dts: sam9x60: add rtt")
> Signed-off-by: Alexander Dahl <ada@thorsis.com>
Applied to at91-dt, thanks!
prev parent reply other threads:[~2024-08-24 17:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-20 13:27 [PATCH] ARM: dts: microchip: sam9x60: Fix rtc/rtt clock parent Alexander Dahl
2024-08-21 5:51 ` [PATCH v2] ARM: dts: microchip: sam9x60: Fix rtc/rtt clocks Alexander Dahl
2024-08-21 23:52 ` Alexandre Belloni
2024-08-22 6:53 ` Alexander Dahl
2024-08-22 8:17 ` Alexandre Belloni
2024-08-22 10:25 ` Alexander Dahl
2024-08-24 17:28 ` claudiu beznea [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=1f570dfd-ca07-4dfc-8c2b-de551cf24415@tuxon.dev \
--to=claudiu.beznea@tuxon.dev \
--cc=ada@thorsis.com \
--cc=alexandre.belloni@bootlin.com \
--cc=codrin.ciubotariu@microchip.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas.ferre@microchip.com \
--cc=robh@kernel.org \
--cc=sandeepsheriker.mallikarjun@microchip.com \
--cc=tudor.ambarus@linaro.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