From: Chanwoo Choi <cw00.choi@samsung.com>
To: Jassi Brar <jassisinghbrar@gmail.com>
Cc: Chanwoo Choi <cw00.choi@samsung.com>,
alsa-devel@alsa-project.org,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
Kyungmin Park <kyungmin.park@samsung.com>,
Joonyoung Shim <jy0922.shim@samsung.com>
Subject: Re: [PATCH] ASoC: SAMSUNG: Add Aquila sound driver
Date: Fri, 09 Jul 2010 10:06:56 +0900 [thread overview]
Message-ID: <4C367630.3090607@samsung.com> (raw)
In-Reply-To: <AANLkTinKT2LvSrfcI2-aw2iXnnCe1R_jCfq09rxlNa3x@mail.gmail.com>
Jassi Brar wrote:
> The gpio config stuff needs to be removed from the CPU driver. It was pending
> due to fear of cross-tree merge issues. The platform specific code to do the
> same is already upstream now.
What is "platform specific code to the same" ?
> One engineer in my team is already looking into it while testing
> Liam's multi-codec
> changes.
>
>>> Please try to use the existing sound/soc/s3c24xx/s3c64xx-i2s-v4.c
> 'try to' is the key word here. The driver is not expected to work rightaway.
> One might need to make some changes to the CPU driver to just make it
> work on platforms with very similar IP.
Do you mean that I should implement i2sv5 drvier refer to the
sound/soc/s3c24xx/s3c64xx-i2s-v4.c after completing cross-tree merge issue?
Thank you,
Chanwoo Choi
next prev parent reply other threads:[~2010-07-09 1:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-08 4:57 [PATCH] ASoC: SAMSUNG: Add Aquila sound driver Chanwoo Choi
2010-07-08 5:52 ` Jassi Brar
2010-07-08 8:10 ` Chanwoo Choi
2010-07-08 8:19 ` Jassi Brar
2010-07-09 1:06 ` Chanwoo Choi [this message]
2010-07-09 2:17 ` Jassi Brar
2010-07-08 7:05 ` Mark Brown
2010-07-09 2:21 ` Chanwoo Choi
2010-07-09 2:42 ` Mark Brown
2010-07-09 3:55 ` Chanwoo Choi
2010-07-12 7:23 ` Chanwoo Choi
2010-07-12 9:41 ` Mark Brown
2010-07-09 9:15 ` Liam Girdwood
-- strict thread matches above, loose matches on Subject: below --
2010-07-07 8:41 최찬우
2010-07-07 13:36 ` Mark Brown
2010-07-08 1:51 ` 최찬우
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=4C367630.3090607@samsung.com \
--to=cw00.choi@samsung.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=jassisinghbrar@gmail.com \
--cc=jy0922.shim@samsung.com \
--cc=kyungmin.park@samsung.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 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.