mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bryan Brattlof <bb@ti.com>
To: Sai Sree Kartheek Adivi <s-adivi@ti.com>
Cc: <nm@ti.com>, <vigneshr@ti.com>, <kristo@kernel.org>,
	<robh@kernel.org>, <krzk+dt@kernel.org>, <conor+dt@kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<hnagalla@ti.com>, <jm@ti.com>
Subject: Re: [PATCH 2/2] arm64: dts: ti: k3-am62l: Add alias node
Date: Wed, 30 Sep 2026 09:40:24 -0500	[thread overview]
Message-ID: <20260930144024.7g7ttyokolvsc2to@bryanbrattlof.com> (raw)
In-Reply-To: <20260928034115.1084840-2-s-adivi@ti.com>

On September 28, 2026 thus sayeth Sai Sree Kartheek Adivi:
> From: Judith Mendez <jm@ti.com>
> 
> Add alias node for am62l3. This is mainly to link mmc0
> alias to eMMC and mmc1 alias to SD in u-boot.
> 
> Signed-off-by: Judith Mendez <jm@ti.com>
> Signed-off-by: Sai Sree Kartheek Adivi <s-adivi@ti.com>
> ---
>  arch/arm64/boot/dts/ti/k3-am62l3-evm.dts | 5 +++++
>  1 file changed, 5 insertions(+)
> 
> diff --git a/arch/arm64/boot/dts/ti/k3-am62l3-evm.dts b/arch/arm64/boot/dts/ti/k3-am62l3-evm.dts
> index 964387eb51788..f357dc56de1c7 100644
> --- a/arch/arm64/boot/dts/ti/k3-am62l3-evm.dts
> +++ b/arch/arm64/boot/dts/ti/k3-am62l3-evm.dts
> @@ -21,6 +21,11 @@ / {
>  	compatible = "ti,am62l3-evm", "ti,am62l3";
>  	model = "Texas Instruments AM62L3 Evaluation Module";
>  
> +	aliases {
> +		mmc0 = &sdhci0;
> +		mmc1 = &sdhci1;

Why would we need to alias MMC nodes like this?

~Bryan

  reply	other threads:[~2026-09-30 14:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-28  3:41 [PATCH 1/2] arm64: dts: ti: k3-am62l-main: Add ADC nodes Sai Sree Kartheek Adivi
2026-09-28  3:41 ` [PATCH 2/2] arm64: dts: ti: k3-am62l: Add alias node Sai Sree Kartheek Adivi
2026-09-30 14:40   ` Bryan Brattlof [this message]
2026-09-28 16:49 ` [PATCH 1/2] arm64: dts: ti: k3-am62l-main: Add ADC nodes Vignesh Raghavendra
2026-09-28 17:11 ` Judith Mendez

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=20260930144024.7g7ttyokolvsc2to@bryanbrattlof.com \
    --to=bb@ti.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=hnagalla@ti.com \
    --cc=jm@ti.com \
    --cc=kristo@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nm@ti.com \
    --cc=robh@kernel.org \
    --cc=s-adivi@ti.com \
    --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 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®