From: Maxim Levitsky <maximlevitsky@gmail.com>
To: Philip Langdale <philipl@overt.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Pierre Ossman <pierre@ossman.eu>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] port ricoh_mmc to be pci quirk
Date: Fri, 08 Jan 2010 17:24:44 +0200 [thread overview]
Message-ID: <1262964284.12577.27.camel@maxim-laptop> (raw)
In-Reply-To: <20091126235551.2db699e3@fido2.homeip.net>
On Thu, 2009-11-26 at 23:55 -0800, Philip Langdale wrote:
> On Fri, 27 Nov 2009 01:53:04 +0200
> Maxim Levitsky <maximlevitsky@gmail.com> wrote:
>
> > >From 2d3002e29c329d76ca4e26d9f427814151a9648c Mon Sep 17 00:00:00
> > >2001
> > From: Maxim Levitsky <maximlevitsky@gmail.com>
> > Date: Fri, 27 Nov 2009 00:53:28 +0200
> > Subject: [PATCH] port ricoh_mmc to be pci quirk
> >
> > This patch solves nasty problem original driver has.
> > Original goal of the ricoh_mmc was to disable this device because
> > then, mmc cards can be read using standard SDHCI controller,
> > thus avoiding writing of yet another driver.
> > However, the act of disablement, makes other pci functions that
> > belong to this controller (xD and memstick) shift up one level, thus
> > pci core has now wrong idea about these devices.
> >
> > To fix this issue, this patch moves the driver into pci quirk
> > section, thus it is executes before the pci is enumerated, and
> > therefore solving that issue, also same sequence of commands is
> > performed on resume for same reasons.
> >
> > Also regardless of the above, this way is cleaner.
> >
> > You still need to set CONFIG_MMC_RICOH_MMC
> > to enable this quirk
>
> I like it. Only comment is that I'd like the printks to identify which
> controller is involved. If Andrew is happy with the CONFIG mechanism,
> then you've got an ack from me.
>
> Thanks for doing this.
Hi, do you plan to include this patch in the kernel?
BTW, I did write successfully the driver for the xD controller, so now
this is a real problem.
Best regards,
Maxim Levitsky
next prev parent reply other threads:[~2010-01-08 15:24 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-24 0:13 The work of ricoh_mmc isn't detected by pci core Maxim Levitsky
2009-11-24 0:21 ` Philip Langdale
2009-11-25 14:55 ` Maxim Levitsky
2009-11-25 14:58 ` [PATCH] Port ricoh_mmc from driver to pci quirk Maxim Levitsky
2009-11-25 16:53 ` Philip Langdale
2009-11-25 19:35 ` Andrew Morton
2009-11-25 23:40 ` Maxim Levitsky
2009-11-26 1:30 ` Philip Langdale
2009-11-26 23:51 ` Maxim Levitsky
2009-11-26 23:53 ` [PATCH v2] port ricoh_mmc to be " Maxim Levitsky
2009-11-27 7:55 ` Philip Langdale
2010-01-08 15:24 ` Maxim Levitsky [this message]
2010-01-08 15:40 ` Philip Langdale
2010-01-12 23:43 ` Andrew Morton
2010-01-13 1:23 ` Philip Langdale
2010-01-13 6:46 ` Wolfram Sang
2010-01-29 13:37 ` [PATCH v3] port ricoh_mmc to " Maxim Levitsky
2010-01-29 16:06 ` Philip Langdale
2010-01-29 22:10 ` Maxim Levitsky
2010-01-30 2:18 ` Philip Langdale
2010-01-29 16:33 ` Wolfram Sang
2010-01-29 22:13 ` Maxim Levitsky
2010-01-30 21:28 ` [PATCH] Port " Maxim Levitsky
2010-02-01 15:45 ` Maxim Levitsky
2009-11-25 20:30 ` [PATCH] Port ricoh_mmc from driver " Pierre Ossman
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=1262964284.12577.27.camel@maxim-laptop \
--to=maximlevitsky@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=philipl@overt.org \
--cc=pierre@ossman.eu \
/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