public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Paul Walmsley <paul@pwsan.com>
Cc: linux-omap@vger.kernel.org, saaguirre@ti.com
Subject: Re: [PATCH] OMAP3 clock: camera module has no target IDLEST bit
Date: Fri, 5 Sep 2008 23:37:26 +0100	[thread overview]
Message-ID: <20080905223725.GD17156@flint.arm.linux.org.uk> (raw)
In-Reply-To: <alpine.DEB.1.00.0809051332380.32223@utopia.booyaka.com>

On Fri, Sep 05, 2008 at 01:34:03PM -0600, Paul Walmsley wrote:
> We must not attempt to wait for the CAM module to become ready after
> clock enable, since it has no target IDLEST bit.

Grrr.  These things seem to be collecting here, and in need of a
more generic and elegant solution.  (Please always do that rather
than extending an already existing hack.)

In mainline, I see a bunch of exclusions in omap2_clk_wait_ready()
for OMAP24xx and OMAP34xx.

Your struct clk has a 'flags' field.  Currently, bits 13 to 20 are
free.  Enough room to fit into it two extra bits - a "don't wait for
OMAP24xx" and "don't wait for OMAP34xx" bits.

They can then be used thusly:

	if (cpu_is_omap24xx() && clk->flags & CLK_NOWAIT_24XX)
		return;
	if (cpu_is_omap34xx() && clk->flags & CLK_NOWAIT_34XX)
		return;

rather than throwing individual exceptions into clock.c.  Such a
solution is far more elegant, easier to review, and likely to be
far smaller in the long run - both in terms of lines of change and
code size.

  reply	other threads:[~2008-09-05 22:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-05 19:34 [PATCH] OMAP3 clock: camera module has no target IDLEST bit Paul Walmsley
2008-09-05 22:37 ` Russell King - ARM Linux [this message]
2008-09-10 17:25   ` 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=20080905223725.GD17156@flint.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=linux-omap@vger.kernel.org \
    --cc=paul@pwsan.com \
    --cc=saaguirre@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