linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Li Yang <leoyang.li@nxp.com>
To: Bjorn Helgaas <bhelgaas@google.com>,
	Rob Herring <robh+dt@kernel.org>, Shawn Guo <shawnguo@kernel.org>
Cc: linux-pci@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, Biwen Li <biwen.li@nxp.com>,
	Li Yang <leoyang.lil@nxp.com>
Subject: [PATCH 08/11] arm64: dts: ls1028a-qds: move rtc node to the correct i2c bus
Date: Fri, 12 Nov 2021 16:34:54 -0600	[thread overview]
Message-ID: <20211112223457.10599-9-leoyang.li@nxp.com> (raw)
In-Reply-To: <20211112223457.10599-1-leoyang.li@nxp.com>

From: Biwen Li <biwen.li@nxp.com>

The i2c rtc is on i2c2 bus not i2c1 bus, so fix it in dts.

Signed-off-by: Biwen Li <biwen.li@nxp.com>
Signed-off-by: Li Yang <leoyang.lil@nxp.com>
---
 arch/arm64/boot/dts/freescale/fsl-ls1028a-qds.dts | 14 +++++++++-----
 1 file changed, 9 insertions(+), 5 deletions(-)

diff --git a/arch/arm64/boot/dts/freescale/fsl-ls1028a-qds.dts b/arch/arm64/boot/dts/freescale/fsl-ls1028a-qds.dts
index 0a8f68ff578f..d10593a191e5 100644
--- a/arch/arm64/boot/dts/freescale/fsl-ls1028a-qds.dts
+++ b/arch/arm64/boot/dts/freescale/fsl-ls1028a-qds.dts
@@ -276,11 +276,6 @@ temperature-sensor@4c {
 				vcc-supply = <&sb_3v3>;
 			};
 
-			rtc@51 {
-				compatible = "nxp,pcf2129";
-				reg = <0x51>;
-			};
-
 			eeprom@56 {
 				compatible = "atmel,24c512";
 				reg = <0x56>;
@@ -322,6 +317,15 @@ mux: mux-controller {
 
 };
 
+&i2c1 {
+	status = "okay";
+
+	rtc@51 {
+		compatible = "nxp,pcf2129";
+		reg = <0x51>;
+	};
+};
+
 &enetc_port1 {
 	phy-handle = <&qds_phy1>;
 	phy-connection-type = "rgmii-id";
-- 
2.25.1


  parent reply	other threads:[~2021-11-12 22:35 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-12 22:34 [PATCH 00/11] ls1028a device tree updates Li Yang
2021-11-12 22:34 ` [PATCH 01/11] dt-bindings: pci: layerscape-pci: Add EP mode compatible strings for ls1028a Li Yang
2021-11-12 22:34 ` [PATCH 02/11] dt-bindings: pci: layerscape-pci: define aer/pme interrupts Li Yang
2021-11-12 22:34 ` [PATCH 03/11] arm64: dts: ls1028a: Add PCIe EP nodes Li Yang
2021-11-12 22:34 ` [PATCH 04/11] arm64: dts: ls1028a: add ftm_alarm1 node to be used as wakeup source Li Yang
2021-11-12 22:34 ` [PATCH 05/11] arm64: dts: ls1028a: add flextimer based pwm nodes Li Yang
2021-11-12 22:34 ` [PATCH 06/11] arm64: dts: ls1028a-rdb: reorder nodes to be alphabetic Li Yang
2021-11-12 22:34 ` [PATCH 07/11] arm64: dts: ls1028a-rdb: enable pwm0 Li Yang
2021-11-12 22:34 ` Li Yang [this message]
2021-11-12 22:34 ` [PATCH 09/11] arm64: dts: ls1028a-qds: enable lpuart1 Li Yang
2021-11-12 22:34 ` [PATCH 10/11] arm64: dts: ls1028a-qds: add overlays for various serdes protocols Li Yang
2021-11-12 22:34 ` [PATCH 11/11] arm64: dts: ls1028a-qds: enable optee node Li Yang
2021-11-13  6:36   ` Sahil Malhotra
2021-11-13  7:05     ` Leo Li

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=20211112223457.10599-9-leoyang.li@nxp.com \
    --to=leoyang.li@nxp.com \
    --cc=bhelgaas@google.com \
    --cc=biwen.li@nxp.com \
    --cc=devicetree@vger.kernel.org \
    --cc=leoyang.lil@nxp.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).