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  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 22 Dec 2014 11:04:42 +0100
From:	Ulf Hansson <>
To:	Bjorn Andersson <>
Cc:	Bjorn Andersson <>,
	Anton Vorontsov <>,
	Chris Ball <>,
	Rob Herring <>,
	Pawel Moll <>,
	Mark Rutland <>,
	Ian Campbell <>,
	Grant Likely <>,
	"open list:OPEN FIRMWARE AND..." <>,
	open list <>,
	"open list:SECURE DIGITAL HO..." <>
Subject: Re: [PATCH] mmc: dt: Add property for broken hs200 quirk

On 19 December 2014 at 21:01, Bjorn Andersson <> wrote:
> On Fri, Dec 19, 2014 at 3:38 AM, Ulf Hansson <> wrote:
>> On 12 December 2014 at 20:28, Bjorn Andersson
>> <> wrote:
>> Some more explanation to why this needed would be good.
> Because (according to the git log) some of the memories that we
> mounted in Xperia Z1 does not support HS200 even though they advertise
> they are.

I see. How about using an mmc card quirk instead of a DT binding then?

Kind regards

> I thought we needed for the device I'm testing with, but a couple of
> regulator_set_optimum_mode() solved that - so I have to provide a
> patch for that as well...
>>> Signed-off-by: Bjorn Andersson <>
>>> ---
>>>  Documentation/devicetree/bindings/mmc/mmc.txt | 2 ++
>> This file lists the generic mmc DT bindings, but you want to add a
>> specific binding for sdhci?
> Looking in sdhci_get_of_property() it's a mash of device specific
> properties, sdhci specific properties documented in mmc.txt and
> generic sdhci properties documented in device specific bindings.
> Would you like me to move it to a generic sdhci.txt binding and update
> the individual sdhci-* to reference that instead of mmc.txt? Or should
> I just add the property in the device specific bindings? Or maybe we
> could keep it as a optional property in mmc.txt?
> Regards,
> Bjorn
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists