Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp1320952imu; Fri, 25 Jan 2019 23:53:05 -0800 (PST) X-Google-Smtp-Source: ALg8bN53tj8jaQW2HPun13uP4tqrSGckuMKl2GFv3jBP7o7HhjahkXQTmTsAg5LBYsI2OMcWlTU0 X-Received: by 2002:a17:902:887:: with SMTP id 7mr14139244pll.164.1548489184989; Fri, 25 Jan 2019 23:53:04 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1548489184; cv=none; d=google.com; s=arc-20160816; b=EtbLvnypJr88mX68sCwDrMjqzqhhfwLP7Q9xVskIWFerTc8xQiNZvwJw5XSIBfnjHO 5guDOW2ymqkmAhB033V+0vkaUM0XNIKnhq3YD1CN02EDdv/kxrK0HlZKE2tM1jbDcU0o R4HcK//Vf+5wbtyoc09cOQVe+8S7m9VpaKTEcEiNw2+eTgt2V8/Bce6LCXr6KlLuSKbL GI/aOOYwN/NOeN6LmUyd8DJfUs1+TtccxJsZMfu9zXjLae4vmuF+7qWDy2Ir41P7j0Np 4iCFy3ffTDw67op1aapRikSqRMZU8MKH83qeXcvIVvfaRRwMuTOtc57qm1hK++Jx+NMZ z98g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:dkim-signature; bh=d0NXBQe8aajlr098aMi4Ef9fbquF6GsoPb1AHlzJR8s=; b=iBB69rzmo8CPChFr9E3mrPo0+nNzaItZzvsGw77D4t9t+KELCtoygQezb3cnInLIIf 1MiqzMXR0ECUzBmDO47tPaYC7W0KbPsVQnVTgjZuZElUjTO4XDnQjJ83pTTlBpC5mz/P seVJN9kxBItON6XgwqlcndHod7z5duyFnLo0loVtKY4I142DnctYFTuMhVVLmLevSWUk 0ZeHcGtnWwPhdxAMJzxipCXI3kWt1jvJ59OBeAZL5dwhEqh4dkbfWes/+EuaGELthPDN +fIpDBcWXpeBWYb0nwB84wwybGCm2PPGyVWzvj8nIHVqUiV3B+cEpCTVs31Hn9Jkg4r6 8a3A== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@norrbonn-se.20150623.gappssmtp.com header.s=20150623 header.b=W14fTDMs; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id q8si26450975pgc.580.2019.01.25.23.52.37; Fri, 25 Jan 2019 23:53:04 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@norrbonn-se.20150623.gappssmtp.com header.s=20150623 header.b=W14fTDMs; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726335AbfAZHwd (ORCPT + 99 others); Sat, 26 Jan 2019 02:52:33 -0500 Received: from mail-lj1-f195.google.com ([209.85.208.195]:37818 "EHLO mail-lj1-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726143AbfAZHwd (ORCPT ); Sat, 26 Jan 2019 02:52:33 -0500 Received: by mail-lj1-f195.google.com with SMTP id t18-v6so10253695ljd.4 for ; Fri, 25 Jan 2019 23:52:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=norrbonn-se.20150623.gappssmtp.com; s=20150623; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=d0NXBQe8aajlr098aMi4Ef9fbquF6GsoPb1AHlzJR8s=; b=W14fTDMsGq3FEMYqSmymjq0OJ9BYditxt3Vz+IFhmUEk+BJjlqDvkQbYijaePQaOcj E7P6ZyI8RDWkbxkGck2ZQy4o8UCfMugxzrfd3YQCO7KBkZkhlEBSw1ZPpvk2i21t7ugn vE+UXIr2I6dR11DN/TAP90su9L3n7WdosB6FqZ9eRm5LcfTnOzud5tcGOcbeGs1RK4XN t002SdOyiOK3HBzgGS5NAkJsXoEGEpDgrmYtkpGDrITiwDbLIhAteCGchK2Qjyzz6ZGj wbrbpXoqHN8VOpxyEQKspTXSPkLPiNbJsJh67ht8teK0NBYn+2R8dJk/COgr8E4R7RBA mCxQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=d0NXBQe8aajlr098aMi4Ef9fbquF6GsoPb1AHlzJR8s=; b=GSkuDFd+VzucZqzfB9js+m2+u30Wk/ujZLyZ7sGd8VogrAuXWm/wivpHZsd309UZVG lX5ZrpljIT3J1wy3AamC5w47F7j9uInDCo2YqB4pVLXQfwzwkUCIf37//mYoTx58SqVR hMTRJlDm92KMcUPpQn76MX/XS29q1eeToP0RBAlk8BYWivGYXoNrPaWjQX7nV3yJ0XX/ GC4T8QP9++s/zzVqxPbMkJjrkL3Hh6PQ+kS9vD1pcC2ZTD6gx5/CKTd2m6LCewFgKnXK b4ksHy9fQJ5Z6ku+DbvijO6EIqGU/XWy/q25BYWlbD//VZDWs6yLVk8ukrlh420/HAXZ 4yoQ== X-Gm-Message-State: AJcUukc7pY78nR0eZHsIcjMy4+pAD9e5EK1W/FpBvw5SmSwO4yu9ishs 7Sp789y8jzaOt9+BxLtpkJ2jOg== X-Received: by 2002:a2e:9783:: with SMTP id y3-v6mr10740533lji.167.1548489151036; Fri, 25 Jan 2019 23:52:31 -0800 (PST) Received: from [192.168.1.169] (h-29-16.A159.priv.bahnhof.se. [79.136.29.16]) by smtp.gmail.com with ESMTPSA id m21sm1962812lfl.97.2019.01.25.23.52.29 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 25 Jan 2019 23:52:30 -0800 (PST) Subject: Re: [PATCH 1/2] spi: support inter-word delay requirement for devices To: Mark Brown Cc: Baolin Wang , LKML , linux-spi , Rob Herring , Mark Rutland , DTML References: <20190125114429.20066-1-jonas@norrbonn.se> <20190125114429.20066-2-jonas@norrbonn.se> <20190125174713.GA6939@sirena.org.uk> <20190125175031.GA25898@sirena.org.uk> From: Jonas Bonn Message-ID: <84d6c40f-62bb-fd00-0dcb-d2f390b136c1@norrbonn.se> Date: Sat, 26 Jan 2019 08:52:29 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.2.1 MIME-Version: 1.0 In-Reply-To: <20190125175031.GA25898@sirena.org.uk> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 25/01/2019 18:50, Mark Brown wrote: > On Fri, Jan 25, 2019 at 05:47:13PM +0000, Mark Brown wrote: >> On Fri, Jan 25, 2019 at 01:06:45PM +0100, Jonas Bonn wrote: > >>> Having this as device property rather than a transfer property allows this >>> to be configured one time in setup() rather than having to fiddle with the >>> configuration register for every transfer. > >> That doesn't mean that the coniguration should be done in DT though, and >> given that this presumably is a property of the device there seems to be >> no reason why we'd have it in DT - if every instance of the device is >> going to need to set the property we should just figure it out from the >> compatble string instead. > > To be clear here: the suggestion is to add a parameter the slave device > can set in spi_device which sets the default word_delay similarly to how > max_speed_hz works. > I'm confused... isn't that exactly what this patch does? It adds a field word_delay to spi_device in the same manner as max_speed_hz. I also added the ability to set it via DT, which I can break out into a separate patch if that's an issue. Or is the problem that it's set via DT, at all? Documentation/devicetree/bindings/spi-bus.txt documents 10 other slave-node properties related to transfer characteristics; word_delay is just another such characteristic. But again, I'm having trouble parsing your response Is the patch wrong, should be broken up, or you just misunderstood it? Thanks, /Jonas