From: tony@atomide•com (Tony Lindgren)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH 3/3] memory: gpmc: Move omap gpmc code to live under drivers
Date: Mon, 24 Nov 2014 07:44:04 -0800 [thread overview]
Message-ID: <20141124154403.GB2817@atomide.com> (raw)
In-Reply-To: <547301AB.9040905@ti.com>
* Roger Quadros <rogerq@ti•com> [141124 02:02]:
> On 11/21/2014 08:34 PM, Tony Lindgren wrote:
> > --- a/drivers/memory/Kconfig
> > +++ b/drivers/memory/Kconfig
> > @@ -41,6 +41,14 @@ config TI_EMIF
> > parameters and other settings during frequency, voltage and
> > temperature changes
> >
> > +config OMAP_GPMC
> > + bool
>
> We should depend on ARCH_OMAP2PLUS. Other platforms won't benefit
> anything from this driver.
We can't do that yet until we have sorted out the remaining platform
data issues with arch/arm/mach-omap2/*gpmc*.c files.
So OMAP_GPMC is currently a silent Kconfig option that does not show
up as the description after the bool is not there, we select
OMAP_GPMC automatically based on ARCH_OMAP2PLUS.
Once we have the remaining legacy code issues sorted out, we can
make this into just a regular device driver.
Regards,
Tony
next prev parent reply other threads:[~2014-11-24 15:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-21 18:34 [PATCHv2 0/3] Move omap GPMC to live in drivers/memory Tony Lindgren
2014-11-21 18:34 ` [PATCH 1/3] ARM: OMAP2+: Prepare to move GPMC to drivers by platform data header Tony Lindgren
2014-11-26 11:28 ` Roger Quadros
2014-11-21 18:34 ` [PATCH 2/3] ARM: OMAP2+: Move GPMC initcall to devices.c Tony Lindgren
2014-11-21 18:34 ` [PATCH 3/3] memory: gpmc: Move omap gpmc code to live under drivers Tony Lindgren
2014-11-21 18:39 ` Felipe Balbi
2014-11-21 18:45 ` Tony Lindgren
2014-11-24 10:00 ` Roger Quadros
2014-11-24 15:44 ` Tony Lindgren [this message]
2014-11-26 11:22 ` Roger Quadros
2014-11-26 20:10 ` Tony Lindgren
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=20141124154403.GB2817@atomide.com \
--to=tony@atomide$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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