From: jassisinghbrar@gmail.com (jassi brar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 08/10] S3C64XX I2S: Return correct codec clock
Date: Wed, 16 Sep 2009 14:16:54 +0900 [thread overview]
Message-ID: <1b68c6790909152216od3f372ftc2fa3db488e6996@mail.gmail.com> (raw)
In-Reply-To: <20090915115618.GN22878@rakim.wolfsonmicro.main>
On Tue, Sep 15, 2009 at 8:56 PM, Mark Brown
<broonie@opensource.wolfsonmicro.com> wrote:
> On Tue, Sep 15, 2009 at 08:21:05PM +0900, jassi brar wrote:
>> On Tue, Sep 15, 2009 at 8:06 PM, Mark Brown
>
>> > There's three possible clocks here according to the datasheet - PCLK,
>> > CLKAUDIO and I2SCLK - so this will still give the wrong clock some of
>> > the time. ?Also, please use checkpatch
>
>> Yes, but the existing code doesn't consider I2SCLK at all.
>> The infra isn't there to provide the clock pointer anyhow.
>
> Please put a comment there explaining that, or ideally code that returns
> an error in those cases, to make it clearer what's being done.
Wait, there is no option for selecting I2SCLK in the manual. That is
behind the MUX along with Mpll/Epll Out etc.
In the driver we actually have all the correct options : PCLK or
CLKAUDIO(which is the output of the MUX).
The IMS bit can select only either PCLK or CLKAUDIO.So, i guess
the patch is fine as it is.
next prev parent reply other threads:[~2009-09-16 5:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-15 10:02 [PATCH 08/10] S3C64XX I2S: Return correct codec clock Jassi
2009-09-15 11:06 ` Mark Brown
2009-09-15 11:21 ` jassi brar
2009-09-15 11:56 ` Mark Brown
2009-09-16 5:16 ` jassi brar [this message]
2009-09-16 11:09 ` Mark Brown
2009-09-16 11:50 ` jassi brar
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=1b68c6790909152216od3f372ftc2fa3db488e6996@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 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.