From: Dinh Nguyen <dinguyen@kernel.org>
To: "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 v5 0/2] Add eMMC support for Stratix 10 SoCDK
Date: Mon, 23 Feb 2026 12:33:43 -0600 [thread overview]
Message-ID: <27aec2f7-f4c1-495c-8a7c-5c0a0d09b848@kernel.org> (raw)
In-Reply-To: <907db5dd-414d-4333-8667-bfe9e69db576@altera.com>
On 2/23/26 00:45, Ng, Tze Yee wrote:
> On 26/1/2026 2:19 pm, Ng, Tze Yee wrote:
>> From: Ng Tze Yee <tzeyee.ng@altera.com>
>>
>> The first patch adds the device tree binding documentation for the new
>> board compatible string. The second patch introduces a new base device
>> tree include file (socfpga_stratix10_socdk.dtsi) containing common board
>> configurations, and the eMMC-specific device tree file
>> (socfpga_stratix10_socdk_emmc.dts) that includes the base dtsi along
>> with eMMC controller configuration.
>>
>> This follows a hierarchical structure:
>> - socfpga_stratix10.dtsi: SoC-level definitions
>> - socfpga_stratix10_socdk.dtsi: Board-level common configurations
>> - socfpga_stratix10_socdk_emmc.dts: eMMC daughter board specifics
>>
>> Changes in v5:
>> - Move Acked-by's above the Signed-off-by: and remove the empty
>> line between them.
>> - No code change
>>
>> Changes in v4:
>> - Included Acked-by from Rob Herring and Krzysztof Kozlowski in the second
>> patch commit message
>> - No code change
>>
>> Changes in v3:
>> - Refactor socfpga_stratix10_socdk.dts to use the new common dtsi file,
>> eliminating code duplication
>> - Move gmac2 and i2c2 nodes from socfpga_stratix10_socdk.dtsi to
>> socfpga_stratix10_socdk_emmc.dts as they are specific to the eMMC
>> daughter board variant
>> - Fix PHY address in socfpga_stratix10_socdk.dts from @0 to @4
>>
>> Changes in v2:
>> - Introduced socfpga_stratix10_socdk.dtsi for common board settings
>> - Updated socfpga_stratix10_socdk_emmc.dts to include the new dtsi
>> - Added fallback compatible string "altr,socfpga-stratix10-socdk" in
>> the binding documentation for broader compatibility
>>
>> Ng Tze Yee (2):
>> dt-bindings: altera: Add fallback compatible for Stratix 10 SoCDK eMMC
>> variant
>> arm64: dts: socfpga: stratix10: Add emmc support
>>
>> .../devicetree/bindings/arm/altera.yaml | 6 ++
>> arch/arm64/boot/dts/altera/Makefile | 1 +
>> .../dts/altera/socfpga_stratix10_socdk.dts | 67 +--------------
>> .../dts/altera/socfpga_stratix10_socdk.dtsi | 71 ++++++++++++++++
>> .../altera/socfpga_stratix10_socdk_emmc.dts | 81 +++++++++++++++++++
>> 5 files changed, 161 insertions(+), 65 deletions(-)
>> create mode 100644 arch/arm64/boot/dts/altera/socfpga_stratix10_socdk.dtsi
>> create mode 100644 arch/arm64/boot/dts/altera/socfpga_stratix10_socdk_emmc.dts
>>
>
> Hi maintainers,
>
> I would like to gently ping on this patch series that was submitted. The
> series has received Acked-by from Rob Herring and Krzysztof Kozlowski
> for the dt-bindings patch in v4, and all requested changes have been
> addressed in v5.
>
> Patch series link:
> https://lore.kernel.org/all/cover.1769407657.git.tzeyee.ng@altera.com/
>
> Could you please let me know if there are any concerns or additional
> changes needed for this series to be merged?
>
> Thanks for your time and consideration.
>
This series look good to me, but can you rebase it to v7.0-rc1? I'm
getting a conflict.
Thanks,
Dinh
next prev parent reply other threads:[~2026-02-23 18:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-26 6:19 tzeyee.ng
2026-01-26 6:19 ` [PATCH v5 1/2] dt-bindings: altera: Add fallback compatible for Stratix 10 SoCDK eMMC variant tzeyee.ng
2026-01-26 6:19 ` [PATCH v5 2/2] arm64: dts: socfpga: stratix10: Add emmc support tzeyee.ng
2026-02-23 6:45 ` [PATCH v5 0/2] Add eMMC support for Stratix 10 SoCDK Ng, Tze Yee
2026-02-23 18:33 ` Dinh Nguyen [this message]
2026-02-24 6:04 ` Ng, Tze Yee
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=27aec2f7-f4c1-495c-8a7c-5c0a0d09b848@kernel.org \
--to=dinguyen@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=tze.yee.ng@altera.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
Powered by JetHome