From: jassi brar <jassisinghbrar@gmail.com>
To: Kyungmin Park <kmpark@infradead.org>
Cc: alsa-devel@alsa-project.org,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
Jassi Brar <jassi.brar@samsung.com>,
Ben Dooks <ben-linux@fluff.org>
Subject: Re: Reforming S3C I2S towards supporting I2Sv4
Date: Sun, 2 May 2010 17:28:03 +0900 [thread overview]
Message-ID: <z2t1b68c6791005020128n5c501797n61ebd15466ac683e@mail.gmail.com> (raw)
In-Reply-To: <i2w9c9fda241005012138j844af741va32948bb0971b77@mail.gmail.com>
On Sun, May 2, 2010 at 1:38 PM, Kyungmin Park <kmpark@infradead.org> wrote:
> Do you have a plan to move or create the sound/soc/samsung or others
> for future Samsung SoCs?
I don't have any such plan atm, but I am not against moving sound/soc/s3c24xx
to sound/soc/samsung
> And can you make a document which SoCs use I2S version?
> e.g.,
> s3c24xx use I2Sv3
> s3c64xx use I2Sv3 or 4??
> s5p64xx use I2Sv4
> s5pc1xx use I2Sv5
> and so on
>
> How about to give name samsung-i2cvx for common use instead of cpu name?
>
I think it is better to call drivers by the first soc that is supported
in mainline. Any new soc, that has the controller reused, should be handled
by the same old driver. For example, if we have driver for s5pc100, then
let s5pc110/v210 use the same s5pc100-i2s.c That is, after soc support
in current drivers is sorted out.
prev parent reply other threads:[~2010-05-02 8:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-10 7:48 Reforming S3C I2S towards supporting I2Sv4 Jassi Brar
2010-03-10 8:24 ` Liam Girdwood
2010-03-10 8:31 ` jassi brar
2010-03-10 9:04 ` Liam Girdwood
2010-03-10 9:22 ` jassi brar
2010-03-10 10:18 ` Mark Brown
2010-03-10 8:35 ` jassi brar
2010-03-10 8:51 ` Liam Girdwood
2010-03-10 9:02 ` jassi brar
2010-03-10 10:20 ` Mark Brown
2010-03-10 14:23 ` Mark Brown
2010-04-06 0:33 ` jassi brar
2010-04-27 2:10 ` jassi brar
2010-04-27 2:58 ` Ben Dooks
2010-04-27 4:25 ` jassi brar
2010-05-02 4:38 ` Kyungmin Park
2010-05-02 8:28 ` 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=z2t1b68c6791005020128n5c501797n61ebd15466ac683e@mail.gmail.com \
--to=jassisinghbrar@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=ben-linux@fluff.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=jassi.brar@samsung.com \
--cc=kmpark@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).