From: Ayaka <ayaka@soulik.info>
To: Mark Brown <broonie@kernel.org>
Cc: alsa-devel@alsa-project.org, sbkim73@samsung.com,
s.nawrocki@samsung.com, lgirdwood@gmail.com, perex@perex.cz,
tiwai@suse.com, krzk@kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ASoC: samsung: make audio interface/controller explicitly
Date: Mon, 19 Sep 2016 17:41:50 +0800 [thread overview]
Message-ID: <1BBB8B7D-0C1B-48E0-A516-402515A04568@soulik.info> (raw)
In-Reply-To: <20160919083342.GE10189@sirena.org.uk>
從我的 iPad 傳送
> Mark Brown <broonie@kernel.org> 於 2016年9月19日 下午4:33 寫道:
>
>> On Sun, Sep 18, 2016 at 10:09:11PM +0800, Randy Li wrote:
>>
>> It is simple sound card time, we could assign different codec
>> to a interface without making a specific driver for it.
>
>> config SND_SAMSUNG_AC97
>> - tristate
>> + tristate "Samsung AC97 controller support"
>> select SND_SOC_AC97_BUS
>
> Are you *sure* simple-card works for AC'97?
Not sure. I could hardly find a AC97 device in embedded market. If it didn't I could disable it. I have only tested simple sound card for i2s and SPDIF.
next prev parent reply other threads:[~2016-09-19 9:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-18 14:09 [PATCH] make samsung interface entries explicitly Randy Li
2016-09-18 14:09 ` [PATCH] ASoC: samsung: make audio interface/controller explicitly Randy Li
2016-09-18 14:42 ` Krzysztof Kozlowski
2016-09-18 15:12 ` ayaka
2016-09-18 18:09 ` Krzysztof Kozlowski
2016-09-19 1:21 ` Ayaka
2016-09-19 15:15 ` Krzysztof Kozlowski
2016-09-18 17:27 ` kbuild test robot
2016-09-19 1:42 ` kbuild test robot
2016-09-19 8:33 ` Mark Brown
2016-09-19 9:41 ` Ayaka [this message]
2016-09-19 10:23 ` Mark Brown
2016-09-19 8:33 ` [PATCH] make samsung interface entries explicitly Mark Brown
2016-09-19 15:51 [PATCH] ASoC: samsung: make audio interface/controller explicitly Randy Li
2016-09-19 16:37 ` Krzysztof Kozlowski
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=1BBB8B7D-0C1B-48E0-A516-402515A04568@soulik.info \
--to=ayaka@soulik.info \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=krzk@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=perex@perex.cz \
--cc=s.nawrocki@samsung.com \
--cc=sbkim73@samsung.com \
--cc=tiwai@suse.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).