devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Aneesh V <aneesh@ti.com>
To: Olof Johansson <olof@lixom.net>
Cc: "Cousson, Benoit" <b-cousson@ti.com>,
	Tony Lindgren <tony@atomide.com>,
	Rob Herring <robherring2@gmail.com>,
	devicetree-discuss@lists.ozlabs.org, linux-omap@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	Vishwanath Sripathy <vishwanath.bs@ti.com>,
	Mike Turquette <mturquette@ti.com>,
	grant.likely@secretlab.ca
Subject: Re: [RFC v2 PATCH 0/3] dt: device tree bindings and data for EMIF and DDR
Date: Tue, 17 Jan 2012 17:36:16 +0530	[thread overview]
Message-ID: <4F156438.20502@ti.com> (raw)
In-Reply-To: <4F1087C9.6030908@ti.com>

Hi Olof,

On Saturday 14 January 2012 01:06 AM, Aneesh V wrote:
> Hi Olof,

<snip>

> We wish to drop the DDR3 support because we have concluded that our
> platforms with DDR3 memories will not scale DDR frequency due to
> limitations in DDR3 protocol(operating frequency can vary only in a
> small range). So, is it ok to persist with my bindings for LPDDR2
> (fixing the comments already given by you) and drop the DDR3 part
> from it?

Ping! Forgive my impatience, but I would like to close on this at the
earliest to continue my work on the driver.

thanks,
Aneesh

  parent reply	other threads:[~2012-01-17 12:06 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-19 14:05 [RFC v2 PATCH 0/3] dt: device tree bindings and data for EMIF and DDR Aneesh V
2011-12-19 14:05 ` [RFC v2 PATCH 1/3] dt: device tree bindings for DDR memories Aneesh V
2011-12-19 16:52   ` Olof Johansson
2011-12-20  7:09     ` Aneesh V
2012-01-19 12:18       ` Aneesh V
2011-12-19 14:05 ` [RFC v2 PATCH 2/3] dt: device tree bindings for TI's EMIF sdram controller Aneesh V
2011-12-19 16:56   ` Olof Johansson
2011-12-20  7:12     ` Aneesh V
2011-12-19 16:59   ` Olof Johansson
2011-12-20  7:19     ` Aneesh V
2011-12-19 14:05 ` [RFC v2 PATCH 3/3] arm/dts: EMIF and lpddr2 device tree data for OMAP4 boards Aneesh V
2011-12-19 23:01 ` [RFC v2 PATCH 0/3] dt: device tree bindings and data for EMIF and DDR Rob Herring
2011-12-19 23:35   ` Tony Lindgren
2011-12-20 10:44     ` Aneesh V
2011-12-20 12:40       ` Cousson, Benoit
2011-12-20 14:08         ` Aneesh V
2012-01-08 17:23           ` Aneesh V
2012-01-09  5:42             ` Olof Johansson
2012-01-13 19:36               ` Aneesh V
2012-01-16 19:15                 ` Turquette, Mike
2012-01-19 19:26                   ` Olof Johansson
2012-01-17 12:06                 ` Aneesh V [this message]
2011-12-20 10:16   ` Aneesh V
2012-01-19 14:28 ` Aneesh V
2012-01-19 14:31   ` Aneesh V
2012-01-19 14:28 ` [PATCH 1/3] dt: device tree bindings for DDR memories Aneesh V
2012-01-19 14:28 ` [PATCH 2/3] dt: device tree bindings for TI's EMIF sdram controller Aneesh V
2012-01-19 14:28 ` [PATCH 3/3] arm/dts: EMIF and lpddr2 device tree data for OMAP4 boards 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=4F156438.20502@ti.com \
    --to=aneesh@ti.com \
    --cc=b-cousson@ti.com \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=grant.likely@secretlab.ca \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=mturquette@ti.com \
    --cc=olof@lixom.net \
    --cc=robherring2@gmail.com \
    --cc=tony@atomide.com \
    --cc=vishwanath.bs@ti.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).