From: ben@trinity.fluff.org (Ben Dooks)
To: linux-arm-kernel@lists.infradead.org
Subject: Samsung S3C6410 mainline merge coordination
Date: Wed, 2 Sep 2009 20:09:34 +0100 [thread overview]
Message-ID: <20090902190934.GN25153@trinity.fluff.org> (raw)
In-Reply-To: <1b68c6790909020644k757827f4kf590779f384ceccb@mail.gmail.com>
On Wed, Sep 02, 2009 at 10:44:35PM +0900, jassi brar wrote:
> On Wed, Sep 2, 2009 at 9:11 PM, Harald Welte<laforge@gnumonks.org> wrote:
> > On Wed, Sep 02, 2009 at 11:05:01AM +0100, Mark Brown wrote:
> >> > === Sound ===
> >> > * needs further investigation, there are many different drivers/versions/options
> >>
> >> Merge any changes in with the mainline drivers - there's relatively
> >> little difference from the s3c24xx IPs. ?There's a reasonable chance
> >> I'll get round to this myself for the 64xx series since I have one which
> >> I'm using for some of my development.
> >
> > Apparently there are also features like operating the SoC codec in slave mode
> > as well as different clock configurations wich mainline is missing.
>
> Yes, none of mainline SMDK supports SoC-Slave mode or sourcing I2S IP with
> various possible clocks(PCLK, EPLL, CDCLK) etc yet. Samsung tree has
> implemented
> and fully tested these features for 6410, 6440 and C100.
>
> My idea is to submit only "better enabled" I2S driver with Slave support.
> Clock sourcing related patch maybe later added when the EPLL etc clock
> support has been submitted.
Nope, the extant driver can do slave mode, all you need to do is write
the correct codec<>dai driver and it will do it.
--
Ben
Q: What's a light-year?
A: One-third less calories than a regular year.
next prev parent reply other threads:[~2009-09-02 19:09 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-02 3:17 Samsung S3C6410 mainline merge coordination Harald Welte
2009-09-02 9:51 ` Nelson Castillo
2009-09-02 12:15 ` Harald Welte
2009-09-02 15:58 ` Nelson Castillo
2009-09-02 10:05 ` Mark Brown
2009-09-02 12:11 ` Harald Welte
2009-09-02 13:44 ` jassi brar
2009-09-02 14:47 ` Mark Brown
2009-09-03 0:38 ` jassi brar
2009-09-03 12:14 ` Mark Brown
2009-09-03 13:39 ` jassi brar
2009-09-03 15:18 ` Mark Brown
2009-09-04 1:08 ` jassi brar
2009-09-04 13:41 ` Mark Brown
2009-09-04 14:27 ` jassi brar
2009-09-04 14:57 ` Mark Brown
2009-09-04 1:27 ` Samsung SoC ASOC drivers Harald Welte
2009-09-04 4:10 ` jassi brar
2009-09-02 19:09 ` Ben Dooks [this message]
2009-09-03 0:21 ` Samsung S3C6410 mainline merge coordination Joonyoung Shim
2009-09-03 11:06 ` Mark Brown
2009-09-03 12:48 ` Joonyoung Shim
2009-09-02 13:45 ` Mark Brown
2009-09-02 19:22 ` Ben Dooks
[not found] ` <19987914.1168001251884594226.JavaMail.coremail@bj126app54.126.com>
2009-09-02 12:01 ` Harald Welte
2009-09-02 19:10 ` Ben Dooks
2009-09-02 22:26 ` Harald Welte
2009-09-03 9:51 ` Daniel Silverstone
2009-09-03 10:34 ` Russell King - ARM Linux
2009-09-03 10:40 ` Daniel Silverstone
2009-09-04 5:48 ` Pavel Machek
2009-09-02 12:03 ` David F. Carlson
2009-09-02 12:46 ` Peter Korsgaard
2009-09-02 19:16 ` Ben Dooks
2009-09-03 1:56 ` Harald Welte
2009-09-03 10:04 ` Peter Korsgaard
2009-09-03 10:57 ` Mark Brown
[not found] ` <7641737.122161251944382753.JavaMail.coremail@bj126app17.126.com>
2009-09-03 4:31 ` Harald Welte
2009-09-10 5:49 ` Samsung S3C6410 / SmartQ / 2D acceleration / Xorg Harald Welte
2009-09-15 23:34 ` Ben Dooks
2009-09-15 9:49 ` Samsung S3C6410 / SmartQ / 2D acceleration / Xorgy David F. Carlson
2009-09-02 12:49 ` Samsung S3C6410 mainline merge coordination Peter Korsgaard
2009-09-02 22:30 ` Harald Welte
2009-09-02 16:12 ` Ben Dooks
2009-09-02 21:25 ` David F. Carlson
2009-09-02 23:18 ` Harald Welte
2009-09-03 3:31 ` Bill Gatliff
2009-09-03 3:38 ` Nelson Castillo
2009-09-03 4:33 ` Harald Welte
2009-09-04 7:15 ` Nelson Castillo
2009-09-02 16:58 ` Mark Brown
[not found] <23992600.419641251935757361.JavaMail.weblogic@epml11>
2009-09-03 0:46 ` Harald Welte
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=20090902190934.GN25153@trinity.fluff.org \
--to=ben@trinity.fluff.org \
--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).