From: sricharan <r.sricharan@ti.com>
To: r.sricharan@ti.com, linux-omap@vger.kernel.org
Cc: santosh.shilimkar@ti.com, tony@atomide.com, paul@pwsan.com
Subject: [PATCH 0/5] omap2+: mux: Add support for static and dynamic pads.
Date: Fri, 28 Jan 2011 10:38:13 +0530 [thread overview]
Message-ID: <1296191298-17545-1-git-send-email-r.sricharan@ti.com> (raw)
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.
3) By seperating the pads that requires remux as dynamic and the
ones that do not as static the above overhead is avoided.
4) This way the static and dynamic pads are initialised,
and only dynamic pads are taken for remuxing.
sricharan (5):
omap2+: mux: Seperate the pads of a hwmod as static and dynamic.
omap4: board-4430sdp: Initialise the serial pads
omap3: board-3430sdp: Initialise the serial pads.
omap4: board-omap4panda: Initialise the serial pads
omap2+: board-n8x0: Change the flags for the serial pads.
arch/arm/mach-omap2/board-3430sdp.c | 86 ++++++++++-
arch/arm/mach-omap2/board-4430sdp.c | 73 +++++++++-
arch/arm/mach-omap2/board-n8x0.c | 2 +-
arch/arm/mach-omap2/board-omap4panda.c | 72 +++++++++-
arch/arm/mach-omap2/mux.c | 219 +++++++++++++++++++++-----
arch/arm/mach-omap2/mux.h | 33 ++++-
arch/arm/mach-omap2/omap_hwmod.c | 6 +-
arch/arm/plat-omap/include/plat/omap_hwmod.h | 7 +-
8 files changed, 441 insertions(+), 57 deletions(-)
next reply other threads:[~2011-01-28 5:06 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-28 5:08 sricharan [this message]
2011-01-28 5:08 ` [PATCH 1/5] omap2+: mux: Seperate the pads of a hwmod as static and dynamic sricharan
2011-01-28 20:49 ` Anand Gadiyar
2011-01-31 14:20 ` Sricharan R
2011-02-23 18:49 ` Tony Lindgren
2011-02-25 13:21 ` Sricharan R
2011-01-28 5:08 ` [PATCH 2/5] omap4: board-4430sdp: Initialise the serial pads sricharan
2011-02-23 18:49 ` Tony Lindgren
2011-02-25 13:21 ` Sricharan R
2011-01-28 5:08 ` [PATCH 3/5] omap3: board-3430sdp: " sricharan
2011-01-28 5:08 ` [PATCH 4/5] omap4: board-omap4panda: " sricharan
2011-01-28 20:53 ` Anand Gadiyar
2011-01-31 14:20 ` Sricharan R
2011-02-23 18:49 ` Tony Lindgren
2011-02-25 13:22 ` Sricharan R
2011-01-28 5:08 ` [PATCH 5/5] omap2+: board-n8x0: Change the flags for " sricharan
2011-02-23 18:49 ` Tony Lindgren
2011-02-25 13:21 ` Sricharan R
2011-02-10 12:04 ` [PATCH 0/5] omap2+: mux: Add support for static and dynamic pads Sricharan R
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=1296191298-17545-1-git-send-email-r.sricharan@ti.com \
--to=r.sricharan@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
--cc=santosh.shilimkar@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.