From: Greg KH <greg@kroah.com>
To: "Mohammed, Afzal" <afzal@ti.com>
Cc: "Shilimkar, Santosh" <santosh.shilimkar@ti.com>,
Paul Walmsley <paul@pwsan.com>, "V, Aneesh" <aneesh@ti.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"mgreer@animalcreek.com" <mgreer@animalcreek.com>,
"msalter@redhat.com" <msalter@redhat.com>
Subject: Re: [PATCH v4 0/7] Add TI EMIF SDRAM controller driver
Date: Thu, 12 Apr 2012 07:10:50 -0700 [thread overview]
Message-ID: <20120412141050.GA31968@kroah.com> (raw)
In-Reply-To: <C8443D0743D26F4388EA172BF4E2A7A93E95947E@DQHE04.ent.ti.com>
On Thu, Apr 12, 2012 at 01:34:15PM +0000, Mohammed, Afzal wrote:
> Hi Greg,
>
> On Thu, Apr 12, 2012 at 18:40:45, Greg KH wrote:
> > On Thu, Apr 12, 2012 at 12:17:49PM +0530, Santosh Shilimkar wrote:
> > > I was hoping that we will have some thing like drivers/memory/*
> > > but since it doesn't exist, we used drivers/misc.
> >
> > Why not create it? I have no objection to that, it makes it more
> > obvious as to what this really is.
>
> There is another memory controller used in a few TI SoCs,
> namely GPMC [1], do you prefer having it too there.
Sure, why not?
> As of now it is not a driver, platform code handles GPMC, a patch
> series for converting it into a driver (but still residing in
> platform folder) was sent a few days back [2,3].
People are moving things out of the platform folder, so drivers/memory
makes sense.
thanks,
greg k-h
next prev parent reply other threads:[~2012-04-12 14:10 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-16 21:51 [PATCH v4 0/7] Add TI EMIF SDRAM controller driver Aneesh V
2012-03-16 21:51 ` [PATCH v4 1/7] misc: ddr: add LPDDR2 data from JESD209-2 Aneesh V
2012-03-16 21:51 ` [PATCH v4 2/7] misc: emif: add register definitions for EMIF Aneesh V
2012-03-16 21:51 ` [PATCH v4 3/7] misc: emif: add basic infrastructure for EMIF driver Aneesh V
2012-03-16 21:51 ` [PATCH v4 4/7] misc: emif: handle frequency and voltage change events Aneesh V
2012-03-16 21:51 ` [PATCH v4 5/7] misc: emif: add interrupt and temperature handling Aneesh V
2012-03-16 21:51 ` [PATCH v4 6/7] misc: emif: add one-time settings Aneesh V
2012-03-16 21:51 ` [PATCH v4 7/7] misc: emif: add debugfs entries for emif Aneesh V
2012-03-17 6:10 ` [PATCH v4 0/7] Add TI EMIF SDRAM controller driver Kyungmin Park
2012-04-12 2:44 ` Paul Walmsley
2012-04-12 2:57 ` Aneesh V
2012-04-12 3:00 ` Greg KH
2012-04-12 3:12 ` Paul Walmsley
2012-04-12 6:47 ` Santosh Shilimkar
2012-04-12 13:10 ` Greg KH
2012-04-12 13:34 ` Mohammed, Afzal
2012-04-12 14:10 ` Greg KH [this message]
2012-04-12 14:15 ` Mohammed, Afzal
2012-04-12 14:21 ` Kevin Hilman
2012-04-12 17:00 ` Paul Walmsley
2012-04-12 18:50 ` Cousson, Benoit
2012-04-12 19:15 ` Paul Walmsley
2012-04-12 19:24 ` Cousson, Benoit
2012-04-13 9:07 ` Felipe Balbi
2012-04-12 14:14 ` Shilimkar, Santosh
2012-04-12 19:58 ` V, Aneesh
2012-04-23 10:56 ` Mohammed, Afzal
2012-04-23 11:04 ` Shilimkar, Santosh
2012-04-23 11:09 ` Mohammed, Afzal
2012-04-23 14:27 ` Greg KH
2012-04-23 14:44 ` Shilimkar, Santosh
2012-04-27 13:16 ` Santosh Shilimkar
2012-04-13 14:15 ` Mark Salter
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=20120412141050.GA31968@kroah.com \
--to=greg@kroah.com \
--cc=afzal@ti.com \
--cc=aneesh@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mgreer@animalcreek.com \
--cc=msalter@redhat.com \
--cc=paul@pwsan.com \
--cc=santosh.shilimkar@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