From: Wolfram Sang <w.sang@pengutronix.de>
To: "Luis R. Rodriguez" <lrodriguez@atheros.com>
Cc: cjb@laptop.org, linux-mmc@vger.kernel.org,
linux-kernel@vger.kernel.org, vmehta@atheros.com,
naveen.singh@atheros.com, kvalo@adurom.com, j@w1.fi
Subject: Re: [RFC 0/4] sdhci: few patches for ENE 712 support
Date: Sat, 19 Mar 2011 10:15:44 +0100 [thread overview]
Message-ID: <20110319091544.GA16635@pengutronix.de> (raw)
In-Reply-To: <1300486320-23607-1-git-send-email-lrodriguez@atheros.com>
[-- Attachment #1: Type: text/plain, Size: 1162 bytes --]
> I prefer code upstream though so here is my split and cleanup
> of these patches. I've tested it with my ENE card. Since I am
> new to SDHCI I would prefer someone with more experience review
> these chagnes and the respective commit log messages. I've
> tried to make sense of them as best as I can. Unfortunately
> I was not given any explanation to these changes except the
> patch I got so I tried to make the best of it.
You did make the best out of it; still, you probably won't be surprised to hear
that all the patches are, well, not acceptable ;) I agree with Chris about 1/4,
I think 2-4 are for a broken card detection and there is already a quirk for
that. So you could also try dropping 2-4 and use
sdhci.debug_quirks = 0x8028
That should enable the standard quirks for this card and BROKEN_CARD. Can you
alsso please post the PCI-ID of this card? And does it make a difference if you
use the SDIO-WLAN card or a standard SD memory card?
Regards,
Wolfram
--
Pengutronix e.K. | Wolfram Sang |
Industrial Linux Solutions | http://www.pengutronix.de/ |
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2011-03-19 9:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-18 22:11 [RFC 0/4] sdhci: few patches for ENE 712 support Luis R. Rodriguez
2011-03-18 22:11 ` [RFC 1/4] sdhci: allow for multiple delays when sending commands Luis R. Rodriguez
2011-03-18 23:10 ` Chris Ball
2011-03-18 23:52 ` Luis R. Rodriguez
2011-03-18 22:11 ` [RFC 2/4] sdhci: sanity check for triggering interrupts thread Luis R. Rodriguez
2011-03-18 22:11 ` [RFC 3/4] sdhci: cache when the MMC bus width is 4 bits wide Luis R. Rodriguez
2011-03-18 22:12 ` [RFC 4/4] sdhci: add quick for controllers with for CIRQ issues Luis R. Rodriguez
2011-03-18 22:29 ` [RFC 0/4] sdhci: few patches for ENE 712 support Luis R. Rodriguez
2011-03-19 9:15 ` Wolfram Sang [this message]
2011-03-30 1:16 ` Luis R. Rodriguez
2011-03-30 7:47 ` Wolfram Sang
2011-08-24 11:02 ` Kalle Valo
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=20110319091544.GA16635@pengutronix.de \
--to=w.sang@pengutronix.de \
--cc=cjb@laptop.org \
--cc=j@w1.fi \
--cc=kvalo@adurom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=lrodriguez@atheros.com \
--cc=naveen.singh@atheros.com \
--cc=vmehta@atheros.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).