From: Lars-Peter Clausen <lars@metafoo.de>
To: Kuninori Morimoto <kuninori.morimoto.gx@gmail.com>,
Mark Brown <broonie@kernel.org>
Cc: Linux-ALSA <alsa-devel@alsa-project.org>,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Subject: Re: simle-card DT style for DPCM
Date: Mon, 08 Sep 2014 09:39:23 +0200 [thread overview]
Message-ID: <540D5D2B.5080504@metafoo.de> (raw)
In-Reply-To: <877g1fotdd.wl%kuninori.morimoto.gx@gmail.com>
On 09/08/2014 02:20 AM, Kuninori Morimoto wrote:
>
> Hi Mark
>
>>> I wonder how to know it in driver ?
>>> (How to switch normal <-> FE/BE ?, and how to know FE or BE ?)
>>> Can you show me objectivization example / idea ?
>>
>> Surely we can just put a data table or two in there with all the routing
>> inside the IP in the same way that we handle routing within CODECs? It
>> doesn't seem like a fundamentally different problem.
>
> We can use this idea inside C code,
> then, we need decide to use it or not use it somehow ?
> We can do everything in C code, I have no concern about it.
> But, my main concern is that how to decide this switching from DT file.
> How to decide to use this "data table" ?
> Does this mean you can accept new compatible ?
>
> compatible = "simple-audio-card"; # normal simple-card
>
> compatible = "soc-audio-card"; # special sound card
> # we use DPCM this time
If there is no difference in hardware there shouldn't be any difference in
the hardware description.
Lets try to get to the bottom of the problem. Why do you want to enable DPCM
on some cards and not enable it on others?
- Lars
next prev parent reply other threads:[~2014-09-08 7:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-01 0:35 simle-card DT style for DPCM Kuninori Morimoto
2014-09-01 14:30 ` Mark Brown
2014-09-02 1:28 ` Kuninori Morimoto
2014-09-02 11:34 ` Mark Brown
2014-09-03 0:11 ` Kuninori Morimoto
2014-09-05 15:55 ` Mark Brown
2014-09-08 0:20 ` Kuninori Morimoto
2014-09-08 7:39 ` Lars-Peter Clausen [this message]
2014-09-08 8:50 ` Kuninori Morimoto
2014-09-09 11:51 ` Mark Brown
2014-09-10 0:18 ` Kuninori Morimoto
2014-09-03 5:17 ` Kuninori Morimoto
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=540D5D2B.5080504@metafoo.de \
--to=lars@metafoo.de \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=kuninori.morimoto.gx@gmail.com \
--cc=kuninori.morimoto.gx@renesas.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).