From: Krzysztof Kozlowski <krzk@kernel.org>
To: Jyothi Kumar Seerapu <jyothi.seerapu@oss.qualcomm.com>
Cc: Mark Brown <broonie@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
linux-arm-msm@vger.kernel.org, linux-spi@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: spi: qcom,spi-geni-qcom: Document QSPI support
Date: Mon, 2 Nov 2026 12:29:10 +0100 [thread overview]
Message-ID: <20261102-crafty-beautiful-lizard-36db2b@quoll> (raw)
In-Reply-To: <53640a9c-395f-4faf-bbac-20c47013cec4@oss.qualcomm.com>
On Fri, Oct 30, 2026 at 07:28:57PM +0530, Jyothi Kumar Seerapu wrote:
>
>
> On 10/30/2026 7:06 PM, Krzysztof Kozlowski wrote:
> > On 30/10/2026 14:30, Jyothi Kumar Seerapu wrote:
> > > Add the "qcom,geni-qspi" compatible to identify GENI Serial Engine
> > > instances configured for QSPI operation.
> > >
> > > The compatible also allows the driver to select the appropriate protocol
> > > firmware when the Serial Engine is unconfigured (GENI_SE_INVALID_PROTO),
> > > distinguishing between SPI and QSPI firmware.
> > >
> > > Signed-off-by: Jyothi Kumar Seerapu <jyothi.seerapu@oss.qualcomm.com>
> >
> > Where is any user of this? You speak about driver, but there is no driver.
> >
> Thanks for the review. This patch only adds the QSPI binding change. The
Please avoid stating obvious. I can read the patch.
> corresponding driver changes to add QSPI support will be submitted in an
> upcoming separate patch.
So no point for this submission. Please read submitting patches
documents (both).
Best regards,
Krzysztof
prev parent reply other threads:[~2026-11-02 11:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-30 13:30 Jyothi Kumar Seerapu
2026-10-30 13:36 ` Krzysztof Kozlowski
2026-10-30 13:58 ` Jyothi Kumar Seerapu
2026-11-02 11:29 ` Krzysztof Kozlowski [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=20261102-crafty-beautiful-lizard-36db2b@quoll \
--to=krzk@kernel.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jyothi.seerapu@oss.qualcomm.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--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®