Devicetree
 help / color / mirror / Atom feed
From: "Kathpalia, Tanmay" <tanmay.kathpalia@altera.com>
To: Michael Tretter <m.tretter@pengutronix.de>
Cc: linux-mmc@vger.kernel.org, ulfh@kernel.org,
	adrian.hunter@intel.com, krzk+dt@kernel.org, robh@kernel.org,
	conor+dt@kernel.org, dinguyen@kernel.org, p.zabel@pengutronix.de,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 2/8] arm64: dts: agilex5: add SD/eMMC host controller
Date: Wed, 2 Sep 2026 00:02:20 +0530	[thread overview]
Message-ID: <cebd7511-784e-40c8-a893-a7de4a56a147@altera.com> (raw)
In-Reply-To: <apaQX_bHpEcP4Tp5@pengutronix.de>

Hi Michael,

Thanks for your feedback.

>>   			};
>>   		};
>>   
>> +		/*
>> +		 * Shared SD/eMMC controller node. On the SOCDK OOBE daughter-card
>> +		 * this is used for SD card operation; on the SOCDK eMMC daughter-card
>> +		 * it is configured for eMMC.
>> +		 */
> The documentation about the daughter-card configuration belongs into the
> device trees of the daughter-cards and not in the SoC device tree.

Agreed. The comment is dropped from the SoC DTSI in v7.

>> +		emmc: mmc@10808000 {
> The HPS register address map uses the name "sdmmc" for this group. Maybe
> that's a better label than emmc, if the controller may be used for eMMC
> or SD card.

Agreed. v7 renames the label to sdmmc.

>> +			compatible = "altr,agilex5-sd6hc", "cdns,sd6hc";
>> +			reg = <0x10808000 0x1000>;
>> +			/*
>> +			 * "ciu" (SDMCLK) is listed first so it is selected as the
>> +			 * primary clock by the SDHCI platform layer; the SD6HC PHY
>> +			 * timing calculations are derived from this clock rate.
>> +			 */
> This is surprising to me and I can't find where the first clock is
> selected as primary clock by the SDHCI platform layer.
>
> Could you point me to the code that relies on the order of clocks in the
> device tree?

The comment was wrong: it is not the SDHCI platform layer. v6 did
   clk = devm_clk_get_enabled(dev, NULL);
in sdhci_cdns_probe().
SD6HC now requests the clocks by
name:
   clk = devm_clk_get_enabled(dev, "ciu");
   biu_clk = devm_clk_get_enabled(dev, "biu");
SD4HC still uses the unnamed lookup because its binding has no
clock-names. The DTS clock-order comment is also removed.

>
>
> -&gpio0 {
> +&emmc {
> +	bus-width = <4>;
> +	cap-sd-highspeed;
> +	disable-wp;
> +	max-frequency = <200000000>;
> +	no-mmc;
> +	sd-uhs-sdr104;
> +	vmmc-supply = <&vmmc_reg>;
> +	vqmmc-supply = <&vqmmc_io_reg>;
> +
>   	status = "okay";
> I'd have split the addition of the controller to the SoC device tree and
> the enabling for the board in two separate patches, but that's probably
> just personal taste.
>

Done in v7: SoC node in one patch, SOCDK SD enablement in the next.

Thanks again for the review, it improved the series.

Tanmay

  reply	other threads:[~2026-09-01 18:32 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-29 18:42 [PATCH v6 0/8] mmc: sdhci-cadence: add SD6HC support and Agilex5 enablement Tanmay Kathpalia
2026-08-29 18:42 ` [PATCH v6 1/8] dt-bindings: mmc: add Cadence SD6HC binding Tanmay Kathpalia
2026-08-29 18:42 ` [PATCH v6 2/8] arm64: dts: agilex5: add SD/eMMC host controller Tanmay Kathpalia
2026-08-29 18:51   ` sashiko-bot
2026-09-01  8:44   ` Michael Tretter
2026-09-01 18:32     ` Kathpalia, Tanmay [this message]
2026-08-29 18:42 ` [PATCH v6 3/8] dt-bindings: arm: altera: add Agilex5 SOCDK eMMC board variant Tanmay Kathpalia
2026-08-29 18:42 ` [PATCH v6 4/8] arm64: dts: agilex5: add SOCDK eMMC daughter board Tanmay Kathpalia
2026-08-29 18:42 ` [PATCH v6 5/8] mmc: sdhci-cadence: rename SD4HC symbols for SD6HC groundwork Tanmay Kathpalia
2026-08-29 18:51   ` sashiko-bot
2026-08-29 18:42 ` [PATCH v6 6/8] mmc: sdhci-cadence: refactor driver structure for V6 controller support Tanmay Kathpalia
2026-08-29 18:54   ` sashiko-bot
2026-08-29 18:42 ` [PATCH v6 7/8] mmc: sdhci-cadence: add Cadence SD6HC support Tanmay Kathpalia
2026-08-29 18:59   ` sashiko-bot
2026-08-29 18:42 ` [PATCH v6 8/8] mmc: sdhci-cadence: add Altera Agilex5 " Tanmay Kathpalia

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=cebd7511-784e-40c8-a893-a7de4a56a147@altera.com \
    --to=tanmay.kathpalia@altera.com \
    --cc=adrian.hunter@intel.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=linux-mmc@vger.kernel.org \
    --cc=m.tretter@pengutronix.de \
    --cc=p.zabel@pengutronix.de \
    --cc=robh@kernel.org \
    --cc=ulfh@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