From: Aneesh V <aneesh@ti.com>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org
Subject: Re: [PATCH v4] misc: ddr: add LPDDR2 data from JESD209-2
Date: Sat, 17 Mar 2012 03:20:36 +0530 [thread overview]
Message-ID: <4F63B5AC.5080808@ti.com> (raw)
In-Reply-To: <20120316214334.GA24925@kroah.com>
On Saturday 17 March 2012 03:13 AM, Greg KH wrote:
> On Sat, Mar 17, 2012 at 02:20:07AM +0530, Aneesh V wrote:
>> add LPDDR2 data from the JEDEC spec JESD209-2. The data
>> includes:
>>
>> 1. Addressing information for LPDDR2 memories of different
>> densities and types(S2/S4)
>> 2. AC timing data.
>>
>> This data will useful for memory controller device drivers.
>> Right now this is used by the TI EMIF SDRAM controller
>> driver.
>>
>> Cc: Greg KH<greg@kroah.com>
>> Signed-off-by: Aneesh V<aneesh@ti.com>
>
> What happened to the other patches that depended on this one?
I was not sure what was the convention regarding re-submitting just one
patch in a series. I realize that you prefer having the whole series
again. I will send it shortly.
thanks,
Aneesh
WARNING: multiple messages have this Message-ID (diff)
From: aneesh@ti.com (Aneesh V)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4] misc: ddr: add LPDDR2 data from JESD209-2
Date: Sat, 17 Mar 2012 03:20:36 +0530 [thread overview]
Message-ID: <4F63B5AC.5080808@ti.com> (raw)
In-Reply-To: <20120316214334.GA24925@kroah.com>
On Saturday 17 March 2012 03:13 AM, Greg KH wrote:
> On Sat, Mar 17, 2012 at 02:20:07AM +0530, Aneesh V wrote:
>> add LPDDR2 data from the JEDEC spec JESD209-2. The data
>> includes:
>>
>> 1. Addressing information for LPDDR2 memories of different
>> densities and types(S2/S4)
>> 2. AC timing data.
>>
>> This data will useful for memory controller device drivers.
>> Right now this is used by the TI EMIF SDRAM controller
>> driver.
>>
>> Cc: Greg KH<greg@kroah.com>
>> Signed-off-by: Aneesh V<aneesh@ti.com>
>
> What happened to the other patches that depended on this one?
I was not sure what was the convention regarding re-submitting just one
patch in a series. I realize that you prefer having the whole series
again. I will send it shortly.
thanks,
Aneesh
next prev parent reply other threads:[~2012-03-16 21:50 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-15 18:17 [PATCH v2 0/7] Add TI EMIF SDRAM controller driver Aneesh V
2012-03-15 18:17 ` Aneesh V
2012-03-15 18:17 ` [PATCH v2 1/7] misc: ddr: add LPDDR2 data from JESD209-2 Aneesh V
2012-03-15 18:17 ` Aneesh V
2012-03-15 19:02 ` Greg KH
2012-03-15 19:02 ` Greg KH
2012-03-15 19:56 ` Aneesh V
2012-03-15 19:56 ` Aneesh V
2012-03-16 20:19 ` [PATCH v3] " Aneesh V
2012-03-16 20:19 ` Aneesh V
2012-03-16 20:50 ` [PATCH v4] " Aneesh V
2012-03-16 20:50 ` Aneesh V
2012-03-16 21:43 ` Greg KH
2012-03-16 21:43 ` Greg KH
2012-03-16 21:50 ` Aneesh V [this message]
2012-03-16 21:50 ` Aneesh V
2012-03-16 20:58 ` [PATCH v2 1/7] " Aneesh V
2012-03-16 20:58 ` Aneesh V
2012-03-16 20:58 ` Aneesh V
2012-03-16 21:33 ` Greg KH
2012-03-16 21:33 ` Greg KH
2012-03-16 21:53 ` Aneesh V
2012-03-16 21:53 ` Aneesh V
2012-03-15 18:17 ` [PATCH v2 2/7] misc: emif: add register definitions for EMIF Aneesh V
2012-03-15 18:17 ` Aneesh V
2012-03-15 18:17 ` Aneesh V
2012-03-15 18:17 ` [PATCH v2 3/7] misc: emif: add basic infrastructure for EMIF driver Aneesh V
2012-03-15 18:17 ` Aneesh V
2012-03-15 18:17 ` [PATCH v2 4/7] misc: emif: handle frequency and voltage change events Aneesh V
2012-03-15 18:17 ` Aneesh V
2012-03-15 18:17 ` [PATCH v2 5/7] misc: emif: add interrupt and temperature handling Aneesh V
2012-03-15 18:17 ` Aneesh V
2012-03-15 18:17 ` [PATCH v2 6/7] misc: emif: add one-time settings Aneesh V
2012-03-15 18:17 ` Aneesh V
2012-03-15 18:17 ` [PATCH v2 7/7] misc: emif: add debugfs entries for emif Aneesh V
2012-03-15 18:17 ` Aneesh V
2012-03-15 19:04 ` [PATCH v2 0/7] Add TI EMIF SDRAM controller driver Greg KH
2012-03-15 19:04 ` Greg KH
2012-03-15 20:01 ` Aneesh V
2012-03-15 20:01 ` Aneesh V
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=4F63B5AC.5080808@ti.com \
--to=aneesh@ti.com \
--cc=greg@kroah.com \
--cc=linux-arm-kernel@lists.infradead.org \
--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 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.