alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Kyungmin Park <kmpark@infradead.org>
To: jassi brar <jassisinghbrar@gmail.com>
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 13:38:46 +0900	[thread overview]
Message-ID: <i2w9c9fda241005012138j844af741va32948bb0971b77@mail.gmail.com> (raw)
In-Reply-To: <q2x1b68c6791004262125o69932e63qd9ddc885b2627dd0@mail.gmail.com>

Hi Jassi,

Do you have a plan to move or create the sound/soc/samsung or others
for future Samsung SoCs?
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?

Thank you,
Kyungmin Park

On Tue, Apr 27, 2010 at 1:25 PM, jassi brar <jassisinghbrar@gmail.com> wrote:
> On Tue, Apr 27, 2010 at 11:58 AM, Ben Dooks <ben-linux@fluff.org> wrote:
>> On Wed, Mar 10, 2010 at 02:23:15PM +0000, Mark Brown wrote:
>>> On Wed, Mar 10, 2010 at 04:48:55PM +0900, Jassi Brar wrote:
>>>
>>> >  I have prepared some patches that debug and modify the behaviour of
>>> > extant S3C I2S support towards managing I2Sv4 controllers as well.
>>>
>>> OK, I think that's everything.  I've not applied anything after the
>>> header move yet due to the need for an ack from Ben.  Any patches I
>>> didn't specifically comment on are OK.  Overall it's all good, most of
>>> the issues are minor.
>>
>> I'd like to see a bit of header reformatting to make them readable
>> if they're not already merged.
> Ok.
>
>> the header moves are ok by me, much prefer to see them git mv'd than
>> copy and rm'd.
> Ok, I will move the header.
> Though the original plan was to create a copy in sound/soc/s3c24xx and
> render useless the one in plat-samsung/include/plat/ which could
> be independently removed from your tree. That was meant to avoid
> cross tree changes.
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
>

  reply	other threads:[~2010-05-02  4:38 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 [this message]
2010-05-02  8:28         ` 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=i2w9c9fda241005012138j844af741va32948bb0971b77@mail.gmail.com \
    --to=kmpark@infradead.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=ben-linux@fluff.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=jassi.brar@samsung.com \
    --cc=jassisinghbrar@gmail.com \
    /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).