From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Josh Boyer <jwboyer@redhat.com>
Cc: Manoj Iyer <manoj.iyer@canonical.com>,
Chris Ball <cjb@laptop.org>,
Koji Matsumuro <matsumur@nts.ricoh.co.jp>,
stable@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mmc: Always check for lower base frequency quirk for Ricoh 1180:e823
Date: Fri, 14 Oct 2011 09:07:27 -0700 [thread overview]
Message-ID: <20111014090727.2ad3d774@jbarnes-desktop> (raw)
In-Reply-To: <20111005154449.GA2479@zod.bos.redhat.com>
[-- Attachment #1: Type: text/plain, Size: 972 bytes --]
On Wed, 5 Oct 2011 11:44:50 -0400
Josh Boyer <jwboyer@redhat.com> wrote:
> Commit 15bed0f2f added a quirk for the e823 Ricoh card reader to lower the
> base frequency. However, the quirk first checks to see if the proprietary
> MMC controller is disabled, and returns if so. On some devices, such as the
> Lenovo X220, the MMC controller is already disabled by firmware it seems,
> but the frequency change is still needed so sdhci-pci can talk to the cards.
> Since the MMC controller is disabled, the frequency fixup was never being run
> on these machines.
>
> This moves the e823 check above the MMC controller check so that it always
> gets run.
>
> This fixes https://bugzilla.redhat.com/show_bug.cgi?id=722509
>
Applied to linux-next, thanks. I forgot to cc stable on it though;
once it hits Linus's tree you may want to make sure it gets backported
to 3.0.x and 3.1.x.
Thanks,
--
Jesse Barnes, Intel Open Source Technology Center
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2011-10-14 16:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-05 15:44 [PATCH] mmc: Always check for lower base frequency quirk for Ricoh 1180:e823 Josh Boyer
2011-10-05 16:27 ` Manoj Iyer
2011-10-05 16:43 ` Josh Boyer
2011-10-05 18:19 ` Manoj Iyer
2011-10-14 16:07 ` Jesse Barnes [this message]
2011-10-14 16:24 ` Josh Boyer
2011-11-01 18:47 ` Greg KH
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=20111014090727.2ad3d774@jbarnes-desktop \
--to=jbarnes@virtuousgeek.org \
--cc=cjb@laptop.org \
--cc=jwboyer@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=manoj.iyer@canonical.com \
--cc=matsumur@nts.ricoh.co.jp \
--cc=stable@kernel.org \
/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