From: Peng Fan <peng.fan@oss.nxp.com>
To: Frank Li <Frank.li@nxp.com>
Cc: Meng Li <Meng.Li@windriver.com>,
linux@roeck-us.net, s.hauer@pengutronix.de,
kernel@pengutronix.de, linux-watchdog@vger.kernel.org,
imx@lists.linux.dev, shawnguo@kernel.org, robh@kernel.org,
conor+dt@kernel.org, linux-arm-kernel@lists.infradead.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [v3 PATCH 2/2] arch: arm64: dts: add big-endian property back into watchdog node
Date: Thu, 5 Jun 2025 10:42:20 +0800 [thread overview]
Message-ID: <20250605024220.GE29462@nxa18884-linux> (raw)
In-Reply-To: <aD8MxZUCkzRR0IWt@lizhi-Precision-Tower-5810>
On Tue, Jun 03, 2025 at 10:55:01AM -0400, Frank Li wrote:
>On Tue, Jun 03, 2025 at 12:02:30PM +0800, Meng Li wrote:
>> When verifying watchdog feature on NXP ls1046ardb board,
>> it doesn't work. Because in commit 7c8ffc5555cb("arm64: dts: layerscape:
>
>Watchdog doesn't work on NXP ls1046ardb board because ...
>
>please wrap at 75 chas.
>> remove big-endian for mmc nodes"), it intented to remove the big-endian
>> from mmc node, but the big-endian of watchdog node is also removed by
>> accident. So, add watchdog big-endian property back.
>
>extra empty line here.
>
>> In addition, fsl,ls1046a-wdt allows big-endian property, so add it into
>> compatible property.
>
>In addition, add compatible string fsl,ls1046a-wdt, which allow big-endian
>property.
>
>>
>> Fixes: 7c8ffc5555cb ("arm64: dts: layerscape: remove big-endian for mmc nodes")
>> Cc: stable@vger.kernel.org
>> Signed-off-by: Meng Li <Meng.Li@windriver.com>
>
>after above small fix
>
>Reviewed-by: Frank Li <Frank.Li@nxp.com>
>
>> ---
>> arch/arm64/boot/dts/freescale/fsl-ls1046a.dtsi | 3 ++-
>> 1 file changed, 2 insertions(+), 1 deletion(-)
>>
>> diff --git a/arch/arm64/boot/dts/freescale/fsl-ls1046a.dtsi b/arch/arm64/boot/dts/freescale/fsl-ls1046a.dtsi
>> index 0baf256b4400..983b2f0e8797 100644
>> --- a/arch/arm64/boot/dts/freescale/fsl-ls1046a.dtsi
>> +++ b/arch/arm64/boot/dts/freescale/fsl-ls1046a.dtsi
>> @@ -687,11 +687,12 @@ lpuart5: serial@29a0000 {
>> };
>>
>> wdog0: watchdog@2ad0000 {
>> - compatible = "fsl,imx21-wdt";
>> + compatible = "fsl,ls1046a-wdt", "fsl,imx21-wdt";
So ls1046a is really compatible with imx21?
Regards,
Peng
>> reg = <0x0 0x2ad0000 0x0 0x10000>;
>> interrupts = <GIC_SPI 83 IRQ_TYPE_LEVEL_HIGH>;
>> clocks = <&clockgen QORIQ_CLK_PLATFORM_PLL
>> QORIQ_CLK_PLL_DIV(2)>;
>> + big-endian;
>> };
>>
>> edma0: dma-controller@2c00000 {
>> --
>> 2.34.1
>>
next prev parent reply other threads:[~2025-06-05 1:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-03 4:02 [v3 PATCH 0/2] create patches for nxp-ls1046a platform watchdog feature Meng Li
2025-06-03 4:02 ` [v3 PATCH 1/2] dt-bindings: watchdog: fsl-imx-wdt: add compatible string fsl,ls1046a-wdt Meng Li
2025-06-03 14:50 ` Frank Li
2025-06-03 4:02 ` [v3 PATCH 2/2] arch: arm64: dts: add big-endian property back into watchdog node Meng Li
2025-06-03 14:55 ` Frank Li
2025-06-05 2:42 ` Peng Fan [this message]
2025-06-05 1:48 ` Li, Meng
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=20250605024220.GE29462@nxa18884-linux \
--to=peng.fan@oss.nxp.com \
--cc=Frank.li@nxp.com \
--cc=Meng.Li@windriver.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--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;
as well as URLs for NNTP newsgroup(s).