From: kishore kadiyala <kishorek.kadiyala@gmail.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: kishore kadiyala <kishore.kadiyala@ti.com>,
linux-mmc@vger.kernel.org, linux-omap@vger.kernel.org,
madhu.cr@ti.com, jarkko.lavinen@nokia.com, tony@atomide.com,
rmk+lkml@arm.linux.org.uk, santosh.shilimkar@ti.com
Subject: Re: [PATCH 5/7] OMAP4-HSMMC: Adds Dummy Interface clock's for MMC controllers
Date: Thu, 22 Apr 2010 09:41:54 +0530 [thread overview]
Message-ID: <m2j7f9d1ffb1004212111pc6fbe8d7p36d81f06cc6c8dea@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1004211912540.24256@utopia.booyaka.com>
On Thu, Apr 22, 2010 at 6:44 AM, Paul Walmsley <paul@pwsan.com> wrote:
> Kishore,
>
> On Wed, 21 Apr 2010, kishore kadiyala wrote:
>
>> This patch adds dummy Interface clocks for MMC controllers
>
> Um, your patch removes the existing dummy interface clocks and adds them
> back again. Or is there some other point?
My bad , will repost in New series.
Regards,
Kishore
>
>> Signed-off-by: Kishore Kadiyala <kishore.kadiyala@ti.com>
>> ---
>> arch/arm/mach-omap2/clock44xx_data.c | 10 +++++-----
>> 1 files changed, 5 insertions(+), 5 deletions(-)
>>
>> diff --git a/arch/arm/mach-omap2/clock44xx_data.c b/arch/arm/mach-omap2/clock44xx_data.c
>> index 1dd7dc8..6177a89 100644
>> --- a/arch/arm/mach-omap2/clock44xx_data.c
>> +++ b/arch/arm/mach-omap2/clock44xx_data.c
>> @@ -2675,11 +2675,11 @@ static struct omap_clk omap44xx_clks[] = {
>> CLK("omap-mcspi.2", "ick", &dummy_ck, CK_443X),
>> CLK("omap-mcspi.3", "ick", &dummy_ck, CK_443X),
>> CLK("omap-mcspi.4", "ick", &dummy_ck, CK_443X),
>> - CLK("mmci-omap-hs.0", "ick", &dummy_ck, CK_443X),
>> - CLK("mmci-omap-hs.1", "ick", &dummy_ck, CK_443X),
>> - CLK("mmci-omap-hs.2", "ick", &dummy_ck, CK_443X),
>> - CLK("mmci-omap-hs.3", "ick", &dummy_ck, CK_443X),
>> - CLK("mmci-omap-hs.4", "ick", &dummy_ck, CK_443X),
>> + CLK("mmci-omap-hs.0", "ick", &dummy_ck, CK_443X),
>> + CLK("mmci-omap-hs.1", "ick", &dummy_ck, CK_443X),
>> + CLK("mmci-omap-hs.2", "ick", &dummy_ck, CK_443X),
>> + CLK("mmci-omap-hs.3", "ick", &dummy_ck, CK_443X),
>> + CLK("mmci-omap-hs.4", "ick", &dummy_ck, CK_443X),
>> CLK(NULL, "uart1_ick", &dummy_ck, CK_443X),
>> CLK(NULL, "uart2_ick", &dummy_ck, CK_443X),
>> CLK(NULL, "uart3_ick", &dummy_ck, CK_443X),
>> --
>> 1.6.3.3
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
>
>
> - Paul
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" 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:[~2010-04-22 4:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-21 18:20 [PATCH 5/7] OMAP4-HSMMC: Adds Dummy Interface clock's for MMC controllers kishore kadiyala
2010-04-22 1:14 ` Paul Walmsley
2010-04-22 4:11 ` kishore kadiyala [this message]
2010-04-22 6:39 ` Russell King
2010-05-04 6:21 ` kishore kadiyala
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=m2j7f9d1ffb1004212111pc6fbe8d7p36d81f06cc6c8dea@mail.gmail.com \
--to=kishorek.kadiyala@gmail.com \
--cc=jarkko.lavinen@nokia.com \
--cc=kishore.kadiyala@ti.com \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=madhu.cr@ti.com \
--cc=paul@pwsan.com \
--cc=rmk+lkml@arm.linux.org.uk \
--cc=santosh.shilimkar@ti.com \
--cc=tony@atomide.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;
as well as URLs for NNTP newsgroup(s).