From: Mike Rapoport <mike@compulab.co.il>
To: Saeed Bishara <saeed@marvell.com>
Cc: "linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] MMC: add support for the Marvell platform SDHCI controller
Date: Wed, 27 Oct 2010 11:17:27 +0200 [thread overview]
Message-ID: <4CC7EE27.4030704@compulab.co.il> (raw)
In-Reply-To: <FCBE654890C0334289D0AD3AF4EF009FE1475AA356@IL-MB01.marvell.com>
On 10/27/10 10:46, Saeed Bishara wrote:
>
>
>> +config MMC_SDHCI_MV
>> + bool "SDHCI support on Marvell's SoC"
>> + depends on MMC_SDHCI
>> + depends on MMC_SDHCI_PLTFM
>> + select MMC_SDHCI_IO_ACCESSORS
>> + help
>> + This selects the Secure Digital Host Controller Interface in
>> + Marvell's SoC controllers.
>> +
>> + If you have a controller with this interface, say Y or M here.
>> +
>> + If unsure, say N.
>> +
> Mike, the config name and description is too generic as there are several sdhci
> controllers on Marvell devices (see like pxa), I suggest to name it SDHCI_DOVE
> and make it depends on ARCH_DOVE and modify the description accordingly.
No problem. That said, no ARCH_MPP for now, like it was in [1]?
[1] http://marc.info/?l=linux-kernel&m=128458441031769&q=raw
>> +#include <linux/clk.h>
>> +#include <linux/delay.h>
>> +#include <linux/err.h>
>> +#include <linux/platform_device.h>
>> +#include <linux/io.h>
>> +#include <linux/mmc/host.h>
>> +#include "sdhci.h"
>> +#include "sdhci-pltfm.h"
> are those includes are realy needed? At least the delay.h and clk.h not needed for now.
>
> saeed
--
Sincerely yours,
Mike.
WARNING: multiple messages have this Message-ID (diff)
From: mike@compulab.co.il (Mike Rapoport)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] MMC: add support for the Marvell platform SDHCI controller
Date: Wed, 27 Oct 2010 11:17:27 +0200 [thread overview]
Message-ID: <4CC7EE27.4030704@compulab.co.il> (raw)
In-Reply-To: <FCBE654890C0334289D0AD3AF4EF009FE1475AA356@IL-MB01.marvell.com>
On 10/27/10 10:46, Saeed Bishara wrote:
>
>
>> +config MMC_SDHCI_MV
>> + bool "SDHCI support on Marvell's SoC"
>> + depends on MMC_SDHCI
>> + depends on MMC_SDHCI_PLTFM
>> + select MMC_SDHCI_IO_ACCESSORS
>> + help
>> + This selects the Secure Digital Host Controller Interface in
>> + Marvell's SoC controllers.
>> +
>> + If you have a controller with this interface, say Y or M here.
>> +
>> + If unsure, say N.
>> +
> Mike, the config name and description is too generic as there are several sdhci
> controllers on Marvell devices (see like pxa), I suggest to name it SDHCI_DOVE
> and make it depends on ARCH_DOVE and modify the description accordingly.
No problem. That said, no ARCH_MPP for now, like it was in [1]?
[1] http://marc.info/?l=linux-kernel&m=128458441031769&q=raw
>> +#include <linux/clk.h>
>> +#include <linux/delay.h>
>> +#include <linux/err.h>
>> +#include <linux/platform_device.h>
>> +#include <linux/io.h>
>> +#include <linux/mmc/host.h>
>> +#include "sdhci.h"
>> +#include "sdhci-pltfm.h"
> are those includes are realy needed? At least the delay.h and clk.h not needed for now.
>
> saeed
--
Sincerely yours,
Mike.
next prev parent reply other threads:[~2010-10-27 9:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-27 8:07 [PATCH] MMC: add support for the Marvell platform SDHCI controller Mike Rapoport
2010-10-27 8:07 ` Mike Rapoport
2010-10-27 8:46 ` Saeed Bishara
2010-10-27 8:46 ` Saeed Bishara
2010-10-27 9:17 ` Mike Rapoport [this message]
2010-10-27 9:17 ` Mike Rapoport
2010-10-27 9:10 ` Chris Ball
2010-10-27 9:10 ` Chris Ball
-- strict thread matches above, loose matches on Subject: below --
2010-06-22 14:09 Saeed Bishara
2010-06-23 11:52 ` Matt Fleming
2010-06-23 12:11 ` saeed bishara
2010-06-23 14:06 ` Matt Fleming
2010-08-25 22:39 ` Matt Fleming
2010-08-25 23:16 ` Andrew Morton
2010-09-10 20:16 ` Chris Ball
2010-05-04 16:24 Saeed Bishara
2010-05-05 13:39 ` saeed bishara
2010-05-25 7:21 ` saeed bishara
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=4CC7EE27.4030704@compulab.co.il \
--to=mike@compulab.co.il \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mmc@vger.kernel.org \
--cc=saeed@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.