linux-mmc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eli Billauer <eli.billauer@gmail.com>
To: Chris Ball <chris@printf.net>
Cc: michal.simek@xilinx.com, linux-mmc@vger.kernel.org
Subject: Re: [PATCH] mmc: sdhci: add quirk for broken write protect detection
Date: Mon, 24 Feb 2014 02:54:06 +0200	[thread overview]
Message-ID: <530A982E.80200@gmail.com> (raw)
In-Reply-To: <86r46ts70i.fsf@void.printf.net>

Hello Chris.

On 24/02/14 02:12, Chris Ball wrote:
> Hi Eli,
>
> On Sun, Feb 23 2014, Eli Billauer wrote:
>    
>> The write protection signal is absent on a board based upon Xilinx' Zynq
>> processor ("ZyBo"). This leads the kernel to think that the MicroSD card is
>> write protected, and causes a kernel panic during boot, as root fails to
>> mount RW.
>>
>> This patch adds a quirk and an optional OF property, sdhci,wp-broken to
>> work around this issue.
>>      
> Just to confirm your motivation for the patch:  wp-inverted would solve
> this problem for you, but you'd rather add a new property that more
> accurately describes the hardware?
>    
Yes, that's the point.
> (We'd probably use broken-wp, for symmetry with the existing broken-cd.)
>    
I picked "sdhci,wp-broken" because of the similarity with 
"sdhci,wp-inverted", as opposed to "broken-cd" (with no "sdhci," prefix).

Would you like me to resubmit the patch with "broken-wp"? Or maybe 
"sdhci,broken-wp"?

Regards,
    Eli

  reply	other threads:[~2014-02-24  1:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-23 23:32 [PATCH] mmc: sdhci: add quirk for broken write protect detection Eli Billauer
2014-02-24  0:12 ` Chris Ball
2014-02-24  0:54   ` Eli Billauer [this message]
2014-11-27 14:08 ` Raul

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=530A982E.80200@gmail.com \
    --to=eli.billauer@gmail.com \
    --cc=chris@printf.net \
    --cc=linux-mmc@vger.kernel.org \
    --cc=michal.simek@xilinx.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).