From: Mike Rapoport <mike@compulab.co.il>
To: Tony Lindgren <tony@atomide.com>
Cc: Kevin Hilman <khilman@deeprootsystems.com>,
"Menon, Nishanth" <nm@ti.com>,
Cory Maccarrone <darkstar6262@gmail.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: mux strategy (was RE: [PATCH] [OMAP1] mux: Add MMC mux pins for omap7xx)
Date: Thu, 08 Oct 2009 08:27:40 +0200 [thread overview]
Message-ID: <4ACD865C.70106@compulab.co.il> (raw)
In-Reply-To: <20091007174750.GG7899@atomide.com>
Tony Lindgren wrote:
> * Kevin Hilman <khilman@deeprootsystems.com> [091006 15:18]:
>> "Menon, Nishanth" <nm@ti.com> writes:
>>
>
> BTW, I've been thinking about the following sets of patches for the next
> merge window:
>
> 1. Do the include directories for mach-omap1 and mach-omap2 as suggested
> by Russell earlier
>
> 2. Move all mux code to only live under arch/arm/*omap*/ and make sure
> drivers don't call omap_cfg_reg() any longer
IMHO, we should also change omap_cfg_reg to omap_cfg_mux or something alike.
> 3. Remove the enumeration for the mux and require all the boards to
> register the pins they'll use
+1
> After these it should be trivial to improve the mux code further. The
> steps 2 & 3 above will be most likely breaking things for some boards,
> so help will be needed with testing.
>
> Regards,
>
> Tony
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
Sincerely yours,
Mike.
next prev parent reply other threads:[~2009-10-08 6:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-06 13:53 [PATCH] [OMAP1] mux: Add MMC mux pins for omap7xx Cory Maccarrone
2009-10-06 17:30 ` Nishanth Menon
2009-10-06 19:44 ` Cory Maccarrone
2009-10-06 21:13 ` Kevin Hilman
2009-10-06 21:52 ` mux strategy (was RE: [PATCH] [OMAP1] mux: Add MMC mux pins for omap7xx) Menon, Nishanth
2009-10-06 21:54 ` Kevin Hilman
2009-10-07 17:47 ` Tony Lindgren
2009-10-07 18:33 ` Kevin Hilman
2009-10-07 18:48 ` Cory Maccarrone
2009-10-08 2:32 ` Philip Balister
2009-10-08 16:51 ` Tony Lindgren
2009-10-08 6:27 ` Mike Rapoport [this message]
2009-10-14 14:28 ` Kevin Hilman
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=4ACD865C.70106@compulab.co.il \
--to=mike@compulab.co.il \
--cc=darkstar6262@gmail.com \
--cc=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
--cc=tony@atomide.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 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.