From: Wolfram Sang <w.sang@pengutronix.de>
To: Chris Ball <cjb@laptop.org>
Cc: linux-mmc@vger.kernel.org,
Anton Vorontsov <cbouatmailru@gmail.com>,
Olof Johansson <olof@lixom.net>,
Philip Rakity <prakity@marvell.com>
Subject: Re: [PATCH 2/2] mmc: sdhci: Replace SDHCI_QUIRK_NO_MULTIBLOCK with a platform hook.
Date: Sun, 13 Feb 2011 22:13:12 +0100 [thread overview]
Message-ID: <20110213211312.GA27028@pengutronix.de> (raw)
In-Reply-To: <20110212210541.GA11634@void.printf.net>
On Sat, Feb 12, 2011 at 09:05:41PM +0000, Chris Ball wrote:
> > > If there still isn't a better alternative in mind, I'm thinking about
> > > going ahead and taking this patch, and then reusing the quirk bit for
> > > Chuanxiao's "mmc: set a suitable max_discard_sectors value for HC"
> > > patchset.
> >
> > What about using the SZ_2048 quirk instead which could be done via
> > io-accessors?
>
> That sounds fine too; I thought this one was more straightforward.
>
> > That being said, I have a train travel tomorrow and will try to
> > see if a fixup() function would make sense for this one. Can you
> > wait one more day?
>
> Sure, no immediate hurry. Thanks!
So, I had a look today: Hmm....
I wanted something like a fixup-function called at the end of sdhci_add_host
which could handle all quirks doing some "mmc->..." changes. (I know that Olof
doesn't like this because it breaks abstraction. There might be a middle-way,
though.)
What bugs me with that approach is that it won't help against all quirks, so we
would need to replace all other quirks with functions, too. I'd think a
combination of QUIRKS and a fixup-function will be too confusing (we have that
to some degree already). Changing all at once is a major task though if you
want to group them properly and not do a 1:1 mapping.
I'd like to hear other people's opinion at this point. For now, my suggestion
would be to remove those quirks which could be handled via io-accessors. That
could be done on a step by step basis and should not create confusion if all
registers flaws are handled via io-accessors. But that's just my brainstorming,
so looking forward to comments.
Regards,
Wolfram
--
Pengutronix e.K. | Wolfram Sang |
Industrial Linux Solutions | http://www.pengutronix.de/ |
next prev parent reply other threads:[~2011-02-13 21:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-06 6:13 [PATCH 2/2] mmc: sdhci: Replace SDHCI_QUIRK_NO_MULTIBLOCK with a platform hook Chris Ball
2011-02-07 17:48 ` Wolfram Sang
2011-02-12 20:22 ` Chris Ball
2011-02-12 20:43 ` Wolfram Sang
2011-02-12 21:05 ` Chris Ball
2011-02-13 21:13 ` Wolfram Sang [this message]
2011-05-29 2:28 ` Chris Ball
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=20110213211312.GA27028@pengutronix.de \
--to=w.sang@pengutronix.de \
--cc=cbouatmailru@gmail.com \
--cc=cjb@laptop.org \
--cc=linux-mmc@vger.kernel.org \
--cc=olof@lixom.net \
--cc=prakity@marvell.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).