From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752859AbcFVPGY (ORCPT ); Wed, 22 Jun 2016 11:06:24 -0400 Received: from mail-vk0-f46.google.com ([209.85.213.46]:33682 "EHLO mail-vk0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751315AbcFVPGW (ORCPT ); Wed, 22 Jun 2016 11:06:22 -0400 MIME-Version: 1.0 In-Reply-To: <1465374021-2526-1-git-send-email-shawn.lin@rock-chips.com> References: <1465373996-2485-1-git-send-email-shawn.lin@rock-chips.com> <1465374021-2526-1-git-send-email-shawn.lin@rock-chips.com> From: Doug Anderson Date: Wed, 22 Jun 2016 08:06:20 -0700 X-Google-Sender-Auth: ju0wwUy3A6qjI-4dlQbHHQrn9kI Message-ID: Subject: Re: [RFC PATCH 1/4] Documentation: mmc: add description for new caps To: Shawn Lin Cc: Ulf Hansson , Jaehoon Chung , Rob Herring , "linux-mmc@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "open list:ARM/Rockchip SoC..." , "devicetree@vger.kernel.org" , Olof Johansson Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, On Wed, Jun 8, 2016 at 1:20 AM, Shawn Lin wrote: > Let's add some basic description for cap-no-sdio, > cap-no-sd and cap-no-mmc. > > Signed-off-by: Shawn Lin > > --- > > Documentation/devicetree/bindings/mmc/mmc.txt | 3 +++ > 1 file changed, 3 insertions(+) > > diff --git a/Documentation/devicetree/bindings/mmc/mmc.txt b/Documentation/devicetree/bindings/mmc/mmc.txt > index ecc007a..e16d42b 100644 > --- a/Documentation/devicetree/bindings/mmc/mmc.txt > +++ b/Documentation/devicetree/bindings/mmc/mmc.txt > @@ -39,6 +39,9 @@ Optional properties: > - cap-power-off-card: powering off the card is safe > - cap-mmc-hw-reset: eMMC hardware reset is supported > - cap-sdio-irq: enable SDIO IRQ signalling on this interface > +- cap-no-sdio: skip sending sdio cmd during initialization > +- cap-no-sd: skip sending sd cmd during initialization > +- cap-no-mmc: skip sending mmc cmd during initialization In the past it has been determined that the "cap-" prefix is unnecessary. Some properties still have "cap-" because of backward compatibility reasons, but as I understand it new properties shouldn't start with "cap-". See for reference. -Doug