From: "Cousson, Benoit" <b-cousson@ti.com>
To: Kevin Hilman <khilman@deeprootsystems.com>
Cc: kishore kadiyala <kishorek.kadiyala@gmail.com>,
"Kadiyala, Kishore" <kishore.kadiyala@ti.com>,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"tony@atomide.com" <tony@atomide.com>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"Chikkature Rajashekar, Madhusudhan" <madhu.cr@ti.com>,
"adrian.hunter@nokia.com" <adrian.hunter@nokia.com>
Subject: Re: [PATCH 3/3] omap3/omap4 hsmmc: Register offset handling
Date: Fri, 03 Sep 2010 17:50:56 +0200 [thread overview]
Message-ID: <4C811960.9060801@ti.com> (raw)
In-Reply-To: <87eida4ysh.fsf@deeprootsystems.com>
On 9/3/2010 5:44 PM, Kevin Hilman wrote:
> kishore kadiyala<kishorek.kadiyala@gmail.com> writes:
>
>> Hi Benoit
>>
>> <snip>
>>
>>>> + while (!(omap_readl(base + reg_off)&
>>>> MMCHS_SYSSTATUS_RESETDONE))
>>>> cpu_relax();
>>>
>>> Why does that series not seems to be based on your hwmod migration? The
>>> reset is fully handle by the hwmod framework now.
>>
>> Agree. But Kevin has suggested to post this patch independent of hwmod.
>> Does this patch has to go in hwmod series ?
>
> I suggested that this register conversion patch could be merged before
> the hwmod conversion as it is independent of that.
OK, I missed that part. I was surprised because the hwmod series was
sent before that one.
Benoit
next prev parent reply other threads:[~2010-09-03 15:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-30 17:48 [PATCH 3/3] omap3/omap4 hsmmc: Register offset handling kishore kadiyala
2010-09-01 12:26 ` Adrian Hunter
2010-09-01 13:34 ` kishore kadiyala
2010-09-03 7:44 ` Cousson, Benoit
2010-09-03 8:21 ` kishore kadiyala
2010-09-03 15:44 ` Kevin Hilman
2010-09-03 15:50 ` Cousson, Benoit [this message]
2010-09-06 15:49 ` 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=4C811960.9060801@ti.com \
--to=b-cousson@ti.com \
--cc=adrian.hunter@nokia.com \
--cc=akpm@linux-foundation.org \
--cc=khilman@deeprootsystems.com \
--cc=kishore.kadiyala@ti.com \
--cc=kishorek.kadiyala@gmail.com \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=madhu.cr@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 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.