public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Nishanth Menon <nm@ti.com>
To: Wadim Egorov <w.egorov@phytec.de>
Cc: <vigneshr@ti.com>, <kristo@kernel.org>, <robh@kernel.org>,
	<krzk+dt@kernel.org>, <conor+dt@kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>,
	<upstream@lists.phytec.de>
Subject: Re: [PATCH 1/3] arm64: dts: ti: k3-am642-phyboard-electra-peb-c-010: Fix icssg-prueth schema warning
Date: Wed, 26 Nov 2025 07:29:08 -0600	[thread overview]
Message-ID: <20251126132908.4l2w4lu75prnilze@ninth> (raw)
In-Reply-To: <20251126084403.24146-1-w.egorov@phytec.de>

On 09:44-20251126, Wadim Egorov wrote:
> Reduce length of dma-names and dmas properties for icssg1-ethernet
> node to comply with ti,icssg-prueth schema constraints. The previous
> entries exceeded the allowed count and triggered dtschema warnings
> during validation.
> 

Fixes: e53fbf955ea7 ("arm64: dts: ti: k3-am642-phyboard-electra: Add PEB-C-010 Overlay")

Perhaps?

> Signed-off-by: Wadim Egorov <w.egorov@phytec.de>
> ---
>  .../boot/dts/ti/k3-am642-phyboard-electra-peb-c-010.dtso   | 7 ++-----
>  1 file changed, 2 insertions(+), 5 deletions(-)
> 
> diff --git a/arch/arm64/boot/dts/ti/k3-am642-phyboard-electra-peb-c-010.dtso b/arch/arm64/boot/dts/ti/k3-am642-phyboard-electra-peb-c-010.dtso
> index 7fc73cfacadb..1176a52d560b 100644
> --- a/arch/arm64/boot/dts/ti/k3-am642-phyboard-electra-peb-c-010.dtso
> +++ b/arch/arm64/boot/dts/ti/k3-am642-phyboard-electra-peb-c-010.dtso
> @@ -30,13 +30,10 @@ icssg1-ethernet {
>  				<&main_pktdma 0xc206 15>, /* egress slice 1 */
>  				<&main_pktdma 0xc207 15>, /* egress slice 1 */
>  				<&main_pktdma 0x4200 15>, /* ingress slice 0 */
> -				<&main_pktdma 0x4201 15>, /* ingress slice 1 */
> -				<&main_pktdma 0x4202 0>, /* mgmnt rsp slice 0 */
> -				<&main_pktdma 0x4203 0>; /* mgmnt rsp slice 1 */
> +				<&main_pktdma 0x4201 15>; /* ingress slice 1 */
>  		dma-names = "tx0-0", "tx0-1", "tx0-2", "tx0-3",
>  					"tx1-0", "tx1-1", "tx1-2", "tx1-3",
> -					"rx0", "rx1",
> -					"rxmgm0", "rxmgm1";
> +					"rx0", "rx1";
>  
>  		firmware-name = "ti-pruss/am65x-sr2-pru0-prueth-fw.elf",
>  				"ti-pruss/am65x-sr2-rtu0-prueth-fw.elf",
> -- 
> 2.48.1
> 

-- 
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3  1A34 DDB5 849D 1736 249D
https://ti.com/opensource


      parent reply	other threads:[~2025-11-26 13:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-26  8:44 [PATCH 1/3] arm64: dts: ti: k3-am642-phyboard-electra-peb-c-010: Fix icssg-prueth schema warning Wadim Egorov
2025-11-26  8:44 ` [PATCH 2/3] arm64: dts: ti: k3-am642-phyboard-electra-x27-gpio1-spi1-uart3: Fix schema warnings Wadim Egorov
2025-11-26 13:28   ` Nishanth Menon
2025-11-26  8:44 ` [PATCH 3/3] arm64: dts: ti: k3-am62-lp-sk-nand: Rename pinctrls to fix " Wadim Egorov
2025-11-26 13:27   ` Nishanth Menon
2025-11-26 13:29 ` Nishanth Menon [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=20251126132908.4l2w4lu75prnilze@ninth \
    --to=nm@ti.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=kristo@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=upstream@lists.phytec.de \
    --cc=vigneshr@ti.com \
    --cc=w.egorov@phytec.de \
    /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