From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Sayali Lokhande <quic_sayalil@quicinc.com>,
andersson@kernel.org, konradybcio@kernel.org, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mmc-owner@vger.kernel.org
Subject: Re: [PATCH 1/1] arm64: dts: msm: Add eMMC support for qcs8300
Date: Fri, 13 Jun 2025 21:40:02 +0200 [thread overview]
Message-ID: <a033f565-96b0-48ba-b12e-8deee4691f72@oss.qualcomm.com> (raw)
In-Reply-To: <20250612092146.5170-2-quic_sayalil@quicinc.com>
On 6/12/25 11:21 AM, Sayali Lokhande wrote:
> Add eMMC support for qcs8300 board.
>
> Signed-off-by: Sayali Lokhande <quic_sayalil@quicinc.com>
> ---
[...]
> + sdhc_1: mmc@87C4000 {
> + compatible = "qcom,sdhci-msm-v5";
This needs a SoC-specific compatible and a corresponding dt-bindings
change (see other soc dtsi files, e.g. x1e80100.dtsi)
> + status = "disabled";
> +
> + reg = <0x0 0x87C4000 0x0 0x1000>,
> + <0x0 0x87C5000 0x0 0x1000>;
Please align the '<'s across this change
> + reg-names = "hc", "cqhci";
> +
> + interrupts = <GIC_SPI 383 IRQ_TYPE_LEVEL_HIGH>,
> + <GIC_SPI 521 IRQ_TYPE_LEVEL_HIGH>;
> + interrupt-names = "hc_irq", "pwr_irq";
> +
> + clocks = <&gcc GCC_SDCC1_AHB_CLK>,
> + <&gcc GCC_SDCC1_APPS_CLK>,
> + <&rpmhcc RPMH_CXO_CLK>;
> + clock-names = "iface", "core", "xo";
> + interconnects = <&aggre1_noc MASTER_SDC 0 &mc_virt SLAVE_EBI1 0>,
0 -> QCOM_ICC_TAG_ALWAYS on this path
> + <&gem_noc MASTER_APPSS_PROC 0 &config_noc SLAVE_SDC1 0>;
0 -> QCOM_ICC_TAG_ACTIVE_ONLY on this path
> + interconnect-names = "sdhc-ddr","cpu-sdhc";
one per line, please, also change-wide
Konrad
next prev parent reply other threads:[~2025-06-13 19:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-12 9:21 [PATCH 0/1] " Sayali Lokhande
2025-06-12 9:21 ` [PATCH 1/1] arm64: dts: msm: " Sayali Lokhande
2025-06-12 10:02 ` Krzysztof Kozlowski
2025-06-13 19:40 ` Konrad Dybcio [this message]
2025-06-12 20:12 ` [PATCH 0/1] " 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=a033f565-96b0-48ba-b12e-8deee4691f72@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc-owner@vger.kernel.org \
--cc=quic_sayalil@quicinc.com \
--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®