From: David Brownell <david-b@pacbell.net>
To: Purushotam Kumar <purushotam@ti.com>
Cc: davinci-linux-open-source@linux.davincidsp.com,
linux-kernel@vger.kernel.org, drzeus-mmc@drzeus.cx
Subject: Re: [PATCH 1/1] DaVinci: MMC: MMC/SD controller driver for DaVinci/DM6446.
Date: Mon, 16 Mar 2009 11:40:00 -0700 [thread overview]
Message-ID: <200903161140.01121.david-b@pacbell.net> (raw)
In-Reply-To: <1237214559-31345-1-git-send-email-purushotam@ti.com>
On Monday 16 March 2009, Purushotam Kumar wrote:
> From: Purshotam Kumar <purushotam@ti.com>
>
> This patch adds support for DaVinci (DM6446) MMC/SD controller driver. This
The dm6446 is the only chip with current mainline support;
but dm355 can use it too, "support on the way" to mainline.
(Only for 2.6.30 if Kevin still has time...)
And there are other DaVinci chips that support MMC too ...
some are compatible with those two chips, some not, all
should use a version of this driver. (And OMAP-L137 too,
same tech family but with a different marketing label.)
So I'd remove the implication that DaVinci == DM6446, or
that this driver is specific to that SoC.
> @@ -171,6 +171,14 @@ config MMC_TIFM_SD
> To compile this driver as a module, choose M here: the
> module will be called tifm_sd.
>
> +config MMC_DAVINCI
> + tristate "TI DAVINCI Multimedia Card Interface support"
> + depends on MMC
Everything in that menu depends on MMC. This should
depend on ARCH_DAVINCI instead. :)
> + host->clk = clk_get(&pdev->dev, NULL);
The NULL won't work with the clock code currently
included in mainline ... "MMCSDCLK" will though.
It's probably simplest to list the updated DaVinci
clock framework code as a runtime dependency, much
like EDMA support is a build-time one, for this patch.
> + if (pdata->max_freq)
> + mmc->f_max = pdata->max_freq;
> + if (pdata->caps)
> + mmc->caps |= pdata->caps;
A build-time issue is that "struct davinci_mmc_config"
is missing. You could update this patch to include
"arch/arm/mach-davinci/include/mach/mmc.h" too.
- Dave
next prev parent reply other threads:[~2009-03-16 18:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-16 14:42 Purushotam Kumar
2009-03-16 18:14 ` Trilok Soni
2009-03-17 10:14 ` Kumar, Purushotam
2009-03-16 18:40 ` David Brownell [this message]
2009-03-17 7:25 ` Kumar, Purushotam
2009-03-16 21:08 ` David Brownell
2009-03-17 7:30 ` Kumar, Purushotam
2009-03-22 15:12 ` Pierre Ossman
2009-03-26 8:58 ` Kumar, Purushotam
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=200903161140.01121.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=davinci-linux-open-source@linux.davincidsp.com \
--cc=drzeus-mmc@drzeus.cx \
--cc=linux-kernel@vger.kernel.org \
--cc=purushotam@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
all inboxes | Powered by JetHome®