mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Vignesh Raghavendra <vigneshr@ti.com>
To: Kendall Willis <k-willis@ti.com>, Nishanth Menon <nm@ti.com>,
	Tero Kristo <kristo@kernel.org>, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>, Dhruva Gole <d-gole@ti.com>,
	Bryan Brattlof <bb@ti.com>
Cc: <vishalm@ti.com>, <sebin.francis@ti.com>, <msp@baylibre.com>,
	<khilman@baylibre.com>, <linux-arm-kernel@lists.infradead.org>,
	<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 2/4] arm64: boot: dts: ti: k3-am62l-wakeup: create label for target-module
Date: Fri, 6 Feb 2026 10:11:14 +0530	[thread overview]
Message-ID: <3bac0dc6-6e58-4a04-a0c6-a6646e261f6e@ti.com> (raw)
In-Reply-To: <20260127-v6-19-wkup-uart-wakeup-v3-2-e7ccac761f3a@ti.com>

Hi

On 28/01/26 04:09, Kendall Willis wrote:
> Add label to the target-module node so that it can easily be referenced.
> The node specifically configures the SYSCONFIG related registers for WKUP
> UART.
> 
> Reviewed-by: Dhruva Gole <d-gole@ti.com>
> Signed-off-by: Kendall Willis <k-willis@ti.com>
> ---
>  arch/arm64/boot/dts/ti/k3-am62l-wakeup.dtsi | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/arch/arm64/boot/dts/ti/k3-am62l-wakeup.dtsi b/arch/arm64/boot/dts/ti/k3-am62l-wakeup.dtsi
> index 61bfcdcfc66ea8d802a36ed43cd01fbbf3decc70..e9d638d9ffd3a52aa6e0df70f6003879bc292358 100644
> --- a/arch/arm64/boot/dts/ti/k3-am62l-wakeup.dtsi
> +++ b/arch/arm64/boot/dts/ti/k3-am62l-wakeup.dtsi
> @@ -81,7 +81,7 @@ wkup_i2c0: i2c@2b200000 {
>  		status = "disabled";
>  	};
>  
> -	target-module@2b300050 {
> +	wkup_uart0_interconnect: target-module@2b300050 {

This is not an interconnect node, so the label is a bit misleading, just
use something like wkup_uart_target or something similar to how these
are labeled in arch/arm/boot/dts/ti/

>  		compatible = "ti,sysc-omap2", "ti,sysc";
>  		reg = <0x00 0x2b300050 0x00 0x4>,
>  		      <0x00 0x2b300054 0x00 0x4>,
> 

-- 
Regards
Vignesh
https://ti.com/opensource


  reply	other threads:[~2026-02-06  4:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-27 22:39 [PATCH v3 0/4] arm64: boot: dts: ti: k3-am62l: allow WKUP UART wakeup from LPM Kendall Willis
2026-01-27 22:39 ` [PATCH v3 1/4] arm64: dts: ti: k3-am62l: include WKUP_UART0 in wakeup peripheral window Kendall Willis
2026-01-27 22:39 ` [PATCH v3 2/4] arm64: boot: dts: ti: k3-am62l-wakeup: create label for target-module Kendall Willis
2026-02-06  4:41   ` Vignesh Raghavendra [this message]
2026-02-12 22:06     ` Kendall Willis
2026-01-27 22:39 ` [PATCH v3 3/4] arm64: boot: dts: ti: k3-am62l3-evm: define WKUP_UART0 pins Kendall Willis
2026-01-27 22:39 ` [PATCH v3 4/4] arm64: boot: dts: ti: k3-am62l3-evm: enable target-module node Kendall Willis

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=3bac0dc6-6e58-4a04-a0c6-a6646e261f6e@ti.com \
    --to=vigneshr@ti.com \
    --cc=bb@ti.com \
    --cc=conor+dt@kernel.org \
    --cc=d-gole@ti.com \
    --cc=devicetree@vger.kernel.org \
    --cc=k-willis@ti.com \
    --cc=khilman@baylibre.com \
    --cc=kristo@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=msp@baylibre.com \
    --cc=nm@ti.com \
    --cc=robh@kernel.org \
    --cc=sebin.francis@ti.com \
    --cc=vishalm@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®