From: Wolfram Sang <w.sang@pengutronix.de>
To: Kyungmin Park <kmpark@infradead.org>
Cc: linux-mmc@vger.kernel.org, pierre-list@ossman.eu,
gdavis@mvista.com, cbouatmailru@gmail.com,
m.szyprowski@samsung.com, akpm@linux-foundation.org,
정재훈 <jh80.chung@samsung.com>, "Alan Cox" <alan@linux.intel.com>
Subject: cleaning up sdhci? (was Re: [RFC] thoughts about recent Samsung related patches)
Date: Tue, 14 Sep 2010 12:28:59 +0200 [thread overview]
Message-ID: <20100914102858.GB2629@pengutronix.de> (raw)
In-Reply-To: <AANLkTi=zpAz+0VT0GGGrMP3KOJiWqvypWVfxuDZDpoSx@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1998 bytes --]
On Tue, Sep 14, 2010 at 09:05:30AM +0900, Kyungmin Park wrote:
> On Mon, Sep 13, 2010 at 9:31 PM, Wolfram Sang <w.sang@pengutronix.de> wrote:
> >> > I hope my comments are applicable; because there is no freely available
> >> > datasheet, I can't verify all of my assumptions. Looking forward to
> >> > comments.
> >> Good, I think it's possible. I'll try and send a patch.
> >
> > Any news on this ?
>
> I tried and no problem to work, but I'm thinking does it really
> required for reducing one quirk?
> With this change sdhci-s3c should use the
> CONFIG_MMC_SDHCI_IO_ACCESSORS and it introduces the io functions for
> every io access.
>
> So I'm not sure these change is required for s3c sdhci.
>
> Give you opinions.
I know what you mean. Still, I'd prefer to see that sdhci.c implements
stuff as generic as possible and trying to follow the standard closely.
Exceptions to that should be handled elsewhere if possible. That is, if
some implementations of a controller do not adhere to that standard and
change some bits in the register layout, well, then they have to live
with the quirks and their performance issues IMHO.
BTW it is not only the HI_SPD issue, which is a candidate for the io-
accessors. I am also interested to get the 8BITBUS patch reverted. It
breaks some SD cards on some boards using the esdhc controller :(
Support for a 8bit-bus needs a bit more thought, it seems...
Seeing Alan's patchset, it seems to be a good time to do some
sdhci-cleanup. My impression is that we could get generalize a few
quirks by using io-accessors and overriding capabilties-flags. I am open
for other opinions, though. All in all, it would be great if we all
could combine our efforts and get some kind of master-plan :)
Will take a look at Alan's patches now...
Regards,
Wolfram
--
Pengutronix e.K. | Wolfram Sang |
Industrial Linux Solutions | http://www.pengutronix.de/ |
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-09-14 10:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-06 11:00 [RFC] thoughts about recent Samsung related patches Wolfram Sang
2010-09-06 11:16 ` Kyungmin Park
2010-09-06 12:05 ` Wolfram Sang
2010-09-13 12:31 ` Wolfram Sang
2010-09-14 0:05 ` Kyungmin Park
2010-09-14 10:28 ` Wolfram Sang [this message]
2010-09-14 10:21 ` cleaning up sdhci? (was Re: [RFC] thoughts about recent Samsung related patches) Alan Cox
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=20100914102858.GB2629@pengutronix.de \
--to=w.sang@pengutronix.de \
--cc=akpm@linux-foundation.org \
--cc=alan@linux.intel.com \
--cc=cbouatmailru@gmail.com \
--cc=gdavis@mvista.com \
--cc=jh80.chung@samsung.com \
--cc=kmpark@infradead.org \
--cc=linux-mmc@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=pierre-list@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