From: Mark Brown <broonie@kernel.org>
To: Martin Sperl <martin@sperl.org>
Cc: "Michal Suchanek" <hramrach@gmail.com>,
"Heiner Kallweit" <hkallweit1@gmail.com>,
"David Woodhouse" <dwmw2@infradead.org>,
"Brian Norris" <computersforpeace@gmail.com>,
"Han Xu" <han.xu@freescale.com>,
"Boris Brezillon" <boris.brezillon@free-electrons.com>,
"Javier Martinez Canillas" <javier@osg.samsung.com>,
"Stephen Warren" <swarren@nvidia.com>,
"Andrew F. Davis" <afd@ti.com>, "Marek Vasut" <marex@denx.de>,
"Rafał Miłecki" <zajec5@gmail.com>,
"Mika Westerberg" <mika.westerberg@linux.intel.com>,
"Gabor Juhos" <juhosg@openwrt.org>,
"Bean Huo 霍斌斌" <beanhuo@micron.com>,
"Furquan Shaikh" <furquan@google.com>,
linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-spi@vger.kernel.org
Subject: Re: [PATCH v5 08/10] spi: expose master transfer size limitation.
Date: Mon, 7 Dec 2015 20:18:04 +0000 [thread overview]
Message-ID: <20151207201804.GP5727@sirena.org.uk> (raw)
In-Reply-To: <5FC39638-EEE0-4CFA-B464-0B4743CB6AB6@sperl.org>
[-- Attachment #1: Type: text/plain, Size: 879 bytes --]
On Fri, Dec 04, 2015 at 03:30:50PM +0100, Martin Sperl wrote:
> > On 02.12.2015, at 00:12, Mark Brown <broonie@kernel.org> wrote:
> > Can we change this to return SIZE_MAX instead (ie, the maximum value for
> > a size_t)? That way callers don't need to worry if there is a limit, if
> > they want to handle it they can just unconditionally assume that a limit
> > will be provided.
> As I just came across: spi_master.max_dma_len, so I wonder how this
> value would differ from the proposed spi_master.max_transfer_size
> on specific HW?
> For all practical purposes I would assume both are identical.
Yeah, we should probably just remove the DMA specific one in time though
it may be useful for some devices with built in DMA engines if they're
oddly limited I'm not sure how practical their DMA would be if it
differed from the overall transfer length.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
prev parent reply other threads:[~2015-12-07 20:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1448988089.git.hramrach@gmail.com>
[not found] ` <8c34c7790244489c2ce0072c72bd9bc7c4cdb965.1448988089.git.hramrach@gmail.com>
2015-12-01 19:58 ` Mark Brown
2015-12-01 21:07 ` Heiner Kallweit
2015-12-01 21:31 ` Mark Brown
2015-12-02 9:55 ` Michal Suchanek
2015-12-01 23:12 ` Mark Brown
2015-12-02 9:38 ` Michal Suchanek
2015-12-04 14:30 ` Martin Sperl
2015-12-04 16:45 ` Michal Suchanek
2015-12-07 20:18 ` Mark Brown [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=20151207201804.GP5727@sirena.org.uk \
--to=broonie@kernel.org \
--cc=afd@ti.com \
--cc=beanhuo@micron.com \
--cc=boris.brezillon@free-electrons.com \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=furquan@google.com \
--cc=han.xu@freescale.com \
--cc=hkallweit1@gmail.com \
--cc=hramrach@gmail.com \
--cc=javier@osg.samsung.com \
--cc=juhosg@openwrt.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-spi@vger.kernel.org \
--cc=marex@denx.de \
--cc=martin@sperl.org \
--cc=mika.westerberg@linux.intel.com \
--cc=swarren@nvidia.com \
--cc=zajec5@gmail.com \
/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®