[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAPDyKFqmTP1+pe7UNavOAZA0QWFOu8M4FcQOpGkqZj=nnpP9qA@mail.gmail.com>
Date: Fri, 16 Dec 2016 12:07:42 +0100
From: Ulf Hansson <ulf.hansson@...aro.org>
To: Masahiro Yamada <yamada.masahiro@...ionext.com>
Cc: Rob Herring <robh@...nel.org>,
linux-mmc <linux-mmc@...r.kernel.org>,
Adrian Hunter <adrian.hunter@...el.com>,
Douglas Anderson <dianders@...omium.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
Al Cooper <alcooperx@...il.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Stefan Wahren <stefan.wahren@...e.com>,
Andrei Pistirica <andrei.pistirica@...rochip.com>,
Wolfram Sang <wsa+renesas@...g-engineering.com>,
Mark Rutland <mark.rutland@....com>,
Simon Horman <horms+renesas@...ge.net.au>
Subject: Re: [PATCH v5 2/2] mmc: sdhci-cadence: add Cadence SD4HC support
[...]
>>
>> I think a better approach is to use the new sdhci-caps* bindings to
>> mask those caps that can't be trusted. And then use the generic mmc
>> bindings for speed modes instead.
>>
>> That should be a safer approach, right!?
>
> Right.
>
> But, if I know the caps register bits 63-32 are all zero,
> I need not explicitly specify sdhci-caps-mask, right?
Maybe not. I don't have a strong opinion here, so l am fine with
whatever you choose.
Kind regards
Uffe
Powered by blists - more mailing lists