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
Subject: Re: [PATCH V2 1/2] arm64: dts: qcom: Add eMMC support for qcs8300
Date: Mon, 23 Jun 2025 16:09:30 +0200 [thread overview]
Message-ID: <d3309e0d-d751-44c4-845c-e05eec4ac75d@oss.qualcomm.com> (raw)
In-Reply-To: <20250619070224.23428-2-quic_sayalil@quicinc.com>
On 6/19/25 9:02 AM, Sayali Lokhande wrote:
> Add eMMC support for qcs8300 board.
>
> Signed-off-by: Sayali Lokhande <quic_sayalil@quicinc.com>
> ---
It's customary to split board and SoC changes into separate commits
[...]
> + sdhc_1: mmc@87C4000 {
Please use lowercase hex across DT, in all places
> + compatible = "qcom,qcs8300-sdhci", "qcom,sdhci-msm-v5";
> + reg = <0x0 0x87C4000 0x0 0x1000>,
To make it easier to compare by eye, we tend to pad the address
values to 8 hex digits with leading zeroes, please do so as well
> + <0x0 0x87C5000 0x0 0x1000>;
> + 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";
> +
> + resets = <&gcc GCC_SDCC1_BCR>;
> +
> + power-domains = <&rpmhpd RPMHPD_CX>;
> + operating-points-v2 = <&sdhc1_opp_table>;
> + iommus = <&apps_smmu 0x0 0x0>;
In case anyone's wondering, this is actually the correct value
> + interconnects = <&aggre1_noc MASTER_SDC QCOM_ICC_TAG_ALWAYS
> + &mc_virt SLAVE_EBI1 QCOM_ICC_TAG_ALWAYS>,
> + <&gem_noc MASTER_APPSS_PROC QCOM_ICC_TAG_ACTIVE_ONLY
> + &config_noc SLAVE_SDCC_1 QCOM_ICC_TAG_ACTIVE_ONLY>;
> + interconnect-names = "sdhc-ddr",
> + "cpu-sdhc";
[...]
> + sdc1_state_on: sdc1-on-state {
> + clk-pins {
> + pins = "sdc1_clk";
> + bias-disable;
> + drive-strength = <16>;
Please move bias properties under drive-strength for consistency
> + };
> +
> + cmd-pins {
> + pins = "sdc1_cmd";
> + bias-pull-up;
> + drive-strength = <10>;
> + };
> +
> + data-pins {
> + pins = "sdc1_data";
> + bias-pull-up;
> + drive-strength = <10>;
> + };
> +
> + rclk-pins {
> + pins = "sdc1_rclk";
> + bias-pull-down;
> + };
> + };
> +
> + sdc1_state_off: sdc1-off-state {
> + clk-pins {
> + pins = "sdc1_clk";
> + bias-bus-hold;
Is bus-hold what we want here? Other platforms do a pull-up/down
or disable bias altogether
Konrad
next prev parent reply other threads:[~2025-06-23 14:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-19 7:02 [PATCH V2 0/2] " Sayali Lokhande
2025-06-19 7:02 ` [PATCH V2 1/2] arm64: dts: qcom: " Sayali Lokhande
2025-06-19 23:19 ` kernel test robot
2025-06-23 14:09 ` Konrad Dybcio [this message]
2025-07-02 8:55 ` Sayali Lokhande
2025-06-19 7:02 ` [PATCH V2 2/2] dt-bindings: mmc: Add sdhci compatible " Sayali Lokhande
2025-06-27 19:40 ` Rob Herring
2025-06-27 19: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=d3309e0d-d751-44c4-845c-e05eec4ac75d@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=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®