mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Ng, Tze Yee" <tze.yee.ng@altera.com>
To: Dinh Nguyen <dinguyen@kernel.org>,
	"Ng, Tze Yee" <tze.yee.ng@altera.com>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] arm64: dts: socfpga: agilex: add emmc support
Date: Wed, 14 Jan 2026 08:19:35 +0000	[thread overview]
Message-ID: <055d2e9d-ec73-4f9e-853c-68a4e64be653@altera.com> (raw)
In-Reply-To: <e781a5d3-4c38-4547-89ba-168c6ee1e018@kernel.org>

On 14/1/2026 1:54 am, Dinh Nguyen wrote:
> [CAUTION: This email is from outside your organization. Unless you trust 
> the sender, do not click on links or open attachments as it may be a 
> fraudulent email attempting to steal your information and/or compromise 
> your computer.]
> 
> On 1/11/26 21:35, tzeyee.ng@altera.com wrote:
>> From: Ng Tze Yee <tzeyee.ng@altera.com>
>>
>> The Agilex devkit supports a separate NAND/eMMC daughter card. The
>> NAND/eMMC daughter card replaces the SDMMC slot that is on the default
>> daughter card and thus requires a separate board dts file.
>>
>> New eMMC dts which is based on the existing NAND dts, which is
>> needed to comply with spec in which eMMC board ID is designated as 2.
>>
> 
> Can you elaborate what you mean by this? I don't see a change that is
> related.
> 
> Dinh
The board ID is transparent to Linux kernel. Will drop the board ID 
reference from commit.

  reply	other threads:[~2026-01-14  8:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-12  3:35 tzeyee.ng
2026-01-13 17:54 ` Dinh Nguyen
2026-01-14  8:19   ` Ng, Tze Yee [this message]
2026-01-13 17:57 ` Krzysztof Kozlowski

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=055d2e9d-ec73-4f9e-853c-68a4e64be653@altera.com \
    --to=tze.yee.ng@altera.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dinguyen@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@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

all inboxes | Powered by JetHome®