public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Ball <cjb@laptop.org>
To: Takashi Iwai <tiwai@suse.de>
Cc: Aries Lee <arieslee@jmicron.com>,
	linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mmc: Fix read-only detection with JMicron 388 chip
Date: Thu, 21 Apr 2011 13:36:03 -0400	[thread overview]
Message-ID: <m3y6338q2k.fsf@pullcord.laptop.org> (raw)
In-Reply-To: <s5hmxjjil9r.wl%tiwai@suse.de> (Takashi Iwai's message of "Thu, 21 Apr 2011 19:09:36 +0200")

Hi Takashi,

On Thu, Apr 21 2011, Takashi Iwai wrote:
>> I don't like overwriting ops here -- it's too magical, and now we have
>> to maintain the ops table in two places.  A quirk seems justified here,
>> even though we're trying to reduce them in general.
>
> Well, I also used quirk bit in my very first version I worked for
> 2.6.32 kernel.  But when I looked at 2.6.39, quirks are almost full --
> only the last one bit is left for bit 31.  So I didn't want to finish
> it :)
>
>>  Can anyone find a better solution?
>  
> One way would be to copy the ops table itself in struct sdhci_host
> instead of keeping the ops table pointer.  Then you can overwrite only
> the specific op in each probe_slot callback.

I think I'd rather not touch ops at all and keep the code simple --
if you don't mind, please post a version with quirks, and I'll work
on freeing up a few bits.

Thanks,

- Chris.
-- 
Chris Ball   <cjb@laptop.org>   <http://printf.net/>
One Laptop Per Child

  reply	other threads:[~2011-04-21 17:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-21 16:00 [PATCH] mmc: Fix read-only detection with JMicron 388 chip Takashi Iwai
2011-04-21 16:40 ` Chris Ball
2011-04-21 17:09   ` Takashi Iwai
2011-04-21 17:36     ` Chris Ball [this message]
2011-04-21 18:24       ` Takashi Iwai

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=m3y6338q2k.fsf@pullcord.laptop.org \
    --to=cjb@laptop.org \
    --cc=arieslee@jmicron.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=tiwai@suse.de \
    /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