From: Conor Dooley <conor@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: Fabio Estevam <festevam@gmail.com>,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
devicetree@vger.kernel.org, linux-spi@vger.kernel.org,
shawnguo@kernel.org, linux-arm-kernel@lists.infradead.org,
lukma@denx.de, Fabio Estevam <festevam@denx.de>
Subject: Re: [PATCH 1/3] dt-bindings: misc: lwn,bk4-spi: Add binding
Date: Wed, 23 Oct 2024 19:06:57 +0100 [thread overview]
Message-ID: <20241023-dares-december-d15da85e5799@spud> (raw)
In-Reply-To: <94889e08-07b3-473c-9f52-bdeb5d1fd822@sirena.org.uk>
[-- Attachment #1: Type: text/plain, Size: 568 bytes --]
On Wed, Oct 23, 2024 at 06:33:07PM +0100, Mark Brown wrote:
> On Wed, Oct 23, 2024 at 05:37:29PM +0100, Conor Dooley wrote:
> > On Wed, Oct 23, 2024 at 09:00:13AM -0300, Fabio Estevam wrote:
>
> > > + fsl,spi-cs-sck-delay: true
>
> > > + fsl,spi-sck-cs-delay: true
>
> > Why does this have fsl properties? I figure they're taken from the dts,
> > but spidev doesn't use them, right?
>
> These are controlling signal timing and implemented by the SPI
> controller rather than the device - they're the timing the device
> requires.
I see, thanks.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2024-10-23 19:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-23 12:00 [PATCH 1/3] dt-bindings: misc: lwn,bk4-spi: Add binding Fabio Estevam
2024-10-23 12:00 ` [PATCH 2/3] spi: spidev: Add an entry for lwn,bk4-spi Fabio Estevam
2024-10-23 12:00 ` [PATCH 3/3] ARM: dts: vf610-bk4: Use the more specific "lwn,bk4-spi" Fabio Estevam
2024-10-23 15:17 ` [PATCH 1/3] dt-bindings: misc: lwn,bk4-spi: Add binding Lukasz Majewski
2024-10-24 15:14 ` Rob Herring
2024-10-23 16:37 ` Conor Dooley
2024-10-23 17:33 ` Mark Brown
2024-10-23 18:06 ` Conor Dooley [this message]
2024-12-02 16:51 ` (subset) " Mark Brown
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=20241023-dares-december-d15da85e5799@spud \
--to=conor@kernel.org \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@denx.de \
--cc=festevam@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-spi@vger.kernel.org \
--cc=lukma@denx.de \
--cc=robh@kernel.org \
--cc=shawnguo@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