Received: by 2002:ac0:950c:0:0:0:0:0 with SMTP id f12csp2058365imc; Tue, 12 Mar 2019 06:19:44 -0700 (PDT) X-Google-Smtp-Source: APXvYqzmz8jf5p26/fdHiKmzQ5y4MvXwiWK8pdxLtX/Hy5jNR6Md+ZfgLT9eGBt5G/oS0gwV66/a X-Received: by 2002:a63:104e:: with SMTP id 14mr34845824pgq.185.1552396783905; Tue, 12 Mar 2019 06:19:43 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1552396783; cv=none; d=google.com; s=arc-20160816; b=VtkILn/+y4zlj6yN4zQeJynNzT1K9OI+iPFrApWLIi0hC4ib5ZxSddTqGSzdTWwq4O xxMNcDOqvKKj9Rm8ER69YxMvC5f9AcRr2AeBYFQI3ix6jHbrrcayiCh5/y/KzwLRN1jR 9hZOsovTIGZs3JAXD0vYHZ/KrUrF8Ia2PqdGdO7OllFPa9XRtifsL9pMgrzNVgf4hEiV mzvTTmo5DeN7EkPyaFnLX4F3bdY3T74we7srn3a3c1fR4kJvrgqgr1Fe+9W+X9T7yaMt khMVt9XrFpLXpLX6OltIocwI5u5nsJkwoMqvEXLHbkeEtqHTsmFYAInzajAKjooVToze /wOA== 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:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from; bh=GZ1kR9w461fOKgZ9FPGk7XIvMEAWv9i/z2b/OhsgEoM=; b=esEYdNolWCx4p2+JlcK0pU/V9MuxJIYcLd96ioEXlg2bnblRECRVTOWNd3BunrsUoZ DsP/HqOZWSsX412jhSLqc9XcVVEBsfZw9O/YHhyXwLvB2v40wzQJJhgOtJg93+Ps4yzP GPOl/5UudQO6c/muZUbFm9NfelTqFLKeTBYUHlKgaLAaDJRjDs07WSM+4Kaesf9MSseh WeXC0zFXbdscwhA8IUBudeTa3YiZvvw2PPBUrVoWbaN39ne0tO+1Q5dhEnL0Ni3mZCpY IbMMQeZFKdwiAi5nLgJ4hunB4uXtGHcERZubC2xWxqKlhJqXBxck8ezJRVWDgVMZ4g7p Ycvw== 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 f3si7795003pfn.122.2019.03.12.06.19.26; Tue, 12 Mar 2019 06:19:43 -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 S1726856AbfCLNSS convert rfc822-to-8bit (ORCPT + 99 others); Tue, 12 Mar 2019 09:18:18 -0400 Received: from gloria.sntech.de ([185.11.138.130]:60206 "EHLO gloria.sntech.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726009AbfCLNSR (ORCPT ); Tue, 12 Mar 2019 09:18:17 -0400 Received: from we0652.dip.tu-dresden.de ([141.76.178.140] helo=phil.localnet) by gloria.sntech.de with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1h3hI4-0001pp-39; Tue, 12 Mar 2019 14:17:56 +0100 From: Heiko Stuebner To: Christoph =?ISO-8859-1?Q?M=FCllner?= Cc: Adrian Hunter , robh+dt@kernel.org, mark.rutland@arm.com, shawn.lin@rock-chips.com, ulf.hansson@linaro.org, Philipp Tomsich , Michal Simek , Douglas Anderson , Viresh Kumar , Enric Balletbo i Serra , Vicente Bergas , Emil Renner Berthing , Randy Li , Tony Xie , Ezequiel Garcia , Klaus Goger , Lin Huang , linux-mmc@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-rockchip@lists.infradead.org Subject: Re: [PATCH v2 2/3] dt-bindings: mmc: Add a new property disable-cqe-dcmd. Date: Tue, 12 Mar 2019 14:17:55 +0100 Message-ID: <4793843.T1TZ7EF8k3@phil> In-Reply-To: <3BCC2A27-3AF4-4E5E-BBD4-6A5B49831D3C@theobroma-systems.com> References: <20190307084329.25416-1-christoph.muellner@theobroma-systems.com> <37a96eda-196e-bacf-7ae2-5b9354c70273@intel.com> <3BCC2A27-3AF4-4E5E-BBD4-6A5B49831D3C@theobroma-systems.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8BIT Content-Type: text/plain; charset="iso-8859-1" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Am Freitag, 8. M?rz 2019, 14:10:45 CET schrieb Christoph M?llner: > > > On 08.03.2019, at 13:46, Adrian Hunter wrote: > > > > On 7/03/19 10:43 AM, Christoph Muellner wrote: > >> This patch documents the new property disable-cqe-dcmd > >> for the Arasan eMMC 5.1 driver. > >> > >> Signed-off-by: Christoph Muellner > >> Signed-off-by: Philipp Tomsich > >> --- > >> Documentation/devicetree/bindings/mmc/arasan,sdhci.txt | 4 ++++ > >> 1 file changed, 4 insertions(+) > >> > >> diff --git a/Documentation/devicetree/bindings/mmc/arasan,sdhci.txt b/Documentation/devicetree/bindings/mmc/arasan,sdhci.txt > >> index 1edbb049cccb..ec699bf98b7c 100644 > >> --- a/Documentation/devicetree/bindings/mmc/arasan,sdhci.txt > >> +++ b/Documentation/devicetree/bindings/mmc/arasan,sdhci.txt > >> @@ -44,6 +44,10 @@ Optional Properties: > >> properly. Test mode can be used to force the controller to function. > >> - xlnx,int-clock-stable-broken: when present, the controller always reports > >> that the internal clock is stable even when it is not. > >> + - disable-cqe-dcmd: The eMMC 5.1 standard specifies direct commands (DCMDs) > >> + as part of the command queue engine (CQE). On controllers with a CQHCI, > >> + such as the Arasan eMMC 5.1 host controller, the driver has to enable DCMDs. > >> + This is done unless disable-cqe-dcmd is specified. This needs a rewording please. See below for hw-description vs. driver, so the description should be centered around why this is a property of the hw [like faulty controller implementation or whatever] > > If "supports-cqe" is in mmc.txt, should "disable-cqe-dcmd" be there also? > > The file mmc.txt says on top: > "These properties are common to multiple MMC host controllers". > As my patchset introduces "disable-cqe-dcmd" just for sdhci-of-arasan, > I would say it should not go into that file. > > Also I wonder why "supports-cqe" is in mmc.txt, because > only sdhci-tegra.c is evaluating that property. > So I would expect it to be documented in > Documentation/devicetree/bindings/mmc/nvidia,tegra20-sdhci.txt > > However, I see that "disable-cqe-dcmd" could go into other drivers as well. > But is this enough to document it in mmc.txt? Devicetree is always about describing the hardware capabilites and never about the actual nitty-gritty of driver implementation, aka it is not meant as a space for hardware-independent config-settings or such. As for only tegra evaluating this, is probably because it is still so new, like january 2019 and Rob explicitly suggested it becoming common [0], which suggests that the disable-cqe-dcmds should probably also be common. Heiko [0] https://lore.kernel.org/patchwork/patch/1031163/