linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: jassisinghbrar@gmail.com (jassi brar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 09/10] S3C64XX I2S: Set parent links for clock audio-bus.
Date: Tue, 15 Sep 2009 21:57:05 +0900	[thread overview]
Message-ID: <1b68c6790909150557q53bf9843g38bf41fcaf5beca3@mail.gmail.com> (raw)
In-Reply-To: <20090915121539.GO22878@rakim.wolfsonmicro.main>

On Tue, Sep 15, 2009 at 9:15 PM, Mark Brown
<broonie@opensource.wolfsonmicro.com> wrote:
> On Tue, Sep 15, 2009 at 08:42:32PM +0900, jassi brar wrote:
>> On Tue, Sep 15, 2009 at 8:12 PM, Mark Brown
>
>> > The mout/fout connection in particular isn't audio local, there's way
>> > more EPLL users than just the audio.
>
>> Ofcourse, but i think those drivers and requirements are far off that
>> may need EPLL.
>
> Are you sure? ?UART, USB, MMC and SPI all have options to clock off EPLL
> - I've worked with designs that were actively using it for at least USB.
In mainline?
All these devices do have option to source from EPLL but they don't
seem to use it.

>> EPLL is a shared but unused resource. Using EPLL gives far more accurate clocks
>> and we shudn't keep hands off just because there is no arbiter.
>
> That doesn't seem like it's going to work so well, especially if Samsung
> are actively pushing more drivers into mainline - if two drivers start
> trying to play about with this simultaneously then what'll happen is
> that users who end up trying to use those drivers together will have to
> deal with the fallout.
as i said in another reply, current set of patches are meant to be as
simple as possible.
once that is done I am all to implement and support new features.

>> If not here, i favor controlling it from machine specific code.
>
> Well, for the EPLL mux/PLL connection I'm not sure why we're not just
> doing it in the default clock setup - I had thought that that was being
> done by default already to be honest but I've not checked.
yes, we can simply do clk_setparent in platform/machine code. thats
what some of
samsung-git drivers do.

  reply	other threads:[~2009-09-15 12:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-15 10:02 [PATCH 09/10] S3C64XX I2S: Set parent links for clock audio-bus Jassi
2009-09-15 11:12 ` Mark Brown
2009-09-15 11:42   ` jassi brar
2009-09-15 12:15     ` Mark Brown
2009-09-15 12:57       ` jassi brar [this message]
2009-09-15 13:33         ` Mark Brown
2009-09-16  0:17 ` Ben Dooks

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=1b68c6790909150557q53bf9843g38bf41fcaf5beca3@mail.gmail.com \
    --to=jassisinghbrar@gmail.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;
as well as URLs for NNTP newsgroup(s).