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  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Thu, 20 Mar 2014 14:04:04 +0100
From:	Mike Looijmans <mike.looijmans@...ic.nl>
To:	Eli Billauer <eli.billauer@...il.com>, <monstr@...str.eu>
CC:	Sören Brinkmann <soren.brinkmann@...inx.com>,
	<chris@...ntf.net>, <michal.simek@...inx.com>,
	<linux-mmc@...r.kernel.org>, <devicetree@...r.kernel.org>,
	<linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2] mmc: sdhci: add quirk for broken write protect detection

I totally agree with Eli. The devicetree should read something like "WP is not 
present" (which will be the case on all micro SD readers). Having "WP is 
inverted" there is just misleading.

On our boards, I use MIO0 as a "heartbeat" LED. Combined with a quirk in XPS 
and/or Vivado that the pinmuxing for the WP line is actually routed to MIO0 
when you request it to be unrouted or to EMIO, this made the WP line on our 
systems appear as semi-random.

Mike.

On 03/20/2014 01:39 PM, Eli Billauer wrote:
> Hello Michal.
>
> The Zybo board doesn't have any WP pin connected to the MicroSD card. There is
> no physical possibility for the processor to know whether the card is
> write-protected or not.
>
> As I mentioned earlier, the practical problem can be worked around by
> inverting the polarity of the WP bit, using wp-inverted. Practically speaking,
> there's no need for this patch.
>
> I insisted on this patch, because I think that the device tree should reflect
> the hardware as it is, and not contain tricks for fooling the driver into
> doing what we want. But I guess this wasn't a reason good enough for adding
> yet another quirk (to the existing 38 or so).
>
> Regards,
>     Eli
>
> On 20/03/14 14:26, Michal Simek wrote:
>> we have got this from Mike (we couldn't reply because he has lost this email
>> thread.
>>
>> Mike:
>> "I think I found the issue. In ps7_init.c as generated by the tools, it sets
>> the "WP" pin not to EMIO, but to MIO 0. We use pin 0 for a status LED.
>>
>> # devmem 0XF8000830
>> 0x002E0000
>>
>> Register 0XF8000830 is SD0_WP_CD_SEL, and 0x002E0000 sets CD to pin 46 and
>> WP to pin "0", not to EMIO as I specified in the design.
>> "
>>
>> Eli: Maybe you have the same issue as Mike. Can you please check it?
>
>



Met vriendelijke groet / kind regards,

Mike Looijmans

TOPIC Embedded Systems
Eindhovenseweg 32-C, NL-5683 KH Best
Postbus 440, NL-5680 AK Best
Telefoon: (+31) (0) 499 33 69 79
Telefax:  (+31) (0) 499 33 69 70
E-mail: mike.looijmans@...ic.nl
Website: www.topic.nl

Please consider the environment before printing this e-mail

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists