Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp3373836imu; Mon, 28 Jan 2019 03:51:30 -0800 (PST) X-Google-Smtp-Source: ALg8bN6vB+3TE7t93AyY5J4jepnDmGLBRbe1ZoZ1z72cq7LfIbPX78EHeLAkcDHt5rvmk/0pQi0g X-Received: by 2002:a62:1484:: with SMTP id 126mr21330011pfu.257.1548676290913; Mon, 28 Jan 2019 03:51:30 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1548676290; cv=none; d=google.com; s=arc-20160816; b=dS+5Tn2VkNSn15ssjDVDrYYLgpujCePnG/ILWTgQpendYaMWtPvGS2dJzbzN3m80ku kURawokuxu5oHd+IGMwVSXtPTnhpcsxQV9wJqmlIGg4Ead9onSOZCweTRiEU32drg+F+ NzqlFgbPBPLHshJY9qhgdfSnDI2R1ZMcNrOUlOdSxv5AgtQdejy57PjGlBX3ZZs+9CPd GV/CTd15BPM59/mA1Q+RHMAjosMfj+s0yG0SdAw2apWzHJ1udr/5tDVFLNX5cL06gmDz C0pdaRDxXSCnJ/wXHhSj20NF5Wjna/AiqdTd6DjzzBVrAkvqoB8U8Nzas+UUJo0Dsfdx Pc+Q== 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=zoqZWGIgSxbwt3XyKpf1Pf33WL2f0j+yvIlyD8JFDBM=; b=wobDdbO9SPpqx2ZPMnO6fNKB1igGAq1iuROrHQ1Bn2VW9S44PX/rXxC2h1GlUxXT2s 3M18ubYlbdbJbna2Y5gB/U9daB30A/uI9KcWMInfiCABZUtVtwsUIjX2Ugzc4KmidtU4 16WzNj0pyvCCNjUNMnCXyiFiEvlpXhQbToLXzqv0Sk5jTZVWTlx8zX4C8d/HfloC6z8g t4MunHhW8nogQ+A451gPV5Bh5Zs2eW3o6KCwv5G4Va6t9RU7h/2HGItlngQPKySkcVYM Zd2f5ij3NWsvgFUw/AYazXEuNPexALmc1PgI/Bulpv2cvY822HeWqAqpMiYE+Y50bCco 25sQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@norrbonn-se.20150623.gappssmtp.com header.s=20150623 header.b=eQSqaLCR; 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 87si32106048pfs.7.2019.01.28.03.51.15; Mon, 28 Jan 2019 03:51:30 -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=eQSqaLCR; 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 S1726805AbfA1LvH (ORCPT + 99 others); Mon, 28 Jan 2019 06:51:07 -0500 Received: from mail-lf1-f65.google.com ([209.85.167.65]:37016 "EHLO mail-lf1-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726661AbfA1LvH (ORCPT ); Mon, 28 Jan 2019 06:51:07 -0500 Received: by mail-lf1-f65.google.com with SMTP id y11so11609186lfj.4 for ; Mon, 28 Jan 2019 03:51:05 -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=zoqZWGIgSxbwt3XyKpf1Pf33WL2f0j+yvIlyD8JFDBM=; b=eQSqaLCRJQk0yHT47/lmhZDAkz2JMAWmLfA0B2qH9ER5TsCFrVpMaPwgR9Knxkz6ib OVDhgROwG9ir2fyO7MdF+vwTS2mhmlQMN08xfkj1MoGrOoMZ3KC5ORVhZsx2dADLs/MP aC7Qr9cy0nxEWhxIOC82JLZCy123A1R1OMIZOoqpU1EHtvJIpRNFna6eDOa8aFv5z7kR izgtv40JxTw/z09HDpCWU9PZubwUpE87IyYF63wv5yPFFCgNNkJj5R5LHBEK3Y/ghgr1 xrgnpC4YvatFk0lmuMvvwd4BIWGvF7ZZwedSz0nsoocTANTz9UKSSrHpXJaoe/tgtYaF 8piQ== 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=zoqZWGIgSxbwt3XyKpf1Pf33WL2f0j+yvIlyD8JFDBM=; b=ZOYEZCqlUyUmFbbCke5FPSrXmwuYIM9xuh71NgQ6j0g+ME7FQ1FrF45CzHJJOsEH+Q mv66/F6+ktU++sTwq49AtO6enwtYm1nBcfvzZHhtiu9wJl0W0wZHg8sQpihjZL+RW4YU Xp4RpKDGUPWJjzhCo0GAYuOC0Wu/mXknvMvmkigpdFQNWBhN5bFX0m374VeYxYnxYwpT 7FzQR+RfFs83r9xyddxjuIp14sNLzXQk1jlfK9UvF2AdPaTDAdu8dJkCvDnGd00HrgfG p+VUkpUQkTDZdkMp7gOCWIVpUUiaJPuOzvEij3TLimRJoOXxuYi3Naiy0XmTm9a/xgsW npNA== X-Gm-Message-State: AJcUukdstxUdS4UcBTD4zyqB12DxEjlZ+9PpvV7nnxSz7Yt4t0Y2E6s8 XTjHswe8mjWC1xkufPKzq6L/ag== X-Received: by 2002:a19:1f54:: with SMTP id f81mr16532479lff.153.1548676264735; Mon, 28 Jan 2019 03:51:04 -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 t22sm3044934lfb.0.2019.01.28.03.51.03 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 28 Jan 2019 03:51:04 -0800 (PST) Subject: Re: [PATCH 1/2] spi: support inter-word delay requirement for devices To: Mark Brown , Geert Uytterhoeven 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> <84d6c40f-62bb-fd00-0dcb-d2f390b136c1@norrbonn.se> <20190128114757.GA11699@sirena.org.uk> From: Jonas Bonn Message-ID: <94c7514c-de1f-ff70-d2b7-6394f9747942@norrbonn.se> Date: Mon, 28 Jan 2019 12:51:02 +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: <20190128114757.GA11699@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 28/01/2019 12:47, Mark Brown wrote: > On Mon, Jan 28, 2019 at 08:41:05AM +0100, Geert Uytterhoeven wrote: >> On Sat, Jan 26, 2019 at 4:40 PM Jonas Bonn wrote: > >>> spi-3wire: again, only set by MAXIM DS-1302 which always needs this >>> setting; driver could set this > >> For DS1302, this is probable true. >> Some devices may support both 4-wire or 3-wire mode? > > IIRC yes. Just for the record, the datasheet says it's exclusively 3-wire. But it's not important... /Jonas > >>> Yeah, that one make sense. But if the DT is only overriding the maximum >>> device frequency that the driver should otherwise be setting, why is >>> spi-max-frequency a _required_ property? > >> That's a good question. Legacy? > > It's a documentation error. >