From: jassi brar <jassisinghbrar@gmail.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: alsa-devel@alsa-project.org, Ben Dooks <ben-linux@fluff.org>,
Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: ASoC: SAMSUNG: About I2S_v4 support
Date: Wed, 3 Mar 2010 21:53:14 +0900 [thread overview]
Message-ID: <1b68c6791003030453l27435214v5877db054d42747d@mail.gmail.com> (raw)
In-Reply-To: <20100303112123.GA14190@rakim.wolfsonmicro.main>
On Wed, Mar 3, 2010 at 8:21 PM, Mark Brown
<broonie@opensource.wolfsonmicro.com> wrote:
> On Wed, Mar 03, 2010 at 08:10:32PM +0900, jassi brar wrote:
>> On Wed, Mar 3, 2010 at 6:54 PM, Mark Brown
>
>> > Please also remember that we need to get the clock API changes to allow
>> > the driver to start. I've been chasing patches for these for the past
>> > couple of kernel releases but it's not ideal that I need to do this.
>
>> I guess whatever needs to be done for the release version, will be done.
>> Though I am not sure if I should get into modifying s3c-clock support for
>> the sake of s3c-audio.
>
> The stuff that needs doing is the really basic stuff like registering
> CLKAUDIO2 so the driver can request it, not any substantial refactoring
> of the clocking code.
yeah, that's fine.
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
prev parent reply other threads:[~2010-03-03 12:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-03 8:32 ASoC: SAMSUNG: About I2S_v4 support jassi brar
2010-03-03 9:54 ` Mark Brown
2010-03-03 11:10 ` jassi brar
2010-03-03 11:21 ` Mark Brown
2010-03-03 12:53 ` jassi brar [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=1b68c6791003030453l27435214v5877db054d42747d@mail.gmail.com \
--to=jassisinghbrar@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=ben-linux@fluff.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=lrg@slimlogic.co.uk \
/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).