From: Mark Brown <broonie@kernel.org>
To: David Laight <David.Laight@ACULAB.COM>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>,
'Eddie James' <eajames@linux.ibm.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-spi@vger.kernel.org" <linux-spi@vger.kernel.org>,
"robh+dt@kernel.org" <robh+dt@kernel.org>
Subject: Re: [PATCH 1/2] spi: fsi: Reduce max transfer size to 8 bytes
Date: Tue, 20 Jul 2021 14:13:03 +0100 [thread overview]
Message-ID: <20210720131303.GB5042@sirena.org.uk> (raw)
In-Reply-To: <0a637d7704df4303abe783215080578d@AcuMS.aculab.com>
[-- Attachment #1: Type: text/plain, Size: 748 bytes --]
On Tue, Jul 20, 2021 at 01:04:38PM +0000, David Laight wrote:
> Having said that, you might want a loop in the driver so that
> application requests for longer transfers are implemented
> with multiple hardware requests.
No, that's something that should be and indeed is done in the core -
this isn't the only hardware out there with some kind of restriction on
length.
> I do also wonder why there is support in the main kernel sources
> for hardware that doesn't actually exist.
We encourage vendors to get support for their devices upstream prior to
hardware availability so that users are able to run upstream when they
get access to hardware, this means users aren't forced to run out of
tree code needlessly and greatly eases deployment.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-07-20 13:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-16 13:39 [PATCH 0/2] spi: fsi: Reduce max transfer size to 8 bytes Eddie James
2021-07-16 13:39 ` [PATCH 1/2] " Eddie James
2021-07-16 17:19 ` Mark Brown
2021-07-16 18:34 ` Eddie James
2021-07-19 15:20 ` Mark Brown
2021-07-19 15:46 ` Eddie James
2021-07-20 13:04 ` David Laight
2021-07-20 13:13 ` Mark Brown [this message]
2021-07-20 17:32 ` David Laight
2021-07-16 13:39 ` [PATCH 2/2] dt-bindings: fsi: Remove ibm, fsi2spi-restricted compatible Eddie James
2021-07-19 15:54 ` [PATCH 2/2] dt-bindings: fsi: Remove ibm,fsi2spi-restricted compatible Mark Brown
2021-07-17 13:46 ` [PATCH 0/2] spi: fsi: Reduce max transfer size to 8 bytes David Laight
2021-07-19 15:57 ` Eddie James
2021-07-19 18:00 ` 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=20210720131303.GB5042@sirena.org.uk \
--to=broonie@kernel.org \
--cc=David.Laight@ACULAB.COM \
--cc=devicetree@vger.kernel.org \
--cc=eajames@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=openbmc@lists.ozlabs.org \
--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;
as well as URLs for NNTP newsgroup(s).