linux-kernel - Re: [RFC PATCH 1/4] Documentation: mmc: add description for new caps

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 22 Jun 2016 14:30:22 +0200
From:	Ulf Hansson <ulf.hansson@...aro.org>
To:	Rob Herring <robh@...nel.org>
Cc:	Jaehoon Chung <jh80.chung@...sung.com>,
	Shawn Lin <shawn.lin@...k-chips.com>,
	linux-mmc <linux-mmc@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Doug Anderson <dianders@...omium.org>,
	"open list:ARM/Rockchip SoC..." <linux-rockchip@...ts.infradead.org>,
	"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>
Subject: Re: [RFC PATCH 1/4] Documentation: mmc: add description for new caps

On 8 June 2016 at 22:48, Rob Herring <robh@...nel.org> wrote:
> On Wed, Jun 08, 2016 at 04:20:21PM +0800, Shawn Lin wrote:
>> Let's add some basic description for cap-no-sdio,
>> cap-no-sd and cap-no-mmc.
>
> This doesn't say why.
>
> If you know what is there, then there's a better way to do this. Look at
> the child nodes because chances are if you have something soldered down
> like SDIO or eMMC, then you have a child node already for resets,
> regulators, etc.
>

According to patch4, this is a description of the mmc controller,
perhaps together with some limitations as per SoC/platform and thus
has nothing to do with the card.

I have seen several drivers, which needs to validate every single
piece of command to avoid execute those it cannot support.

So, I personally thinks these new DT bindings would be nice to add.

Kind regards
Uffe