From: aneesh@ti.com (Aneesh V)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 3/8] misc: emif: add register definitions for EMIF
Date: Thu, 09 Feb 2012 19:50:30 +0530 [thread overview]
Message-ID: <4F33D62E.8070403@ti.com> (raw)
In-Reply-To: <B5906170F1614E41A8A28DE3B8D121433179B3F3@DBDE01.ent.ti.com>
On Thursday 09 February 2012 04:55 PM, Bedia, Vaibhav wrote:
>> -----Original Message-----
>> From: linux-omap-owner at vger.kernel.org [mailto:linux-omap-owner at vger.kernel.org] On Behalf Of V, Aneesh
>> Sent: Saturday, February 04, 2012 5:46 PM
>> To: linux-omap at vger.kernel.org
>> Cc: linux-kernel at vger.kernel.org; akpm at linux-foundation.org; V, Aneesh
>> Subject: [RFC PATCH 3/8] misc: emif: add register definitions for EMIF
>>
>
> Sorry for the delayed response. Can these register definitions be put in a place
> where the code from the arch/arm/mach-omap2/* can also access it?
I don't have any issues with it as long as everybody is in agreement.
>
> Devices like AM335x and TI814x will need to reconfigure the EMIF when coming out
> of low power states and putting these register definitions in a common place
> will help us avoid some code duplication.
Can you elaborate on that. Does EMIF lose its settings in low-power
mode? If so, are you going to do the re-initialization from internal
RAM or something? For us EMIF doesn't lose its state in low power modes.
br,
Aneesh
next prev parent reply other threads:[~2012-02-09 14:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <331ABD5ECB02734CA317220B2BBEABC1317897B8@DBDE01.ent.ti.com>
2012-02-09 11:25 ` [RFC PATCH 3/8] misc: emif: add register definitions for EMIF Bedia, Vaibhav
2012-02-09 14:20 ` Aneesh V [this message]
2012-02-09 14:44 ` Bedia, Vaibhav
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=4F33D62E.8070403@ti.com \
--to=aneesh@ti.com \
--cc=linux-arm-kernel@lists.infradead.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