From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 0/9] Convert OMAP GPMC to driver
Date: Wed, 25 Apr 2012 09:44:25 -0700 [thread overview]
Message-ID: <20120425164424.GT3739@atomide.com> (raw)
In-Reply-To: <cover.1333638917.git.afzal@ti.com>
* Afzal Mohammed <afzal@ti.com> [120405 09:06]:
> Hi,
>
> GPMC driver conversion series. NAND and smsc911x ethernet device has
> been adapted to use GPMC driver.
>
> Patches has been generated over linux-omap/master, HEAD
> 33fc21e Linux-omap rebuilt: Updated to v3.4-rc1, merged in most of pending branches
> As OMAP3EVM does not boot linux-omap/master, merge commit,
> 58adb29 Merge branch 'io_chain_devel_3.4' of git://git.pwsan.com/linux-2.6 into prm
> has to be reverted to get OMAP3EVM boot.
> Last patch (with subject prefix TMP - 9/9) is for testing.
>
> Once driver is acceptable, platform code for other peripherals
> connected via GPMC would be adapted to make use of GPMC driver. And
> then the board modifications. But before that HWMOD entry has to be
> populated for respective SoC(s ?).
No, we can't do it this way, it breaks things. We need to first
convert everything to use the new GPMC driver, then move it.
> Now DESTINATION FOR THIS DRIVER has to be decided. Original plan was
> to consider GPMC as MFD. The peripheral(s) connected to GPMC being
> considered childs of MFD.
Let's not put it into MFD. This is a bus driver. But that
decision can wait as we cleary have quite a few things to convert
first under arch/arm/mach-omap2.
> Various options that could be seen so far on where this driver can go,
> 1. mfd
> 2. misc
> 3. drivers/platform/arm/ (create an new one?)
> 4. memory (create a new one ?)
It's a parallel bus driver, not memory not misc, not MFD.
Cheers,
Tony
next prev parent reply other threads:[~2012-04-25 16:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-05 15:45 [PATCH v3 0/9] Convert OMAP GPMC to driver Afzal Mohammed
2012-04-25 16:44 ` Tony Lindgren [this message]
2012-04-26 5:18 ` Mohammed, Afzal
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=20120425164424.GT3739@atomide.com \
--to=tony@atomide.com \
--cc=linux-arm-kernel@lists.infradead.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 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).