All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nishanth Menon <menon.nishanth@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] ARM: OMAP3/4: proposal: Cleanup MUX
Date: Fri, 05 Nov 2010 15:56:46 -0400	[thread overview]
Message-ID: <4CD4617E.8050609@gmail.com> (raw)

Folks,
I would like to work on the following: Cleanup mux configurations done 
in OMAP3 and 4 platforms. includes the following:
a) have isolate mux configurations per IP configuration, e.g. for EHCI, 
we have a mux array definition for EHCI etc..
b) remove ALL mux configurations that are not relevant for u-boot 
functionality - currently we do all muxing in u-boot(including stuff 
like camera which obviously we dont use in u-boot).

any kernel breakages as a result of "assumptions" of muxing already done 
is to be fixed in kernel itself - kernel *has* a mux framework for OMAP 
and platforms files *should* be using that for kernel functionality that 
they need. no point in carrying that burden in u-boot.

I would like to post this patches so that for the next merge window we 
could pull this in and notify the linux-omap kernel guys to fix their 
stuff if they depend on u-boot for mux configurations - it is high time 
they stop being closely tied to U-boot and have capability to deal with 
other bootloaders which may or maynot have capability for doing muxing - 
it also saves us to add and maintain mux configurations for linux kernel 
booting -> u-boot is supposed to support multiple operating systems (not 
just linux kernel).

-- 
Regards,
Nishanth Menon

             reply	other threads:[~2010-11-05 19:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-05 19:56 Nishanth Menon [this message]
2010-11-06  2:47 ` [U-Boot] ARM: OMAP3/4: proposal: Cleanup MUX Steve Sakoman
2010-11-06  4:00   ` Nishanth Menon
2010-11-06  4:59     ` Peter Barada
2010-11-09  0:38       ` Nishanth Menon
2010-11-09  8:48         ` Premi, Sanjeev
2010-11-09 11:38           ` Nishanth Menon

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=4CD4617E.8050609@gmail.com \
    --to=menon.nishanth@gmail.com \
    --cc=u-boot@lists.denx.de \
    /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.