From: Konrad Dybcio <konrad.dybcio@linaro.org>
To: Hariharan K <quic_harihk@quicinc.com>,
agross@kernel.org, andersson@kernel.org, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: quic_srichara@quicinc.com, quic_sjaganat@quicinc.com,
quic_kathirav@quicinc.com, quic_arajkuma@quicinc.com,
quic_anusha@quicinc.com
Subject: Re: [PATCH 2/2] arm64: dts: qcom: ipq5018: add support for the RDP415 variant
Date: Thu, 20 Jul 2023 10:16:40 +0200 [thread overview]
Message-ID: <6f26ab9d-cf92-e918-866c-daa68096ee08@linaro.org> (raw)
In-Reply-To: <20230720074846.20350-3-quic_harihk@quicinc.com>
On 20.07.2023 09:48, Hariharan K wrote:
> Add the initial device tree support for the Reference Design
> Platform(RDP) 415 based on IPQ5018 family of SoC. This patch
> carries the support for Console UART and eMMC.
>
> Signed-off-by: Hariharan K <quic_harihk@quicinc.com>
> ---
[...]
> +
> +&sdhc_1 {
> + pinctrl-0 = <&sdc_default_state>;
> + pinctrl-names = "default";
> + mmc-ddr-1_8v;
> + mmc-hs200-1_8v;
> + max-frequency = <192000000>;
> + bus-width = <4>;
> + status = "okay";
Since some (but presumably not all) SKUs have SDHCI, you can define
the plumbing for it in the common DTSI but only enable it on ones
that do (or disable on those that don't)
Konrad
next prev parent reply other threads:[~2023-07-20 8:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-20 7:48 [PATCH 0/2] Add initial support for RDP415 of IPQ5018 family Hariharan K
2023-07-20 7:48 ` [PATCH 1/2] dt-bindings: arm: qcom: Document MP03.3-C2 board based on " Hariharan K
2023-07-20 7:48 ` [PATCH 2/2] arm64: dts: qcom: ipq5018: add support for the RDP415 variant Hariharan K
2023-07-20 8:16 ` Konrad Dybcio [this message]
2023-07-20 11:16 ` Hariharan K
2023-07-20 8:56 ` Krzysztof Kozlowski
2023-07-20 11:20 ` Hariharan K
2023-07-20 8:05 ` [PATCH 0/2] Add initial support for RDP415 of IPQ5018 family Konrad Dybcio
2023-07-20 11:21 ` Hariharan K
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=6f26ab9d-cf92-e918-866c-daa68096ee08@linaro.org \
--to=konrad.dybcio@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_anusha@quicinc.com \
--cc=quic_arajkuma@quicinc.com \
--cc=quic_harihk@quicinc.com \
--cc=quic_kathirav@quicinc.com \
--cc=quic_sjaganat@quicinc.com \
--cc=quic_srichara@quicinc.com \
--cc=robh+dt@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®