Received: by 2002:ac0:bc90:0:0:0:0:0 with SMTP id a16csp5250559img; Wed, 27 Mar 2019 05:11:01 -0700 (PDT) X-Google-Smtp-Source: APXvYqzvLUKuWXHtm+v9VF54FiIjlMl0J7K0cinjOv2wrajmCn6JNxNvj/YHXe0eZa9swYXBEVzB X-Received: by 2002:a63:c548:: with SMTP id g8mr30923618pgd.451.1553688661642; Wed, 27 Mar 2019 05:11:01 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1553688661; cv=none; d=google.com; s=arc-20160816; b=0/u+UYGvztJmlIcbRSC/JBnbpGIToTGv4/VhfsSI6HVwcFlDPfxHgDVAB0OoRR/y6M bE12RyquzDbqfv66lb5aKqNCtY1rikqMy10aOOocCiYkSYQs1LTMPkVa6dwxxWk1xrY7 bBIHDgH5M/kfvl2PbndhzKrX8vt/i7PvqtVQ+3RPYPy0f5yP3fhFs82W2ukLROInGjU7 JUrQvELDx2PWJwTI8yR3sr7kSGi3Hdqcd7hTzvrs23CDh7Cyxy3o7zYXHxS/CO5pu0QI KMpva4Z9yyjHR39doBPM5aHPVwKouNxVNCj6xV/JVtLF1fi/qBz5k1k3gPmdyyWVO4jF Vkbw== 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; bh=fqt5fya8knFlDyCoHNfsIRyS7rgPNIzBHI8a4wIvCXc=; b=f6HNWx08Usxb6wxE9uk1kycYc308JgM9s2AzjSWXd0663gW3Wy+9BIMjk1/f5GfhUw vyelVvrbT+N6vrwI5L0rrgUS8pAKjfayudbVJK1kKqvdbhe2bTbuPVoQIyeKqwo39Isy gVR6u/fCRNYwnmgIvKkQu8f2zRKWIBIzaDsfnkvLCIbyCwoDckUWXsliA8KJevvG4VuJ n+HC5GNLH4ys68kcHOiJQeqlVEsCAQlDY5POdDOdrUswZBgD1bkdE5vVBbAxGw8j8p0f axLFpb+u5yAW5CnRsq5s0Da8aqDcsDyVWzn0Hw5ar95buMQCn8b/BrFSrvFN/QuNbbAj Y+fQ== ARC-Authentication-Results: i=1; mx.google.com; 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 h37si19450817plb.93.2019.03.27.05.10.45; Wed, 27 Mar 2019 05:11:01 -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; 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 S1728444AbfC0MKK (ORCPT + 99 others); Wed, 27 Mar 2019 08:10:10 -0400 Received: from usa-sjc-mx-foss1.foss.arm.com ([217.140.101.70]:53578 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728130AbfC0MKI (ORCPT ); Wed, 27 Mar 2019 08:10:08 -0400 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.72.51.249]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 6247E374; Wed, 27 Mar 2019 05:10:08 -0700 (PDT) Received: from [10.1.196.75] (e110467-lin.cambridge.arm.com [10.1.196.75]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 74F8B3F557; Wed, 27 Mar 2019 05:10:07 -0700 (PDT) Subject: Re: [PATCH v2] arm64: dts: rockchip: add rk3399 UART DMAs To: Katsuhiro Suzuki , Heiko Stuebner Cc: linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org References: <20190321162244.10080-1-katsuhiro@katsuster.net> <8309531.dRdlsDmmhi@phil> From: Robin Murphy Message-ID: <07287fad-c3e6-bcf2-a247-fe4f5031900e@arm.com> Date: Wed, 27 Mar 2019 12:10:05 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.5.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-GB Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 26/03/2019 13:49, Katsuhiro Suzuki wrote: > Hello Robin, > > Sorry for inconvenience. Since I don't adhere enabling DMA for UARTs, > please revert my patch if you need. I found a little time to fire up the board again this morning, so I gave this another try to double-check - in fact this time I only saw it fail 3 times in 15 reboots. So something's certainly not quite right, but it's not quite as terrible as the first try implied. My suspicion at this point is that the DMA implementation might be losing characters occasionally, and obviously the bluetooth firmware transfer is going to be a lot more sensitive to that than a text console is. > BTW, there are DMA properties in RK3328 device-tree like as this patch. > RK3328 UART DMA could not work correctly too...?? Quite possibly, although my 3328 box doesn't have any UARTS connected or exposed other than the standard debug console, so I can't easily investigate there. I do have a 3288 box with similar serial bluetooth to my 3399 which might be worth digging out for comparison with an up-to-date kernel. Robin. > > Best Regards, > Katsuhiro Suzuki > > > On 2019/03/26 20:48, Robin Murphy wrote: >> On 25/03/2019 12:34, Heiko Stuebner wrote: >>> Am Donnerstag, 21. März 2019, 17:22:44 CET schrieb Katsuhiro Suzuki: >>>> Add UART dma channels as specified by the rk3399 TRM. >>>> >>>> Refer: >>>> RK3399 TRM V1.4: Chapter 12 DMA Controller >>>> >>>> Signed-off-by: Katsuhiro Suzuki >>> >>> applied for 5.2 >> >> As a heads-up, I did manage to try my board with this patch applied >> over the weekend, and it makes probing the bluetooth adapter fail with >> communication errors, so I'm not sure the 8250 and pl330 drivers are >> really cooperating well enough :( >> >> Robin. >> >