From: Monish Chunara <monish.chunara@oss.qualcomm.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Ulf Hansson <ulfh@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
linux-mmc@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Nitin Rawat <nitin.rawat@oss.qualcomm.com>,
Pradeep Pragallapati <pradeep.pragallapati@oss.qualcomm.com>,
Komal Bajaj <komal.bajaj@oss.qualcomm.com>
Subject: Re: [PATCH V1] dt-bindings: mmc: sdhci-msm: Document the Shikra compatible
Date: Fri, 8 May 2026 15:36:24 +0530 [thread overview]
Message-ID: <af21oCp0/OHl5lHi@hu-mchunara-hyd.qualcomm.com> (raw)
In-Reply-To: <20260506-arrogant-warthog-of-holiness-84ceea@quoll>
On Wed, May 06, 2026 at 10:23:07AM +0200, Krzysztof Kozlowski wrote:
> On Mon, May 04, 2026 at 12:43:34PM +0530, Monish Chunara wrote:
> > Add the MSM SDHCI compatible name to support both eMMC and SD card for
> > Shikra, which uses 'shikra' as the fallback SoC.
>
> How shikra can use shikra fallback?
>
> >
> > The SDHCI controller on Shikra is based on MSM SDHCI v5 IP. Hence,
> > document the compatible with "qcom,sdhci-msm-v5" as the fallback.
>
> And here you repeat or state something contradictory. So shikra or
> sdhci-msm-v5?
>
> This should be just one paragraph where you state the device and its
> compatibility with any other devices or interfaces.
Will update commit text in next series with better clarity on the change.
>
> Best regards,
> Krzysztof
>
prev parent reply other threads:[~2026-05-08 10:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-04 7:13 [PATCH V1] dt-bindings: mmc: sdhci-msm: Document the Shikra compatible Monish Chunara
2026-05-06 8:23 ` Krzysztof Kozlowski
2026-05-08 10:06 ` Monish Chunara [this message]
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=af21oCp0/OHl5lHi@hu-mchunara-hyd.qualcomm.com \
--to=monish.chunara@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=komal.bajaj@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=nitin.rawat@oss.qualcomm.com \
--cc=pradeep.pragallapati@oss.qualcomm.com \
--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