From: Frank Li <Frank.li@nxp.com>
To: Meng Li <Meng.Li@windriver.com>
Cc: 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: [PATCH] arch: arm64: dts: add big-endian property back into watchdog node
Date: Wed, 28 May 2025 12:10:42 -0400 [thread overview]
Message-ID: <aDc1gobqagsYohO0@lizhi-Precision-Tower-5810> (raw)
In-Reply-To: <20250528111751.3505224-1-Meng.Li@windriver.com>
On Wed, May 28, 2025 at 07:17:51PM +0800, Meng Li wrote:
> When verifying watchdog feature on NXP ls1046ardb board,
> it doesn't work. Because the big-endian is deleted by accident,
> add it back.
>
> Fixes: 7c8ffc5555cb ("arm64: dts: layerscape: remove big-endian for mmc nodes")
fix tags should be wrong.
I remember I tested without big-endian. If it is wrong, please revert original
patch and provide enough reason.
Frank
> Cc: stable@vger.kernel.org
> Signed-off-by: Meng Li <Meng.Li@windriver.com>
> ---
> arch/arm64/boot/dts/freescale/fsl-ls1046a.dtsi | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/arch/arm64/boot/dts/freescale/fsl-ls1046a.dtsi b/arch/arm64/boot/dts/freescale/fsl-ls1046a.dtsi
> index 4d75bff0d548..e15ec2e1cb04 100644
> --- a/arch/arm64/boot/dts/freescale/fsl-ls1046a.dtsi
> +++ b/arch/arm64/boot/dts/freescale/fsl-ls1046a.dtsi
> @@ -753,6 +753,7 @@ wdog0: watchdog@2ad0000 {
> 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-05-28 16:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-28 11:17 [PATCH] arch: arm64: dts: add big-endian property back into watchdog node Meng Li
2025-05-28 12:09 ` Krzysztof Kozlowski
2025-05-29 1:46 ` Li, Meng
2025-05-28 12:37 ` Rob Herring (Arm)
2025-05-29 4:07 ` Li, Meng
2025-05-29 16:05 ` Frank Li
2025-05-30 1:10 ` Li, Meng
2025-05-30 2:12 ` Li, Meng
2025-05-30 15:10 ` Frank Li
2025-05-31 9:10 ` Li, Meng
2025-05-28 16:10 ` Frank Li [this message]
2025-05-29 5:50 ` Li, Meng
2025-05-29 16:00 ` Frank Li
2025-05-30 0:57 ` Li, Meng
2025-05-28 16:16 ` Frank Li
2025-05-29 1:39 ` 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=aDc1gobqagsYohO0@lizhi-Precision-Tower-5810 \
--to=frank.li@nxp.com \
--cc=Meng.Li@windriver.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@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