All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Hiroshi Doyu <hdoyu@nvidia.com>
Cc: Stephen Warren <swarren@wwwdotorg.org>,
	Russell King <linux@arm.linux.org.uk>,
	Olof Johansson <olof@lixom.net>,
	"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	Colin Cross <ccross@android.com>,
	Grant Likely <grant.likely@secretlab.ca>,
	Rob Herring <rob.herring@calxeda.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"devicetree-discuss@lists.ozlabs.org"
	<devicetree-discuss@lists.ozlabs.org>
Subject: Re: [PATCH 1/1] ARM: tegra: Add Tegra Memory Controller(MC) driver
Date: Fri, 4 May 2012 08:41:38 +0000	[thread overview]
Message-ID: <201205040841.39351.arnd@arndb.de> (raw)
In-Reply-To: <20120504083424.0f394a6db8e95763e59ae2a0@nvidia.com>

On Friday 04 May 2012, Hiroshi Doyu wrote:
> > Since tegra has a custom memory controller it's not as obvious that it
> > needs to go in a shared location, indeed. But it's easier to use the
> > same practices across platforms, and if there are other vendors that
> > end up sharing IP blocks for memory down the road, having them in a
> > common location makes sense.
> 
> I think that the above TI's patch is:
> 
>   Add TI EMIF SDRAM controller driver
>     http://lwn.net/Articles/494922/
> 
> I'm moving this Tegra MC driver under drivers/memory, "tegra{20,30}-mc.c".

Ok, very good!

	Arnd

WARNING: multiple messages have this Message-ID (diff)
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/1] ARM: tegra: Add Tegra Memory Controller(MC) driver
Date: Fri, 4 May 2012 08:41:38 +0000	[thread overview]
Message-ID: <201205040841.39351.arnd@arndb.de> (raw)
In-Reply-To: <20120504083424.0f394a6db8e95763e59ae2a0@nvidia.com>

On Friday 04 May 2012, Hiroshi Doyu wrote:
> > Since tegra has a custom memory controller it's not as obvious that it
> > needs to go in a shared location, indeed. But it's easier to use the
> > same practices across platforms, and if there are other vendors that
> > end up sharing IP blocks for memory down the road, having them in a
> > common location makes sense.
> 
> I think that the above TI's patch is:
> 
>   Add TI EMIF SDRAM controller driver
>     http://lwn.net/Articles/494922/
> 
> I'm moving this Tegra MC driver under drivers/memory, "tegra{20,30}-mc.c".

Ok, very good!

	Arnd

  reply	other threads:[~2012-05-04  8:41 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-03 16:51 [PATCH 1/1] ARM: tegra: Add Tegra Memory Controller(MC) driver Hiroshi DOYU
2012-05-03 16:51 ` Hiroshi DOYU
2012-05-03 16:51 ` Hiroshi DOYU
     [not found] ` <1336063897-12083-1-git-send-email-hdoyu-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-05-03 18:39   ` Stephen Warren
2012-05-03 18:39     ` Stephen Warren
2012-05-03 18:39     ` Stephen Warren
2012-05-03 20:13     ` Olof Johansson
2012-05-03 20:13       ` Olof Johansson
     [not found]       ` <CAOesGMivxdDhkEoZh=LuvtKRPfgXi=8X4chEL-cJazjgeo_ONA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-05-04  5:34         ` Hiroshi Doyu
2012-05-04  5:34           ` Hiroshi Doyu
2012-05-04  5:34           ` Hiroshi Doyu
2012-05-04  8:41           ` Arnd Bergmann [this message]
2012-05-04  8:41             ` Arnd Bergmann
     [not found]     ` <4FA2D0C4.4020608-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2012-05-03 19:48       ` Alan Cox
2012-05-03 19:48         ` Alan Cox
2012-05-03 19:48         ` Alan Cox
2012-05-04 13:00       ` Hiroshi Doyu
2012-05-04 13:00         ` Hiroshi Doyu
2012-05-04 13:00         ` Hiroshi Doyu
     [not found]         ` <20120504.160035.1828735037330038337.hdoyu-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-05-04 16:53           ` Stephen Warren
2012-05-04 16:53             ` Stephen Warren
2012-05-04 16:53             ` Stephen Warren

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=201205040841.39351.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=ccross@android.com \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=grant.likely@secretlab.ca \
    --cc=hdoyu@nvidia.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=olof@lixom.net \
    --cc=rob.herring@calxeda.com \
    --cc=swarren@wwwdotorg.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.