From: Lokesh Vutla <lokeshvutla@ti.com>
To: Vignesh Raghavendra <vigneshr@ti.com>
Cc: <u-boot@lists.denx.de>, Tom Rini <trini@konsulko.com>
Subject: Re: [PATCH -next] ARM: dts: k3-j7200-common-proc-board-u-boot.dtsi: Fix dtc warnings
Date: Mon, 21 Jun 2021 17:42:15 +0530 [thread overview]
Message-ID: <c6216f4e-e15d-6744-c830-f27a944b2a87@ti.com> (raw)
In-Reply-To: <20210614084239.17833-1-vigneshr@ti.com>
+Tom
On 14/06/21 2:12 pm, Vignesh Raghavendra wrote:
> Fix following dtc warning by explicitly setting up #size-cells
> and #address-cells when overriding node in -u-boot.dtsi
>
> arch/arm/dts/k3-j7200-common-proc-board.dtb: Warning (reg_format):
> /bus@100000/bus@28380000/mcu-navss/ringacc@2b800000:reg: property has
> invalid length (80 bytes) (#address-cells == 2, #size-cells == 1)
>
> Signed-off-by: Vignesh Raghavendra <vigneshr@ti.com>
Tom,
If you don't mind, can you pull the patch to next directly? This fixed the DT
warning on j7200 builds.
Thanks and regards,
Lokesh
> ---
> arch/arm/dts/k3-j7200-common-proc-board-u-boot.dtsi | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/arch/arm/dts/k3-j7200-common-proc-board-u-boot.dtsi b/arch/arm/dts/k3-j7200-common-proc-board-u-boot.dtsi
> index 41ce9fcb59..786cc48050 100644
> --- a/arch/arm/dts/k3-j7200-common-proc-board-u-boot.dtsi
> +++ b/arch/arm/dts/k3-j7200-common-proc-board-u-boot.dtsi
> @@ -43,6 +43,8 @@
>
> mcu-navss{
> u-boot,dm-spl;
> + #address-cells = <2>;
> + #size-cells = <2>;
>
> ringacc@2b800000 {
> reg = <0x0 0x2b800000 0x0 0x400000>,
>
next prev parent reply other threads:[~2021-06-21 12:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-14 8:42 [PATCH -next] ARM: dts: k3-j7200-common-proc-board-u-boot.dtsi: Fix dtc warnings Vignesh Raghavendra
2021-06-21 12:12 ` Lokesh Vutla [this message]
2021-06-21 17:18 ` Tom Rini
2021-06-24 13:15 ` Tom Rini
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=c6216f4e-e15d-6744-c830-f27a944b2a87@ti.com \
--to=lokeshvutla@ti.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=vigneshr@ti.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.