From: Mark Brown <broonie@kernel.org>
To: Praveen Talari <praveen.talari@oss.qualcomm.com>
Cc: konrad.dybcio@oss.qualcomm.com, 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>,
chandana.chiluveru@oss.qualcomm.com,
Krzysztof Kozlowski <krzk@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 1/2] dt-bindings: spi: qcom-geni: Document device-gpios property
Date: Thu, 6 Aug 2026 19:34:35 +0100 [thread overview]
Message-ID: <65e5ead6-6159-4660-a699-db46fb4caf17@sirena.org.uk> (raw)
In-Reply-To: <3594bbdd-e457-4a88-9e37-7acf0f3d87d2@oss.qualcomm.com>
[-- Attachment #1: Type: text/plain, Size: 375 bytes --]
On Thu, Aug 06, 2026 at 11:47:46PM +0530, Praveen Talari wrote:
> On 06-08-2026 23:05, Mark Brown wrote:
> > This seems a lot like the ready-gpios property we have for some other
> > drivers?
> Yes, you're right. The intention was the same when I added this property.
> Would you prefer that I use the ready-gpios property instead?
Yes, we should have a consistent name.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2026-08-06 18:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-06 10:13 [PATCH 0/2] spi: qcom-geni: Use GPIO to notify master of SPI target activity Praveen Talari
2026-08-06 10:13 ` [PATCH 1/2] dt-bindings: spi: qcom-geni: Document device-gpios property Praveen Talari
2026-08-06 16:47 ` Mark Brown
2026-08-06 16:54 ` Praveen Talari
2026-08-06 17:35 ` Mark Brown
2026-08-06 18:17 ` Praveen Talari
2026-08-06 18:34 ` Mark Brown [this message]
2026-08-06 18:15 ` Mukesh Savaliya
2026-08-06 18:23 ` Praveen Talari
2026-08-06 10:13 ` [PATCH 2/2] spi: qcom-geni: Use GPIO to notify master of SPI target activity Praveen Talari
2026-08-06 18:24 ` Mukesh Savaliya
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=65e5ead6-6159-4660-a699-db46fb4caf17@sirena.org.uk \
--to=broonie@kernel.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=chandana.chiluveru@oss.qualcomm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=praveen.talari@oss.qualcomm.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®