public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: sricharan <r.sricharan@ti.com>
Cc: linux-omap@vger.kernel.org, paul@pwsan.com, santosh.shilimkar@ti.com
Subject: Re: [RFC] omap4: Add board_data and initialise the serial pads
Date: Thu, 20 Jan 2011 09:33:00 -0800	[thread overview]
Message-ID: <20110120173259.GV4957@atomide.com> (raw)
In-Reply-To: <1295363712-5940-1-git-send-email-r.sricharan@ti.com>

Hi,

* sricharan <r.sricharan@ti.com> [110118 07:11]:
> Pass the board specific serial pad mux data
> to the platform level init code.
> 
> Signed-off-by: sricharan <r.sricharan@ti.com>
> ---
> This is a test patch and not intended for a specific use case.
> 
> 1) The support to add the pad data to the device hwmod entry and to use
>    it to dynamically configure the pads based on the state of the
>    hwmod is already present.
> 
> 2) But using that for pads that requires only  initialisation and not 
>    dynamic remux, brings in a overhead to iterate over all the
>    hwmod signals of the device for every device enable/idle transitions.

The right fix for this problem is to change the mux code to keep a separate
list for dynamic pads and static pads. That way all the static pads can
be skipped, and the dynamic list is empty in most cases.

Regards,

Tony

      reply	other threads:[~2011-01-20 17:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-18 15:15 [RFC] omap4: Add board_data and initialise the serial pads sricharan
2011-01-20 17:33 ` Tony Lindgren [this message]

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=20110120173259.GV4957@atomide.com \
    --to=tony@atomide.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=paul@pwsan.com \
    --cc=r.sricharan@ti.com \
    --cc=santosh.shilimkar@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