From: Shawn Guo <shawnguo@kernel.org>
To: Biwen Li <biwen.li@nxp.com>
Cc: mark.rutland@arm.com, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, leoyang.li@nxp.com,
robh+dt@kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: arm64: ls1028a-qds: correct bus of rtc
Date: Sun, 6 Oct 2019 09:01:24 +0800 [thread overview]
Message-ID: <20191006010123.GF7150@dragon> (raw)
In-Reply-To: <20190904085104.44709-1-biwen.li@nxp.com>
On Wed, Sep 04, 2019 at 04:51:04PM +0800, Biwen Li wrote:
> The rtc is on i2c2 bus(hardware), not on i2c1 channel 3,
> so correct it
>
> Signed-off-by: Biwen Li <biwen.li@nxp.com>
This looks a like a fix. Do we need a Fixes tag for it?
> ---
> arch/arm64/boot/dts/freescale/fsl-ls1028a-qds.dts | 13 ++++++++-----
> 1 file changed, 8 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 de6ef39f3118..6c0540ad9c59 100644
> --- a/arch/arm64/boot/dts/freescale/fsl-ls1028a-qds.dts
> +++ b/arch/arm64/boot/dts/freescale/fsl-ls1028a-qds.dts
> @@ -133,11 +133,6 @@
> vcc-supply = <&sb_3v3>;
> };
>
> - rtc@51 {
> - compatible = "nxp,pcf2129";
> - reg = <0x51>;
> - };
> -
> eeprom@56 {
> compatible = "atmel,24c512";
> reg = <0x56>;
> @@ -166,6 +161,14 @@
> };
> };
>
> +&i2c1 {
> + status = "okay";
Please have a newline between properties and child node.
Shawn
> + rtc@51 {
> + compatible = "nxp,pcf2129";
> + reg = <0x51>;
> + };
> +};
> +
> &sai1 {
> status = "okay";
> };
> --
> 2.17.1
>
prev parent reply other threads:[~2019-10-06 1:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-04 8:51 arm64: ls1028a-qds: correct bus of rtc Biwen Li
2019-10-06 1:01 ` Shawn Guo [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=20191006010123.GF7150@dragon \
--to=shawnguo@kernel.org \
--cc=biwen.li@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@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).