LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Jaehoon Chung <jh80.chung@samsung.com>
To: Will Newton <will.newton@gmail.com>
Cc: Jaehoon Chung <jh80.chung@samsung.com>,
Chris Ball <cjb@laptop.org>,
Linux Kernel list <linux-kernel@vger.kernel.org>,
linux-mmc@vger.kernel.org, Matt Fleming <matt@console-pimps.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v4] dw_mmc: Add Synopsys DesignWare mmc host driver.
Date: Tue, 08 Feb 2011 19:49:11 +0900 [thread overview]
Message-ID: <4D511FA7.4040207@samsung.com> (raw)
In-Reply-To: <AANLkTikTxjbkA9d9WjVNm9bC3bPLQDndwSXCxp3jOLKS@mail.gmail.com>
Hi Will
I'm probing dw_mmc on Samsung SoC...
So i have some board specific data..
But i didn't want to add board specific data in dw_mmc.c
I want to use get_cd()/get_wd()/init()...So i asked to you..:)
If i need not the data information, i will not append them..
you're right, maybe "struct dw_mci" need not..(just example)
And i think that need card_detect irq-handler function..if we use pdata->init..isn't? :)
In future, if i need your help, can i ask to you?
Onemore...Did you test the dw_mmc..?
If you can answer, i want to know the performance..
Will Newton wrote:
> On Tue, Feb 8, 2011 at 6:38 AM, Jaehoon Chung <jh80.chung@samsung.com> wrote:
>> Hi Will..
>>
>> I need your help for your code..
>>
>> In dw_mmc.h, exist some function pointer..
>>
>> int *get_ro(u32 slot_id);
>> int *get_cd(u32 slot_id);
>> ...
>>
>> Just only need slot_id??
>> If i need the "struct dw_mci", could i append the parameter?
>
> Yes, that should be possible. However I would like to reduce the
> number of places the whole struct dw_mci
> is passed around if possible, as the whole struct is usually not
> needed and it exposes some driver internals.
>
> Which part of struct dw_mci do you need in the callback?
> --
> To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2011-02-08 10:49 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-06 15:53 [RESEND PATCH] " Will Newton
2010-12-08 11:55 ` Matt Fleming
2010-12-08 13:14 ` Will Newton
2010-12-08 14:21 ` [PATCH] " Will Newton
2010-12-08 16:07 ` Matt Fleming
2010-12-09 6:47 ` Chris Ball
2010-12-09 12:11 ` Will Newton
2010-12-09 16:01 ` Chris Ball
2010-12-09 17:24 ` Will Newton
[not found] ` <20101211192320.GA24430@void.printf.net>
2010-12-12 8:41 ` Russell King - ARM Linux
2010-12-12 11:15 ` Russell King - ARM Linux
2010-12-12 10:57 ` Will Newton
2010-12-12 13:52 ` Chris Ball
2010-12-12 14:03 ` Will Newton
2010-12-12 14:11 ` Russell King - ARM Linux
2010-12-12 14:31 ` Will Newton
2010-12-12 14:47 ` Russell King - ARM Linux
2010-12-12 15:17 ` Will Newton
2010-12-16 17:04 ` [PATCH v4] " Will Newton
2011-01-02 6:20 ` Chris Ball
2011-01-18 7:54 ` Jaehoon Chung
2011-01-18 10:21 ` Will Newton
2011-02-08 6:38 ` Jaehoon Chung
2011-02-08 10:29 ` Will Newton
2011-02-08 10:49 ` Jaehoon Chung [this message]
2011-02-08 12:06 ` Will Newton
2010-12-09 17:35 ` [PATCH] " Chris Ball
2010-12-09 17:46 ` Will Newton
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=4D511FA7.4040207@samsung.com \
--to=jh80.chung@samsung.com \
--cc=cjb@laptop.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=matt@console-pimps.org \
--cc=will.newton@gmail.com \
--subject='Re: [PATCH v4] dw_mmc: Add Synopsys DesignWare mmc host driver.' \
/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
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).