All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Dooks <ben-linux@fluff.org>
To: jassi brar <jassisinghbrar@gmail.com>
Cc: linux-samsung-soc@vger.kernel.org
Subject: Re: clock sourcing suggestion
Date: Wed, 30 Sep 2009 22:13:44 +0100	[thread overview]
Message-ID: <20090930211343.GA28928@trinity.fluff.org> (raw)
In-Reply-To: <1b68c6790909291936s9fc10c2t8385f094980ef13a@mail.gmail.com>

On Wed, Sep 30, 2009 at 11:36:27AM +0900, jassi brar wrote:
> Hi,
> 
>  I2S audio-bus[0,1] in s3c6410 can source clock, among other options,
>  from dedicated pcm_cdclk[0,1] respectively.
>  Whereas in s3c6400, both I2S audio-bus[0,1]  share one common pcm_cdclk.
> 
> The arch/arm/plat-s3c64xx/s3c6400-clock.c  makes audio-bus-0,1 share the same
> pcm_cdclk(s3c6400 case).
> 
> Should we use #ifdef CPU_S3C6410 to assign proper clock sources ?
> But I am afraid that might come in the way of building common kernel
> for 6400 and 6410.
> 
> What should be the solution, please suggest?

A quick think would suggest two solutions:

1) Change the clocks before registering in the relevant init function

2) Moving those clocks out of the common clock code and registering
   s3c6400 version in s3c6400 clock setup and s3c6410 in s3c6410 clock
   setup.

I can have a look tommorow at the code if any further info is required.

(2) is probably the best thing to do.

-- 
Ben

Q:      What's a light-year?
A:      One-third less calories than a regular year.


      reply	other threads:[~2009-09-30 21:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-30  2:36 clock sourcing suggestion jassi brar
2009-09-30 21:13 ` Ben Dooks [this message]

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=20090930211343.GA28928@trinity.fluff.org \
    --to=ben-linux@fluff.org \
    --cc=jassisinghbrar@gmail.com \
    --cc=linux-samsung-soc@vger.kernel.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 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.