From: Chris Ball <cjb@laptop.org>
To: Jaehoon Chung <jh80.chung@samsung.com>
Cc: "linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
Will Newton <will.newton@gmail.com>,
Kyungmin Park <kyungmin.park@samsung.com>
Subject: Re: [PATCH] dw_mmc: modify quirks bit-shift control
Date: Wed, 16 Feb 2011 19:42:32 +0000 [thread overview]
Message-ID: <20110216194232.GA17634@void.printf.net> (raw)
In-Reply-To: <4D5B6C70.2030809@samsung.com>
Hi,
On Wed, Feb 16, 2011 at 03:19:28PM +0900, Jaehoon Chung wrote:
> If we need some quirks, maybe add quirks in future
> But now, quirks value set to integer..later we should be confused..
> So i think that need bit-shift control.
>
> And If we need not any quirks, we didn't set anything..
> (Need not DW_MCI_QUIRK_NONE)
>
> Signed-off-by: Jaehoon Chung <jh80.chung@samsung.com>
> ---
> include/linux/mmc/dw_mmc.h | 8 +++-----
> 1 files changed, 3 insertions(+), 5 deletions(-)
>
> diff --git a/include/linux/mmc/dw_mmc.h b/include/linux/mmc/dw_mmc.h
> index 16b0261..8614832 100644
> --- a/include/linux/mmc/dw_mmc.h
> +++ b/include/linux/mmc/dw_mmc.h
> @@ -165,14 +165,12 @@ struct dw_mci_dma_ops {
> };
>
> /* IP Quirks/flags. */
> -/* No special quirks or flags to cater for */
> -#define DW_MCI_QUIRK_NONE 0
> /* DTO fix for command transmission with IDMAC configured */
> -#define DW_MCI_QUIRK_IDMAC_DTO 1
> +#define DW_MCI_QUIRK_IDMAC_DTO (1 << 0)
> /* delay needed between retries on some 2.11a implementations */
> -#define DW_MCI_QUIRK_RETRY_DELAY 2
> +#define DW_MCI_QUIRK_RETRY_DELAY (1 << 2)
> /* High Speed Capable - Supports HS cards (upto 50MHz) */
> -#define DW_MCI_QUIRK_HIGHSPEED 4
> +#define DW_MCI_QUIRK_HIGHSPEED (1 << 3)
>
Why skip (1 << 1)? (There's also BIT(0) -> BIT(2) if you prefer.)
Thanks,
--
Chris Ball <cjb@laptop.org> <http://printf.net/>
One Laptop Per Child
next prev parent reply other threads:[~2011-02-16 19:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-16 6:19 [PATCH] dw_mmc: modify quirks bit-shift control Jaehoon Chung
2011-02-16 9:58 ` Will Newton
2011-02-16 19:42 ` Chris Ball [this message]
2011-02-17 4:09 ` Jaehoon Chung
2011-02-17 4:13 ` Chris Ball
2011-02-17 10:05 ` Will Newton
2011-02-17 15:39 ` 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=20110216194232.GA17634@void.printf.net \
--to=cjb@laptop.org \
--cc=jh80.chung@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-mmc@vger.kernel.org \
--cc=will.newton@gmail.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