From: Aneesh V <aneesh@ti.com>
To: "Cousson, Benoit" <b-cousson@ti.com>
Cc: linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org
Subject: Re: [PATCH 1/8] OMAP4: hwmod: add EMIF hw mod data
Date: Thu, 08 Mar 2012 22:13:49 +0530 [thread overview]
Message-ID: <4F58E1C5.5090704@ti.com> (raw)
In-Reply-To: <4F58E13C.8040906@ti.com>
On Thursday 08 March 2012 10:11 PM, Cousson, Benoit wrote:
> Hi Aneesh
>
> On 3/8/2012 4:54 PM, Aneesh V wrote:
>> From: Benoit Cousson<b-cousson@ti.com>
>>
>> Add hwmod data for EMIF IP instances in OMAP4.
>
> Paul has just posted an OMAP4 hwmod series (ARM: OMAP4: hwmod data: add
> almost all remaining IP blocks) that does contain the EMIF hwmods, so
> assuming that you are not adding some custom dev_attr here, it should
> work for you.
Ok. I will test with that tomorrow and drop this patch.
Thanks,
Aneesh
next prev parent reply other threads:[~2012-03-08 16:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-08 15:54 [PATCH 0/8] Add TI EMIF SDRAM controller driver Aneesh V
2012-03-08 15:54 ` [PATCH 1/8] OMAP4: hwmod: add EMIF hw mod data Aneesh V
2012-03-08 16:41 ` Cousson, Benoit
2012-03-08 16:43 ` Aneesh V [this message]
2012-03-08 15:54 ` [PATCH 2/8] misc: ddr: add LPDDR2 data from JESD209-2 Aneesh V
2012-03-08 15:54 ` [PATCH 3/8] misc: emif: add register definitions for EMIF Aneesh V
2012-03-08 15:54 ` [PATCH 4/8] misc: emif: add basic infrastructure for EMIF driver Aneesh V
2012-03-08 15:54 ` [PATCH 5/8] misc: emif: handle frequency and voltage change events Aneesh V
2012-03-08 15:54 ` [PATCH 6/8] misc: emif: add interrupt and temperature handling Aneesh V
2012-03-08 15:54 ` [PATCH 7/8] misc: emif: add one-time settings Aneesh V
2012-03-08 15:54 ` [PATCH 8/8] misc: emif: add debugfs entries for emif Aneesh V
2012-03-08 20:59 ` [PATCH 0/8] Add TI EMIF SDRAM controller driver Greg KH
2012-03-08 21:47 ` Paul Walmsley
2012-03-09 3:59 ` Aneesh V
2012-03-12 15:58 ` Santosh Shilimkar
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=4F58E1C5.5090704@ti.com \
--to=aneesh@ti.com \
--cc=b-cousson@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
/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