Devicetree
 help / color / mirror / Atom feed
From: Monish Chunara <monish.chunara@oss.qualcomm.com>
To: sashiko-reviews@lists.linux.dev
Cc: robh@kernel.org, conor+dt@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH V2 1/3] arm64: dts: qcom: monaco: Move eMMC CQE support from SoC to board DT
Date: Wed, 1 Jul 2026 13:59:34 +0530	[thread overview]
Message-ID: <akTP7jU94kwdFL/O@hu-mchunara-hyd.qualcomm.com> (raw)
In-Reply-To: <20260616131405.448371F000E9@smtp.kernel.org>

On Tue, Jun 16, 2026 at 01:14:04PM +0000, sashiko-bot@kernel.org wrote:
> Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
> - [High] Incomplete genericization of `sdhc_1` leaves conflicting eMMC-specific properties in the SoC DT, breaking SD card compatibility.
> - [Medium] Removing the `supports-cqe` property from the SoC-level `monaco.dtsi` without explicitly adding it back to all eMMC-based boards causes a silent performance regression by disabling Command Queue Engine (CQE) support.
> --
> 
> commit 05fd7920ab031fea94cd493a589a30892353cf08
> Author: Monish Chunara <monish.chunara@oss.qualcomm.com>
> 
> arm64: dts: qcom: monaco: Move eMMC CQE support from SoC to board DT
> 
> This commit removes the supports-cqe property from the generic Monaco SoC
> device tree and moves it to the qcs8300-ride board device tree. The stated
> goal is to allow SD card compatibility in the base SoC definition, since the
> Command Queue Engine conflicts with SD card operation.
> 
> > diff --git a/arch/arm64/boot/dts/qcom/monaco.dtsi b/arch/arm64/boot/dts/qcom/monaco.dtsi
> > index 7b1d57460f1e6..e5f316897706b 100644
> > --- a/arch/arm64/boot/dts/qcom/monaco.dtsi
> > +++ b/arch/arm64/boot/dts/qcom/monaco.dtsi
> > @@ -4828,7 +4828,6 @@ &mc_virt SLAVE_EBI1 QCOM_ICC_TAG_ALWAYS>,
> >  			qcom,dll-config = <0x000f64ee>;
> >  			qcom,ddr-config = <0x80040868>;
> >  			bus-width = <8>;
> > -			supports-cqe;
> 
> [Severity: Medium]
> Removing supports-cqe from the SoC DT without adding it back to all
> eMMC-based boards appears to cause a performance regression by disabling the
> Command Queue Engine for those boards.
> 
> For example, arch/arm64/boot/dts/qcom/monaco-monza-som.dtsi and
> arch/arm64/boot/dts/qcom/monaco-evk.dts both configure sdhc_1 as an eMMC
> device (using no-sd and non-removable). Since they rely on the SoC DT for
> the supports-cqe property, won't omitting it from this patch silently degrade
> their performance?
> 

Update for monaco-monza-som in v3 series - https://lore.kernel.org/all/20260701081715.2580329-1-monish.chunara@oss.qualcomm.com/

For monaco-evk, it is handled via the overlay monaco-evk-emmc.dtso added as part
of the same patchset.

> [Severity: High]
> The commit message states the goal is to ensure the SoC definition remains
> generic for SD card compatibility by removing supports-cqe. However, does
> leaving the other eMMC-specific properties in the SoC DT defeat this purpose?
> 
> Properties like bus-width = <8>, mmc-hs400-1_8v, mmc-hs400-enhanced-strobe,
> qcom,dll-config, and qcom,ddr-config remain in the base monaco.dtsi. Since
> device tree overlays do not automatically delete base boolean properties or
> override tuning parameters unless explicitly redefined, won't these
> incorrectly inherit to SD card configurations and cause the MMC core to
> misconfigure the interface?
> 
> Should these properties be moved to the eMMC-specific board files as well?
> 

These speed modes are handled in the eMMC driver and won't affect the SD card
functionality. bus-width is overridden in the platform file to match the SD card
requirements.

> >  			dma-coherent;
> >  
> >  			mmc-ddr-1_8v;
> > diff --git a/arch/arm64/boot/dts/qcom/qcs8300-ride.dts b/arch/arm64/boot/dts/qcom/qcs8300-ride.dts
> > index e9a8553a8d821..3090eba0317ac 100644
> > --- a/arch/arm64/boot/dts/qcom/qcs8300-ride.dts
> > +++ b/arch/arm64/boot/dts/qcom/qcs8300-ride.dts
> > @@ -719,6 +719,7 @@ &sdhc_1 {
> >  	vmmc-supply = <&vreg_l8a>;
> >  	vqmmc-supply = <&vreg_s4a>;
> >  
> > +	supports-cqe;
> >  	non-removable;
> >  	no-sd;
> >  	no-sdio;
> 
> -- 
> Sashiko AI review · https://sashiko.dev/#/patchset/20260616130347.3096034-1-monish.chunara@oss.qualcomm.com?part=1

  reply	other threads:[~2026-07-01  8:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-16 13:03 [PATCH V2 0/3] arm64: dts: qcom: Monaco: Enable SDHCI storage support Monish Chunara
2026-06-16 13:03 ` [PATCH V2 1/3] arm64: dts: qcom: monaco: Move eMMC CQE support from SoC to board DT Monish Chunara
2026-06-16 13:14   ` sashiko-bot
2026-07-01  8:29     ` Monish Chunara [this message]
2026-06-17 10:17   ` Konrad Dybcio
2026-07-01  8:23     ` Monish Chunara
2026-06-16 13:03 ` [PATCH V2 2/3] arm64: dts: qcom: monaco-evk: Enable SDHCI for SD Card via overlay Monish Chunara
2026-06-16 13:15   ` sashiko-bot
2026-06-16 13:03 ` [PATCH V2 3/3] arm64: dts: qcom: monaco-evk: Add SDHCI support for eMMC " Monish Chunara
2026-06-16 13:13   ` sashiko-bot

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=akTP7jU94kwdFL/O@hu-mchunara-hyd.qualcomm.com \
    --to=monish.chunara@oss.qualcomm.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    /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