Linux-mediatek Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
To: Macpaul Lin <macpaul.lin@mediatek.com>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Matthias Brugger <matthias.bgg@gmail.com>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will@kernel.org>, Sean Wang <sean.wang@mediatek.com>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-mediatek@lists.infradead.org
Cc: Bear Wang <bear.wang@mediatek.com>,
	Pablo Sun <pablo.sun@mediatek.com>,
	Ramax Lo <ramax.lo@mediatek.com>, Macpaul Lin <macpaul@gmail.com>,
	MediaTek Chromebook Upstream
	<Project_Global_Chrome_Upstream_Group@mediatek.com>
Subject: Re: [PATCH v3 3/4] arm64: dts: mediatek: add device-tree for Genio 1200 EVK UFS board
Date: Tue, 29 Jul 2025 12:12:27 +0200	[thread overview]
Message-ID: <66551820-45d2-433c-b837-3a0ace37c528@collabora.com> (raw)
In-Reply-To: <20250729093506.273337-3-macpaul.lin@mediatek.com>

Il 29/07/25 11:35, Macpaul Lin ha scritto:
> Add a basic device-tree (mt8395-genio-1200-evk-ufs.dts) in order to be able
> to use UFS storage as the main storage on Genio 1200 EVK board.
> 
> This board is the origin Genio 1200 EVK already mounted two main storages,
> one is eMMC, and the other is UFS. The system automatically prioritizes
> between eMMC and UFS via BROM detection, so user could not use both storage
> types simultaneously. As a result, mt8395-evk-ufs must be treated as a
> separate board.
> 
> It use mt8395-genio-common.dtsi file to use common definitions.
> 
> Signed-off-by: Macpaul Lin <macpaul.lin@mediatek.com>

Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>




  reply	other threads:[~2025-07-29 10:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-29  9:34 [PATCH v3 1/4] dt-bindings: arm64: mediatek: add mt8395-evk-ufs board Macpaul Lin
2025-07-29  9:34 ` [PATCH v3 2/4] arm64: dts: mediatek: mt8395-genio-1200-evk: Move common parts to dtsi Macpaul Lin
2025-07-29 10:12   ` AngeloGioacchino Del Regno
2025-07-29  9:35 ` [PATCH v3 3/4] arm64: dts: mediatek: add device-tree for Genio 1200 EVK UFS board Macpaul Lin
2025-07-29 10:12   ` AngeloGioacchino Del Regno [this message]
2025-07-29  9:35 ` [PATCH v3 4/4] arm64: defconfig: Enable UFS support for MediaTek " Macpaul Lin
2025-07-29 10:12   ` AngeloGioacchino Del Regno
2025-07-29 10:12 ` [PATCH v3 1/4] dt-bindings: arm64: mediatek: add mt8395-evk-ufs board AngeloGioacchino Del Regno
2025-07-29 23:40 ` Rob Herring (Arm)

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=66551820-45d2-433c-b837-3a0ace37c528@collabora.com \
    --to=angelogioacchino.delregno@collabora.com \
    --cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
    --cc=bear.wang@mediatek.com \
    --cc=catalin.marinas@arm.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=macpaul.lin@mediatek.com \
    --cc=macpaul@gmail.com \
    --cc=matthias.bgg@gmail.com \
    --cc=pablo.sun@mediatek.com \
    --cc=ramax.lo@mediatek.com \
    --cc=robh@kernel.org \
    --cc=sean.wang@mediatek.com \
    --cc=will@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