From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753086AbbLDOaz (ORCPT ); Fri, 4 Dec 2015 09:30:55 -0500 Received: from 212-186-180-163.dynamic.surfer.at ([212.186.180.163]:38589 "EHLO cgate.sperl.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752449AbbLDOax (ORCPT ); Fri, 4 Dec 2015 09:30:53 -0500 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\)) Subject: Re: [PATCH v5 08/10] spi: expose master transfer size limitation. From: Martin Sperl In-Reply-To: <20151201231233.GA1929@sirena.org.uk> Date: Fri, 4 Dec 2015 15:30:50 +0100 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?Q?Rafa=C5=82_Mi=C5=82ecki?= , Mika Westerberg , Gabor Juhos , =?utf-8?Q?Bean_Huo_=E9=9C=8D=E6=96=8C=E6=96=8C?= , Furquan Shaikh , linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org, linux-spi@vger.kernel.org Content-Transfer-Encoding: 7bit Message-Id: <5FC39638-EEE0-4CFA-B464-0B4743CB6AB6@sperl.org> References: <8c34c7790244489c2ce0072c72bd9bc7c4cdb965.1448988089.git.hramrach@gmail.com> <20151201231233.GA1929@sirena.org.uk> To: Mark Brown X-Mailer: Apple Mail (2.2104) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > On 02.12.2015, at 00:12, Mark Brown wrote: > > On Tue, Dec 01, 2015 at 04:51:06PM -0000, Michal Suchanek wrote: > >> +static inline size_t >> +spi_max_transfer_size(struct spi_device *spi) >> +{ >> + struct spi_master *master = spi->master; >> + if (!master->max_transfer_size) >> + return 0; >> + return master->max_transfer_size(spi); >> +} > > 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. Martin