[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAD=FV=UC0V1ALZw-EsJXUQ8eVbFY5OppfOGZxMcexSE3B+1EwQ@mail.gmail.com>
Date: Wed, 22 Jun 2016 21:33:35 -0700
From: Doug Anderson <dianders@...omium.org>
To: Shawn Lin <shawn.lin@...k-chips.com>
Cc: Ulf Hansson <ulf.hansson@...aro.org>,
Jaehoon Chung <jh80.chung@...sung.com>,
Rob Herring <robh+dt@...nel.org>,
"linux-mmc@...r.kernel.org" <linux-mmc@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"open list:ARM/Rockchip SoC..." <linux-rockchip@...ts.infradead.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
Olof Johansson <olof@...om.net>
Subject: Re: [RFC PATCH 1/4] Documentation: mmc: add description for new caps
Hi,
On Wed, Jun 22, 2016 at 6:29 PM, Shawn Lin <shawn.lin@...k-chips.com> wrote:
> 在 2016/6/22 23:06, Doug Anderson 写道:
>>
>> Hi,
>>
>> On Wed, Jun 8, 2016 at 1:20 AM, Shawn Lin <shawn.lin@...k-chips.com>
>> wrote:
>>>
>>> Let's add some basic description for cap-no-sdio,
>>> cap-no-sd and cap-no-mmc.
>>>
>>> Signed-off-by: Shawn Lin <shawn.lin@...k-chips.com>
>>>
>>> ---
>>>
>>> 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
>> <https://lists.ozlabs.org/pipermail/devicetree-discuss/2013-June/034664.html>
>> for reference.
>>
>
> Really? was that the final decision? I just see Olof complained it but
> don't see other comments from dt maintainer or from mmc
> maintainer(Chris Ball)?
>
> Hi Ulf and Rob,
>
> What is your opinion?
Notice that most things added later (like mmc-hs200-1_8v) don't have "cap-"
Powered by blists - more mailing lists