From: Chanwoo Choi <cw00.choi@samsung.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: alsa-devel@alsa-project.org,
Joonyoung Shim <jy0922.shim@samsung.com>,
Jassi Brar <jassisinghbrar@gmail.com>,
Chanwoo Choi <cw00.choi@samsung.com>,
Kyungmin Park <kyungmin.park@samsung.com>,
Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: [PATCH] ASoC: SAMSUNG: Add Aquila sound driver
Date: Mon, 12 Jul 2010 16:23:57 +0900 [thread overview]
Message-ID: <4C3AC30D.2000107@samsung.com> (raw)
In-Reply-To: <4C369DA7.6070902@samsung.com>
Dear Mark,
Liam reviewed this patch.(Thank you for your review.)
The upstream kernel include i2s CPU drivers excepts for i2sv5 CPU driver.
I should upgrade existing i2s CPU drivers to support i2s operation
for sound on Aquila board, becuase the sound driver on Aquila board
to need i2sv5 CPU driver.
I have a question.
After upgrading existing i2s CPU drivers to run sound on Aquila board,
Should I post this patch to upstream kernel?
Or,
Now, I post this patch which haven't used i2sv5 CPU driver to upstream kernel.
Then, I will implement it and post incremental patch using it to run
on Aquila board.
Could you give me the opinion about this question?
Thank you,
Chanwoo Choi
next prev parent reply other threads:[~2010-07-12 7:24 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
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 [this message]
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=4C3AC30D.2000107@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 \
--cc=lrg@slimlogic.co.uk \
/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.