All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Ujfalusi <peter.ujfalusi@ti.com>
To: "Dr. H. Nikolaus Schaller" <hns@goldelico.com>
Cc: Belisko Marek <marek.belisko@gmail.com>,
	alsa-devel@alsa-project.org, broonie@kernel.org,
	lgirdwood@gmail.com, jarkko.nikula@bitmer.com
Subject: Re: dummy codec + simple card combination
Date: Tue, 17 Mar 2015 16:07:25 +0200	[thread overview]
Message-ID: <5508351D.7050304@ti.com> (raw)
In-Reply-To: <7087ED0D-9625-48EA-9012-A6A05869E014@goldelico.com>

On 03/13/2015 11:54 AM, Dr. H. Nikolaus Schaller wrote:
> 
> For GSM there is some special logic for tri-stating a DAI because the
> audio channel is wired to the twl4030 *and* a McBSP. This is for either
> routing the voice directly to the twl or through the CPU (and some filters,
> answering machine, sound scrambling etc.). This needs tri-state support
> of the McBSP DX line.
> 
>> Or write a custom machine driver and get it done ;)
> 
> If you would find time (which is beyond what we can realistically expect) to look
> into the non-DT 3.12 kernel where everything works, it would be here:
> 
> http://git.goldelico.com/?p=gta04-kernel.git;a=tree;f=sound/soc/omap;hb=HEAD
> 
> Basically we want to rebuild this using DT and use as much standard pieces
> as possible. So that we only need to upstream what is missing for full gta04
> support.

I see. You have had written dummy codecs for the GSM, BT, the FM had an actual
working driver.

Hrm. There is one thing which would make sense for these audio devices:
Since you do not have control over them in terms of formats, rates and
protocol - they use fixed interfaces.

I think it would make sense to have binding for something like:
compatible = "fixed-codec" or something like that, implying that it's
configuration can not be changed.
In it's bindings you would have the supported properties of the interface,
like rate, channels, sample width, protocol on the bus (I2S, DSP, etc) and to
indicate if it is bus master or slave.

You could use this 'fixed-codec' to describe the DAIs and use simple-card to
connect them with the CPU.

I think this will fill in some gaps and it is actually going to describe the
HW you have as well, so it is not Linux specific.

> 
>>
>>> Is my assumption correct? I would like to get some feedback before
>>> wasting my time with implementing something which cannot be pushed
>>> mainline. Thanks for all suggestions.
>>>
>>> BR,
>>>
>>> marek
>>>
>>> --
>>> as simple and primitive as possible
>>> -------------------------------------------------
>>> Marek Belisko - OPEN-NANDRA
>>> Freelance Developer
>>>
>>> Ruska Nova Ves 219 | Presov, 08005 Slovak Republic
>>> Tel: +421 915 052 184
>>> skype: marekwhite
>>> twitter: #opennandra
>>> web: http://open-nandra.com
>>>
>>
>>
>> -- 
>> Péter
> 
> BR,
> Nikolaus
> 


-- 
Péter

  reply	other threads:[~2015-03-17 14:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-10 20:35 dummy codec + simple card combination Belisko Marek
2015-03-12 18:33 ` Belisko Marek
2015-03-13  9:28   ` Peter Ujfalusi
2015-03-13  9:54     ` Dr. H. Nikolaus Schaller
2015-03-17 14:07       ` Peter Ujfalusi [this message]
2015-04-01 21:08         ` Belisko Marek
2015-04-02  5:11           ` Jean-Francois Moine
2015-04-02 20:24             ` Belisko Marek
2015-04-03  8:45               ` Jean-Francois Moine
2015-04-03 12:29                 ` Belisko Marek

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=5508351D.7050304@ti.com \
    --to=peter.ujfalusi@ti.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=hns@goldelico.com \
    --cc=jarkko.nikula@bitmer.com \
    --cc=lgirdwood@gmail.com \
    --cc=marek.belisko@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 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.