Received: by 10.213.65.68 with SMTP id h4csp1959631imn; Thu, 5 Apr 2018 06:47:11 -0700 (PDT) X-Google-Smtp-Source: AIpwx48SXdGRL6W0KEg0Nltf5wPI0LYmz2XdCQMjlR7B15tN3nzPdVS12aEwE+tk4/OvMb8QMeWT X-Received: by 2002:a17:902:7291:: with SMTP id d17-v6mr22495279pll.16.1522936031144; Thu, 05 Apr 2018 06:47:11 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1522936031; cv=none; d=google.com; s=arc-20160816; b=VeAhAeFF75F/HRAXO5vE/nlZiolXkTaa9uB79Qu+aFUv58Axu1DQtgAPWsZEqYd+Ug r5jx7dSGHn5EJcJ/WSjtKw0t0kQ6N3zztiYImhBAMc9SFGN80fQxkeK56ElQUHyp1TeL OkK6BAdMW+tsFSCuoFQukKSpmXdLoZhBLmSnQyfY4ehOuNTlP0kHCynFyuX+tvlvyuv3 aeXf7AQddDiVQMyKUulOzuFQdcv/2jcrRDWLAFj/4C2QAv4KOFjio6AD5dV/3ZTxm9Hq tfQOGZR1poHfpw34mNHxpBjUyEUdqXC/9lfLIacGJDGPDJden233az7ylBt3WEZ1I99u Jsmg== 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=0PWQtOYScOCC60PKyQbDftlMnoCuxytmxQLBYubAszk=; b=o5Igpeg9YMmnpH0MdIxG7Lf5whIuxDKdf9hKNfxJ6OT2PepffyCsWHujEeR8avW51Q pIGHDc84PW1kOasiwwfYAEc3KYP/U08MpJaXSrIyU2otAB6dobbpfvVluJIMVxjNAVj/ fSVbxTzN8IUsZpHw7cCa4357lfn2YiidhhY0w2o1kjyeZ0xUja5lw+/TwHw54YUHJx15 bjqBINxXeRS9fZA6cIoWO2DDfpC5729yl1f23CyaStI8jvYpf5DXVHPlP/JbswGXfcMs N9EqtnioGBHJQSLKts0aXlxFXvF7wtF7Sn8Rajqe713d5ooE653vZi0FvLDIVo3TY1Go QHkA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@orpaltech.com header.s=mailru header.b=duekmI58; 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 c6-v6si6150178plr.620.2018.04.05.06.46.57; Thu, 05 Apr 2018 06:47:11 -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=duekmI58; 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 S1751749AbeDENo1 (ORCPT + 99 others); Thu, 5 Apr 2018 09:44:27 -0400 Received: from smtp16.mail.ru ([94.100.176.153]:52454 "EHLO smtp16.mail.ru" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751593AbeDENoX (ORCPT ); Thu, 5 Apr 2018 09:44:23 -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=0PWQtOYScOCC60PKyQbDftlMnoCuxytmxQLBYubAszk=; b=duekmI58Va7zNvNtprjisj/IUziswAPAc6jQve9326jjm9j2MuIVT7+2A3KC3KpNt28uS4Ff/YQLc94E8uj1WpI9ai+Y6aUsZwDroghWhCIC+zUK2e6RBx9pseF5Gaf1kRjhwMeKYm+zQSxX2Tuk8yeZbk5aVSkZKhIPJJvQ0AM=; Received: by smtp16.mail.ru with esmtpa (envelope-from ) id 1f45Bc-00036U-D8; Thu, 05 Apr 2018 16:44:20 +0300 Subject: Re: [PATCH v3 3/6] spi: sun6i: restrict transfer length in PIO-mode To: Mark Brown Cc: Maxime Ripard , Chen-Yu Tsai , linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-spi@vger.kernel.org References: <20180403154449.2443-1-ssuloev@orpaltech.com> <20180403154449.2443-4-ssuloev@orpaltech.com> <20180404065048.n76r3ytuznd6fqsl@flea> <20180405091913.ky4dnmszoobn2xry@flea> <20180405131735.GB12349@sirena.org.uk> From: Sergey Suloev Message-ID: <8159c3a5-af74-9f13-aedb-7ecc708bdff6@orpaltech.com> Date: Thu, 5 Apr 2018 16:44:16 +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: <20180405131735.GB12349@sirena.org.uk> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US Authentication-Results: smtp16.mail.ru; auth=pass smtp.auth=ssuloev@orpaltech.com smtp.mailfrom=ssuloev@orpaltech.com X-7FA49CB5: 0D63561A33F958A562424A6E3C855EC53453D82D03A234027AB98F46BDEDFE59725E5C173C3A84C3A1C30C8AFC676C8BA9E697674C83CBBDB58781B77DE60D36C4224003CC836476C0CAF46E325F83A50BF2EBBBDD9D6B0F05F538519369F3743B503F486389A921A5CC5B56E945C8DA X-Mailru-Sender: C5364AD02485212F3ACDC11E67D8491773629529CE441DBAAF7FE6EBE53B8FEB069BFC61DABEEB110841D3AAAB1726C63DDE9B364B0DF289264D2CD8C2503E8C22A194DADEED8EEDCA01A23BA9CD1BE7ED14614B50AE0675 X-Mras: OK Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 04/05/2018 04:17 PM, Mark Brown wrote: > On Thu, Apr 05, 2018 at 12:59:35PM +0300, Sergey Suloev wrote: >> On 04/05/2018 12:19 PM, Maxime Ripard wrote: >>> The point of that patch was precisely to allow to send more data than >>> the FIFO. You're breaking that behaviour without any justification, >>> and this is not ok. >> I am sorry, but you can't. That's a hardware limitation. > Are you positive about that? Normally you can add things to hardware > FIFOs while they're being drained so so long as you can keep data > flowing in at least as fast as it's being consumed. Well, normally yes, but this is not the case with the hardware that I own. My a20 (BPiM1+) and a31 (BPiM2) boards behaves differently. With a transfer larger than FIFO then TC interrupt never happens.