From: tomi.valkeinen@ti.com (Tomi Valkeinen)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 2/3] ARM: omap: hwmod: get rid of all omap_clk_get_by_name usage
Date: Thu, 30 Aug 2012 19:42:13 +0300 [thread overview]
Message-ID: <1346344933.2327.43.camel@deskari> (raw)
In-Reply-To: <503F5517.4010100@ti.com>
On Thu, 2012-08-30 at 13:57 +0200, Benoit Cousson wrote:
> On 08/30/2012 10:39 AM, Rajendra Nayak wrote:
> > On Thursday 30 August 2012 05:45 AM, Turquette, Mike wrote:
> >> On Wed, Aug 29, 2012 at 1:56 AM, Rajendra Nayak<rnayak@ti.com> wrote:
> >>> diff --git a/arch/arm/mach-omap2/clock44xx_data.c
> >>> b/arch/arm/mach-omap2/clock44xx_data.c
> >>> index d7f55e4..a3831a2 100644
> >>> --- a/arch/arm/mach-omap2/clock44xx_data.c
> >>> +++ b/arch/arm/mach-omap2/clock44xx_data.c
> >>> @@ -3156,6 +3156,7 @@ static struct omap_clk omap44xx_clks[] = {
> >>> CLK(NULL, "dss_tv_clk",&dss_tv_clk, CK_443X),
> >>> CLK(NULL, "dss_48mhz_clk",&dss_48mhz_clk, CK_443X),
> >>> CLK(NULL, "dss_dss_clk",&dss_dss_clk, CK_443X),
> >>> + CLK(NULL, "dss_fck",&dss_fck, CK_443X),
> >>> CLK("omapdss_dss", "ick",&dss_fck, CK_443X),
> >>
> >> Is it right to re-use dss_fck for the "ick" here? I think it is due
> >> to omap4 modulemode stuff but I don't have DM in front of me and
> >> wanted a double-check...
> >
> > yes, its because of the wierdness of DSS clocks where a so-called
> > optional clock is actually a function clock.
>
> Not only, it is a hack to allow the DSS to be enabled whenever a DSS
> submodule has to be enabled. Since they are sharing the ick, it will
> enable the modulemode when the DISPC will be enabled.
>
> That hack should disappear as soon as the DSS will be able to handle the
> PM dependency between DSS submodules and the DSS itself using pm_runtime
> parent/child link.
> And then we will have to remove this fake ick modulemode clock node and
> let hwmod handle that properly.
>
> Tomi already cleaned the DSS part, I guess it should be upstreamed soon,
> if this is not already the case.
This is in 3.5. omapdss_dss is now the parent for the rest of the dss
submodules, and runtime PM is being used.
I think we should now revisit this dss clock handling to see if there
are any other changes required in the omapdss side, but I hope they are
already according to our discussions and correct.
Tomi
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20120830/1a379099/attachment.sig>
next prev parent reply other threads:[~2012-08-30 16:42 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-29 8:56 [PATCH v4 0/3] Prepare for OMAP2+ movement to Common Clk Rajendra Nayak
2012-08-29 8:56 ` [PATCH v4 1/3] ARM: omap: clk: add clk_prepare and clk_unprepare Rajendra Nayak
2012-08-30 0:03 ` Turquette, Mike
2012-08-29 8:56 ` [PATCH v4 2/3] ARM: omap: hwmod: get rid of all omap_clk_get_by_name usage Rajendra Nayak
2012-08-30 0:08 ` Russell King - ARM Linux
2012-08-30 8:37 ` Rajendra Nayak
2012-08-30 0:15 ` Turquette, Mike
2012-08-30 8:39 ` Rajendra Nayak
2012-08-30 11:57 ` Benoit Cousson
2012-08-30 16:42 ` Tomi Valkeinen [this message]
2012-08-31 6:23 ` Archit Taneja
2012-08-31 7:15 ` Tomi Valkeinen
2012-08-31 8:20 ` Archit Taneja
2012-08-31 8:27 ` Tomi Valkeinen
2012-08-31 8:28 ` Archit Taneja
2012-10-05 9:46 ` OMAP4 clock/pm fixes [was: " Archit Taneja
2012-10-05 12:20 ` Benoit Cousson
2012-10-05 12:29 ` Archit Taneja
2012-10-05 12:37 ` Rajendra Nayak
2012-10-05 13:20 ` Archit Taneja
2012-10-05 13:31 ` Rajendra Nayak
2012-10-05 13:46 ` Archit Taneja
2012-10-05 13:51 ` Benoit Cousson
2012-09-22 18:55 ` Paul Walmsley
2012-09-24 5:09 ` Rajendra Nayak
2012-08-29 8:56 ` [PATCH v4 3/3] ARM: OMAP2+: clock: Remove all direct dereferencing of struct clk Rajendra Nayak
2012-08-30 20:56 ` [PATCH v4 0/3] Prepare for OMAP2+ movement to Common Clk Paul Walmsley
2012-08-31 5:03 ` Vaibhav Hiremath
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=1346344933.2327.43.camel@deskari \
--to=tomi.valkeinen@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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