Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932866AbbLGUS6 (ORCPT ); Mon, 7 Dec 2015 15:18:58 -0500 Received: from mezzanine.sirena.org.uk ([106.187.55.193]:36554 "EHLO mezzanine.sirena.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932636AbbLGUS4 (ORCPT ); Mon, 7 Dec 2015 15:18:56 -0500 Date: Mon, 7 Dec 2015 20:18:04 +0000 From: Mark Brown To: Martin Sperl Cc: Michal Suchanek , Heiner Kallweit , David Woodhouse , Brian Norris , Han Xu , Boris Brezillon , Javier Martinez Canillas , Stephen Warren , "Andrew F. Davis" , Marek Vasut , =?utf-8?B?UmFmYcWCIE1pxYJlY2tp?= , Mika Westerberg , Gabor Juhos , Bean Huo =?utf-8?B?6ZyN5paM5paM?= , Furquan Shaikh , linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org, linux-spi@vger.kernel.org Message-ID: <20151207201804.GP5727@sirena.org.uk> References: <8c34c7790244489c2ce0072c72bd9bc7c4cdb965.1448988089.git.hramrach@gmail.com> <20151201231233.GA1929@sirena.org.uk> <5FC39638-EEE0-4CFA-B464-0B4743CB6AB6@sperl.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="QAdlk5ze2izLk3Ap" Content-Disposition: inline In-Reply-To: <5FC39638-EEE0-4CFA-B464-0B4743CB6AB6@sperl.org> X-Cookie: revolutionary, adj.: User-Agent: Mutt/1.5.24 (2015-08-30) X-SA-Exim-Connect-IP: 94.175.94.161 X-SA-Exim-Mail-From: broonie@sirena.org.uk Subject: Re: [PATCH v5 08/10] spi: expose master transfer size limitation. X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000) X-SA-Exim-Scanned: Yes (on mezzanine.sirena.org.uk) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1822 Lines: 46 --QAdlk5ze2izLk3Ap Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Dec 04, 2015 at 03:30:50PM +0100, Martin Sperl wrote: > > On 02.12.2015, at 00:12, Mark Brown 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=20 > 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. --QAdlk5ze2izLk3Ap Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJWZel7AAoJECTWi3JdVIfQjjQH/iy91T7A4JvYs/YwGF+FG0Uj B8qw/GNfCdVEH3FFCXPO6knkp5FVlHWGRhdnZzt2lWb2FfrZoN5OefDALP+g/PRK gFzHqoBMCE8lcuPMMRQsJuShGG94N1I+q4RuriA//0DXYXnJuyWms2k/yo0EWtlV 9zK5M6gg4tkTnMJBz1z5+2vzoD5xPK4VzHQSmoPk60E2SZ+987f+fhuCtqwu7t1e 589uV8Ko3XE12QK+ulBlbwQorItX6S6QtyNZC7k9UBnq35QVnROPaQ1VY2ElwIPy DM5sqtNCGFjVEXVqq1lkuQMkXcx1fqxPLXdzsp6pp+oGzlo05XdbKkomQk6e8GA= =lDk6 -----END PGP SIGNATURE----- --QAdlk5ze2izLk3Ap-- -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/