From: jy0922.shim@samsung.com (Joonyoung Shim)
To: linux-arm-kernel@lists.infradead.org
Subject: Samsung S3C6410 mainline merge coordination
Date: Thu, 03 Sep 2009 21:48:15 +0900 [thread overview]
Message-ID: <4A9FBB0F.8060006@samsung.com> (raw)
In-Reply-To: <20090903110652.GB2954@sirena.org.uk>
On 9/3/2009 8:06 PM, Mark Brown wrote:
> On Thu, Sep 03, 2009 at 09:21:02AM +0900, Joonyoung Shim wrote:
>> On 9/2/2009 10:44 PM, jassi brar wrote:
>
>>> S3C2410 has I2S-2.0, S3C6410 has I2S-3.2 and I2S-4.0, S5P6440 has
>>> I2S-4.0, S5PC100 has
>
>> I wonder what mean the numbers(2.0, 3.2, 4.0, 5.1). Does it mean I2S
>> version simply? If it is version, what is the differences of each I2S
>> version?
>
> It's just the version numbers for the IP blocks. The differences tend
> to be in the addition of new features to the blocks, plus occasional
> reorganisations of the register maps. For example, the v4.0 block added
> two extra data out lines for 5.1 audio support. Since you work at
I see. if we use the default feature only, i think the codes of mainline
can be reused because all I2S versions have basically the features of
I2S-2.0(S3C2410).
> Samsung I suspect your best bet for documentation on what's going on is
> to find an internal source - sadly the datasheets and other detailed
> collateral are not public but I'd expect that they are available within
> Samsung.
>
Right. Unfortunately i am not on Samsung LSI linux team, but I do
a related work on other team.
next prev parent reply other threads:[~2009-09-03 12:48 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 ` Samsung S3C6410 mainline merge coordination Ben Dooks
2009-09-03 0:21 ` Joonyoung Shim
2009-09-03 11:06 ` Mark Brown
2009-09-03 12:48 ` Joonyoung Shim [this message]
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=4A9FBB0F.8060006@samsung.com \
--to=jy0922.shim@samsung.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.