From: Tony Lindgren <tony@atomide.com>
To: Madhusudhan Chikkature <madhu.cr@ti.com>
Cc: David Brownell <david-b@pacbell.net>, linux-omap@vger.kernel.org
Subject: Re: [PATCH]Add 3430 SDP board level support for HSMMC2
Date: Tue, 16 Sep 2008 08:12:40 -0700 [thread overview]
Message-ID: <20080916151238.GA25885@atomide.com> (raw)
In-Reply-To: <009c01c917bb$322c7f70$LocalHost@wipultra1303>
* Madhusudhan Chikkature <madhu.cr@ti.com> [080915 22:15]:
>
> ----- Original Message -----
> From: "Tony Lindgren" <tony@atomide.com>
> To: "David Brownell" <david-b@pacbell.net>
> Cc: "Madhusudhan Chikkature" <madhu.cr@ti.com>; <linux-omap@vger.kernel.org>
> Sent: Thursday, September 11, 2008 5:29 AM
> Subject: Re: [PATCH]Add 3430 SDP board level support for HSMMC2
>
>
> >* David Brownell <david-b@pacbell.net> [080908 12:26]:
> >> On Wednesday 13 August 2008, Madhusudhan Chikkature wrote:
> >> > > A better way to do this would be to let the boards say exactly
> >> > > what the hardware configuration is, rather than requiring all
> >> > > OMAP3 boards to be set up exactly like the SDP...
> >> >
> >> > I think the initial version was written specific to SDP. Later
> >> > on it was changed to hsmmc.c and the platforms which required
> >> > simillar setup as SDP started using it.
> >>
> >> Right ...
> >>
> >>
> >> > Now, if support for a new board is required which is unlike SDP a
> >> > new file can still be added for that perticular board, right?
> >>
> >> Each board already gets a board-XYZ.c file. So the clean way
> >> to do this is to have that file set up its hsmmc config ... NOT
> >> to clone versions of hsmmc.c for each board!
> >
> > Madhu, are you planning to abstract hsmmc.c further so various boards
> > can use it?
> Tony, Sorry for the delayed response on this. What level of abstraction are we considering here?
> Are we looking at abstracting out the power stuff (T2 LDO stuff) like the way H4 MMC board file uses
> menelaus driver? What is expected?
Well board-*.c files need to pass information about which MMC
controllers are enabled. I'll have some patches soon that should clean
up the remaining MMC init issues, but does not solve this issue.
Basically board-*.c files need to pass something like
struct omap_mmc_platform_data **controllers, int nr_controllers
to hsmmc.c to init the right instances.
I'm in process of chaning omap2_init_mmc() so hsmmc_init will call
it with something like this:
static struct omap_mmc_platform_data *board_hsmmc_data[OMAP34XX_NR_MMC];
void __init hsmmc_init(void)
{
omap2_init_mmc(board_hsmmc_data, OMAP34XX_NR_MMC);
}
Need to test the patches a bit more before I can post them.
Regards,
Tony
prev parent reply other threads:[~2008-09-16 15:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-13 6:18 [PATCH]Add 3430 SDP board level support for HSMMC2 Madhusudhan Chikkature
2008-08-13 8:54 ` David Brownell
2008-08-13 9:27 ` Madhusudhan Chikkature
2008-09-08 19:26 ` David Brownell
2008-09-10 23:59 ` Tony Lindgren
2008-09-16 5:15 ` Madhusudhan Chikkature
2008-09-16 15:12 ` Tony Lindgren [this message]
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=20080916151238.GA25885@atomide.com \
--to=tony@atomide.com \
--cc=david-b@pacbell.net \
--cc=linux-omap@vger.kernel.org \
--cc=madhu.cr@ti.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