public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Nishanth Menon <nm@ti.com>
To: Cory Maccarrone <darkstar6262@gmail.com>
Cc: "Pais, Allen" <allen.pais@ti.com>,
	"Aguirre Rodriguez, Sergio Alberto" <saaguirre@ti.com>,
	linux-omap <linux-omap@vger.kernel.org>,
	"Chikkature Rajashekar, Madhusudhan" <madhu.cr@ti.com>,
	"Pandita, Vikram" <vikram.pandita@ti.com>,
	"Gadiyar, Anand" <gadiyar@ti.com>,
	"Cousson, Benoit" <b-cousson@ti.com>,
	Felipe Balbi <felipe.balbi@nokia.com>,
	Kevin Hilman <khilman@deeprootsystems.com>,
	"Premi, Sanjeev" <premi@ti.com>,
	"Shilimkar, Santosh" <santosh.shilimkar@ti.com>,
	Tony Lindgren <tony@atomide.com>
Subject: Re: [RFC][Patch V1] OMAP3: Mux Changes.
Date: Fri, 16 Oct 2009 10:03:56 -0500	[thread overview]
Message-ID: <4AD88B5C.3020609@ti.com> (raw)
In-Reply-To: <6cb013310910160715qb8a93b5y1c34781ee565dc32@mail.gmail.com>

Cory Maccarrone had written, on 10/16/2009 09:15 AM, the following:
> On Thu, Oct 15, 2009 at 9:53 PM, Nishanth Menon <nm@ti.com 
> <mailto:nm@ti.com>> wrote:
> 
>     Pais, Allen had written, on 10/15/2009 11:53 PM, the following:
> 
>         a) A simple comment to all my comments: why cant we have these
>         in bootloader and just simply leave the mux file alone?
>         [Allen] Yes Nishanth, this would be a much cleaner approach.
>         Even Santosh had suggested
>         The same, if we can conclude on a approach here, I can go ahead
>         and do the Mux Change it accordingly.
> 
>     Then lets please fix the bootloader and drop this patch.
> 
> 
[...]
> Maybe I'm missing something, but why is it more desirable to add the mux 
> code to the bootloader instead of the kernel?  Wouldn't adding it to the 
> kernel guarantee it works regardless of the bootloader?
adding mux in kernel guarentees that it is independent of the bootloader 
- yes - no questions on that. There are two strategies that can be taken:

A) Ensure that kernel is independent from bootloader variances
   - this is desirable and would adhere to the rules of an entity uses 
the resources(muxes) ONLY what it is required for itself to work -> e.g. 
bootloader would use the minimal set that is required for itself to 
function.

B) Divide the load -> always assume that kernel and bootloaders work 
together.
    - Do all the static muxes in u-boot -> since the u-boot dies off 
once the kernel starts up, the memory is completely freed up.
    - Only the dynamic muxes (e.g. pins being used in two modes by two 
drivers) are handled by the kernel.

The current strategy that is implemented for OMAP3 is (B), but once the 
kernel infrastructure for mux handling improves we should be able to 
arrive at a compromise between A and B as far as execution latencies Vs 
memory usage Vs independence issues are concerned. we are not there yet 
unfortunately.


-- 
Regards,
Nishanth Menon

  parent reply	other threads:[~2009-10-16 15:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-15  9:38 [RFC][Patch V1] OMAP3: Mux Changes Pais, Allen
2009-10-15 12:24 ` Menon, Nishanth
2009-10-15 12:39   ` Menon, Nishanth
2009-10-16  4:53     ` Pais, Allen
2009-10-16  4:53       ` Nishanth Menon
2009-10-16 14:20         ` Cory Maccarrone
     [not found]         ` <6cb013310910160715qb8a93b5y1c34781ee565dc32@mail.gmail.com>
2009-10-16 15:03           ` Nishanth Menon [this message]
2009-10-16 15:50             ` Tony Lindgren
2009-11-12  1:54 ` 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=4AD88B5C.3020609@ti.com \
    --to=nm@ti.com \
    --cc=allen.pais@ti.com \
    --cc=b-cousson@ti.com \
    --cc=darkstar6262@gmail.com \
    --cc=felipe.balbi@nokia.com \
    --cc=gadiyar@ti.com \
    --cc=khilman@deeprootsystems.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=madhu.cr@ti.com \
    --cc=premi@ti.com \
    --cc=saaguirre@ti.com \
    --cc=santosh.shilimkar@ti.com \
    --cc=tony@atomide.com \
    --cc=vikram.pandita@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