From: Sumit Semwal <sumit.semwal@ti.com>
To: tomi.valkeinen@ti.com, linux-omap@vger.kernel.org
Cc: Sumit Semwal <sumit.semwal@ti.com>
Subject: [Patch v2 0/2] OMAP2PLUS:DSS2: use opt-clocks information from hwmod.
Date: Mon, 28 Feb 2011 20:32:41 +0530 [thread overview]
Message-ID: <1298905363-28871-1-git-send-email-sumit.semwal@ti.com> (raw)
This series uses information about opt-clocks provided by omap_hwmod framework
to select which of the non-mandatory DSS clocks are available on a given
platform.
A function pointer opt_clock_available is exported via pdata, which checks the
clock roles returned by hwmod database.
In the driver, while doing clk-get, it is checked if as per hwmod a given clock
is an opt-clock or not, and is handled accordingly.
Tested on: OMAP3430sdp
Sumit Semwal (2):
OMAP2PLUS:DSS2: add opt_clock_available in pdata
OMAP2PLUS:DSS2: Use opt_clock_available from pdata
changes from v1:
- made opt_clock_available a function pointer in the omap_display_platform_data
to avoid having to copy the opt-clock role names.
Based on top of:
http://gitorious.org/linux-omap-dss2/linux/commits/master
commit: ad1c76c: OMAP: Overo Palo43 LCD support
arch/arm/mach-omap2/display.c | 20 ++++++++++++
arch/arm/plat-omap/include/plat/display.h | 2 +
drivers/video/omap2/dss/dss.c | 46 +++++++++++++++++++----------
3 files changed, 52 insertions(+), 16 deletions(-)
next reply other threads:[~2011-02-28 15:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-28 15:02 Sumit Semwal [this message]
2011-02-28 15:02 ` [Patch v2 1/2] OMAP2PLUS:DSS2: add opt_clock_available in pdata Sumit Semwal
2011-02-28 16:03 ` Tomi Valkeinen
2011-03-01 5:42 ` Semwal, Sumit
2011-03-01 6:19 ` Tomi Valkeinen
2011-03-01 6:27 ` Semwal, Sumit
2011-03-01 6:37 ` Tomi Valkeinen
2011-03-01 6:41 ` Semwal, Sumit
2011-02-28 15:02 ` [Patch v2 2/2] OMAP2PLUS:DSS2: Use opt_clock_available from pdata Sumit Semwal
2011-02-28 15:09 ` [Patch v2 0/2] OMAP2PLUS:DSS2: use opt-clocks information from hwmod Semwal, Sumit
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=1298905363-28871-1-git-send-email-sumit.semwal@ti.com \
--to=sumit.semwal@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=tomi.valkeinen@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