public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: linux-omap@vger.kernel.org, karthik-dp@ti.com, rnayak@ti.com,
	igor.stoppa@nokia.com, sakari.poussa@nokia.com,
	jouni.hogander@nokia.com, r-woodruff2@ti.com
Subject: Re: [PATCH 0/4] clockdomains: add OMAP2/3 clockdomain code, link 34xx clocks with clockdomains
Date: Wed, 23 Apr 2008 17:05:06 -0700	[thread overview]
Message-ID: <20080424000506.GD27546@atomide.com> (raw)
In-Reply-To: <20080419014100.8203.31672.stgit@localhost.localdomain>

* Paul Walmsley <paul@pwsan.com> [080418 18:48]:
> 
> Hi everyone,
> 
> This is the second version of the clockdomain patches.  It: 
> 
> . adds the IVA1 clockdomain in the DSP powerdomain, for OMAP2420 only
> 
> . replaces omap_type_t typedef with struct omap_chip_id
> 
> . removes all EXPORT_SYMBOLs - these can be added back in if clockdomain
>   code needs to be used from loadable PM modules - the expectation is that 
>   it will only be used from PM code
> 
> . creates _clkdm_lookup() to avoid potential race in clkdm_register()
> 
> . fixes several clockdomain platform flag bugs
> 
> . gets rid of tabs in comments
> 
> . is refreshed against current git head (e015fc7)
> 
> This version is tested against 3430SDP ES2.1, and compile-tested with
> N800 and 2430SDP configs.  Size, diffstat have been updated below.
> 
> Thanks to Tony & Jouni for review and comments.  More comments welcome,

Pushing today.

Tony

> 
> 
> - Paul
> 
> -------------------------
> 
> Hello,
> 
> this patch series adds a hardware control interface for OMAP2/3
> clockdomains.  Also added is clockdomain usecounting of underlying
> clocks, so hardware-supervised and software-supervised clockdomain
> transitions can occur correctly.  The interface is fully documented in
> the code.
> 
> 24xx clocks are not yet linked with clockdomains. This will be done in
> a later patchset.
> 
> This series must be applied after the powerdomain series, posted earlier.
> 
> Clockdomain code tested on 3430SDP ES2.1; also boot-tested on N800.
> 
> Many people at Nokia and TI provided commentary and review during the
> development of the clockdomain patches.  Particular help came from (in
> alphabetical order): Karthik Dasu, Tony Lindgren, Rajendra Nayak,
> Sakari Poussa, Igor Stoppa, and Richard Woodruff.  Jouni Högander
> merits special mention; he took the original code and made it do what
> it was supposed to do on the hardware, testing and fixing many bugs.
> 
> 
> -----------
> 
> size:
>   text    data     bss     dec     hex filename
> 3269405  152552  100736 3522693  35c085 vmlinux.3430sdp.orig
> 3272093  154920  100736 3527749  35d445 vmlinux.3430sdp
> 
> Paul Walmsley (4):
>       Subject: Integrate OMAP3 clocks with clockdomain code
>       Subject: encode OMAP2/3 clockdomains
>       Subject: connect clockdomain code to powerdomain code
>       Subject: add base OMAP2/3 clockdomain code
> 
> 
>  arch/arm/mach-omap2/Makefile            |    3 
>  arch/arm/mach-omap2/clock.c             |   45 ++
>  arch/arm/mach-omap2/clock.h             |    1 
>  arch/arm/mach-omap2/clock34xx.c         |    4 
>  arch/arm/mach-omap2/clock34xx.h         |  196 +++++++++-
>  arch/arm/mach-omap2/clockdomain.c       |  606 +++++++++++++++++++++++++++++++
>  arch/arm/mach-omap2/clockdomains.h      |  298 +++++++++++++++
>  arch/arm/mach-omap2/cm-regbits-24xx.h   |   24 +
>  arch/arm/mach-omap2/cm-regbits-34xx.h   |   42 ++
>  arch/arm/mach-omap2/io.c                |    4 
>  arch/arm/mach-omap2/pm.c                |   12 -
>  arch/arm/mach-omap2/powerdomain.c       |  132 +++++++
>  arch/arm/plat-omap/Kconfig              |   12 +
>  drivers/dsp/dspgateway/dsp_core.c       |    2 
>  include/asm-arm/arch-omap/clock.h       |    4 
>  include/asm-arm/arch-omap/clockdomain.h |  105 +++++
>  include/asm-arm/arch-omap/powerdomain.h |   16 +
>  17 files changed, 1457 insertions(+), 49 deletions(-)
>  create mode 100644 arch/arm/mach-omap2/clockdomain.c
>  create mode 100644 arch/arm/mach-omap2/clockdomains.h
>  create mode 100644 include/asm-arm/arch-omap/clockdomain.h
> 
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2008-04-24  0:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-19  1:42 [PATCH 0/4] clockdomains: add OMAP2/3 clockdomain code, link 34xx clocks with clockdomains Paul Walmsley
2008-04-19  1:43 ` [PATCH 1/4] clockdomains: add base OMAP2/3 clockdomain code Paul Walmsley
2008-04-19  1:43 ` [PATCH 2/4] clockdomains: connect clockdomain code to powerdomain code Paul Walmsley
2008-04-19  1:43 ` [PATCH 3/4] clockdomains: encode OMAP2/3 clockdomains Paul Walmsley
2008-04-19  1:43 ` [PATCH 4/4] clockdomains: integrate OMAP3 clocks with clockdomain code Paul Walmsley
2008-04-24  0:05 ` Tony Lindgren [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-04-10 16:25 [PATCH 0/4] Clockdomains: add OMAP2/3 clockdomain code, link 34xx clocks with clockdomains Paul Walmsley

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=20080424000506.GD27546@atomide.com \
    --to=tony@atomide.com \
    --cc=igor.stoppa@nokia.com \
    --cc=jouni.hogander@nokia.com \
    --cc=karthik-dp@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=paul@pwsan.com \
    --cc=r-woodruff2@ti.com \
    --cc=rnayak@ti.com \
    --cc=sakari.poussa@nokia.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