From: Adam Ford <aford173@gmail.com>
To: linux-arm-kernel@lists.infradead.org
Cc: aford@beaconembedded.com, Frank.li@nxp.com,
Adam Ford <aford173@gmail.com>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
devicetree@vger.kernel.org, imx@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: [PATCH V2 03/10] arm64: dts: imx8mp-beacon: Fix RTC capacitive load
Date: Tue, 15 Apr 2025 20:01:29 -0500 [thread overview]
Message-ID: <20250416010141.1785841-3-aford173@gmail.com> (raw)
In-Reply-To: <20250416010141.1785841-1-aford173@gmail.com>
Although not noticeable when used every day, the RTC appears to drift when
left to sit over time. This is due to the capacitive load not being
properly set. Fix RTC drift by correcting the capacitive load setting
from 7000 to 12500, which matches the actual hardware configuration.
Fixes: 25a5ccdce767 ("arm64: dts: freescale: Introduce imx8mp-beacon-kit")
Signed-off-by: Adam Ford <aford173@gmail.com>
---
V2: Change commit message, no active changes.
arch/arm64/boot/dts/freescale/imx8mp-beacon-som.dtsi | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm64/boot/dts/freescale/imx8mp-beacon-som.dtsi b/arch/arm64/boot/dts/freescale/imx8mp-beacon-som.dtsi
index 15f7ab58db36..88561df70d03 100644
--- a/arch/arm64/boot/dts/freescale/imx8mp-beacon-som.dtsi
+++ b/arch/arm64/boot/dts/freescale/imx8mp-beacon-som.dtsi
@@ -257,6 +257,7 @@ eeprom@50 {
rtc: rtc@51 {
compatible = "nxp,pcf85263";
reg = <0x51>;
+ quartz-load-femtofarads = <12500>;
};
};
--
2.48.1
next prev parent reply other threads:[~2025-04-16 1:09 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-16 1:01 [PATCH V2 01/10] arm64: dts: imx8mm-beacon: Fix RTC capacitive load Adam Ford
2025-04-16 1:01 ` [PATCH V2 02/10] arm64: dts: imx8mn-beacon: " Adam Ford
2025-04-16 14:40 ` Frank Li
2025-04-16 1:01 ` Adam Ford [this message]
2025-04-16 14:41 ` [PATCH V2 03/10] arm64: dts: imx8mp-beacon: " Frank Li
2025-04-16 1:01 ` [PATCH V2 04/10] arm64: dts: imx8mm-beacon: Set SAI5 MCLK direction to output for HDMI audio Adam Ford
2025-04-16 14:41 ` Frank Li
2025-04-16 1:01 ` [PATCH V2 05/10] arm64: dts: imx8mn-beacon: " Adam Ford
2025-04-16 14:42 ` Frank Li
2025-04-16 1:01 ` [PATCH V2 06/10] arm64: dts: imx8mm-beacon: Configure Ethernet PHY reset and GPIO IRQ Adam Ford
2025-04-16 14:42 ` Frank Li
2025-04-16 1:01 ` [PATCH V2 07/10] arm64: dts: imx8mn-beacon: " Adam Ford
2025-04-16 14:43 ` Frank Li
2025-04-16 1:01 ` [PATCH V2 08/10] arm64: dts: imx8mm-beacon: Enable RTC interrupt and wakeup-source Adam Ford
2025-04-16 14:44 ` Frank Li
2025-04-16 1:01 ` [PATCH V2 09/10] arm64: dts: imx8mn-beacon: " Adam Ford
2025-04-16 14:44 ` Frank Li
2025-04-16 1:01 ` [PATCH V2 10/10] arm64: dts: imx8mp-beacon: " Adam Ford
2025-04-25 2:07 ` [PATCH V2 01/10] arm64: dts: imx8mm-beacon: Fix RTC capacitive load Shawn Guo
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=20250416010141.1785841-3-aford173@gmail.com \
--to=aford173@gmail.com \
--cc=Frank.li@nxp.com \
--cc=aford@beaconembedded.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.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