Received: by 10.213.65.68 with SMTP id h4csp3710389imn; Tue, 3 Apr 2018 09:26:14 -0700 (PDT) X-Google-Smtp-Source: AIpwx4+h0v4kzUewsPf2hcaC6zAIN5jFJBheb+qIDvUWV3/QIAgTD4Nh/lTBKB7lNOcXfMtCs86E X-Received: by 2002:a17:902:149:: with SMTP id 67-v6mr15102447plb.296.1522772774561; Tue, 03 Apr 2018 09:26:14 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1522772774; cv=none; d=google.com; s=arc-20160816; b=eBtYboAo/nNpMRAVUd0lYyTpfqbs5KJsI0+xlUTz4+Ki965Y7xDtgFYVq93bZwEN7u hyKPVFLprgVY49In02WQV3+8U87yWd0iqCFsBRwoALc77h00JwOqgq6FB0nTKmcU2i6r NtYeEnozltx7jbjuxisimqNd3J61Gbh0bW+QTn4kArWs3A0o+6mRleDJ2p2U8qBY+7s7 f58Lu6qaZh38dkP0enPEd2hDI+pm6jE6ljJRqlhyRBb4NJJzi8pvrNYzkH3nM5HDX2Zz XcH2tX3hpQnfddReUiS6eVSBUXpclL4HfnUha+lh+mxgh2EzXkm+zPlMr+KITv+Wwfqe HGwg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-language :content-transfer-encoding:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:dkim-signature :arc-authentication-results; bh=CZLi5lyludkjh8VVEC6YCcVJhVBE6K+EMbBMNMJGYg8=; b=kjQB7EoUvbWgDcSaNHl5p9gU9z7w2gZftg1p53wi7J4o7+u3haq2HmcbFZfstR81Qi KJrx3VzMQslH+BEgKpZEB4cMVuIxDyUJQ8l84G1WrxMErBsFYJ0eISdrBTWHb/4SQuDT Osa6Ccjrv/KPtcgC8btD23vjEgibsWXazqo/mCbUSKIXufIVPeN+SPanukiZCK+jHCAA l6tDZ1pmMr3nqlmkv5Rrxx7x6QU+UkDqPTOtJXq2fUMOmztregCWr/dGVRx12/F+od+T 4wvPtkJgkdKEOtjfZcyfVkNKMRhq3uh/p87sDTTTIK5McOYTnmpnO0rBjvoRQf9iontz BflQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@orpaltech.com header.s=mailru header.b=PVVEze3+; 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 p14si2390386pff.211.2018.04.03.09.26.00; Tue, 03 Apr 2018 09:26:14 -0700 (PDT) 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=@orpaltech.com header.s=mailru header.b=PVVEze3+; 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 S1752414AbeDCQYR (ORCPT + 99 others); Tue, 3 Apr 2018 12:24:17 -0400 Received: from smtp62.i.mail.ru ([217.69.128.42]:33334 "EHLO smtp62.i.mail.ru" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751469AbeDCQYQ (ORCPT ); Tue, 3 Apr 2018 12:24:16 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=orpaltech.com; s=mailru; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:MIME-Version:Date:Message-ID:From:References:Cc:To:Subject; bh=CZLi5lyludkjh8VVEC6YCcVJhVBE6K+EMbBMNMJGYg8=; b=PVVEze3+KBSNRFK0uh+Rc+lBNOMMgEcJSZ1A2YrCV4y1Aqk/idS3y28m+abJSkM+QRhfRhoJAUDdfUj5iofr+TBcLhDoat8pYeROjukn5zgyjAdC9XveKiUVnbS4B4S9IScwhwuk+w+2Lzg5kisQlvQ/++0t5WeZ4YRakDoW6g4=; Received: by smtp62.i.mail.ru with esmtpa (envelope-from ) id 1f3OjE-0008CR-UX; Tue, 03 Apr 2018 19:24:13 +0300 Subject: Re: [PATCH v2 1/6] spi: core: handle timeout error from transfer_one() To: Mark Brown Cc: Maxime Ripard , Chen-Yu Tsai , linux-spi@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org References: <20180403152905.1524-1-ssuloev@orpaltech.com> <20180403152905.1524-2-ssuloev@orpaltech.com> <20180403155224.GA11578@sirena.org.uk> <20180403161824.GB11578@sirena.org.uk> From: Sergey Suloev Message-ID: Date: Tue, 3 Apr 2018 19:24:11 +0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: <20180403161824.GB11578@sirena.org.uk> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US Authentication-Results: smtp62.i.mail.ru; auth=pass smtp.auth=ssuloev@orpaltech.com smtp.mailfrom=ssuloev@orpaltech.com X-7FA49CB5: 0D63561A33F958A5FD29AC8487AFC76645D69CFE915011F8C0A55FB0EC7263FE725E5C173C3A84C30584FF81F342DA07CE36787672731931D028CC0B556B22BCC4224003CC836476C0CAF46E325F83A50BF2EBBBDD9D6B0F05F538519369F3743B503F486389A921A5CC5B56E945C8DA X-Mailru-Sender: C5364AD02485212F3ACDC11E67D8491782A192941C52799AE31CBED767B1E567069BFC61DABEEB110841D3AAAB1726C63DDE9B364B0DF289264D2CD8C2503E8C22A194DADEED8EEDCA01A23BA9CD1BE7ED14614B50AE0675 X-Mras: OK Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 04/03/2018 07:18 PM, Mark Brown wrote: > On Tue, Apr 03, 2018 at 07:00:55PM +0300, Sergey Suloev wrote: >> On 04/03/2018 06:52 PM, Mark Brown wrote: >>> On Tue, Apr 03, 2018 at 06:29:00PM +0300, Sergey Suloev wrote: >>>> As long as sun4i/sun6i SPI drivers have overriden the default >>>> "wait for completion" procedure then we need to properly >>>> handle -ETIMEDOUT error from transfer_one(). >>> Why is this connected to those drivers specifically? >> These 2 drivers have their own "waiting" code and not using the code from >> SPI core. > Does this not apply to any other driver - why is this something we only > have to do when these drivers do it? That's what's setting off alarm > bells. sun4i/sun6i drivers have let's say "smart" waiting while SPI core uses a fixed interval to wait. I can't say for every SPI driver in kernel, that's outside of my area of expertise.