From: Peter Ujfalusi <peter.ujfalusi@ti.com>
To: Belisko Marek <marek.belisko@gmail.com>,
jarkko.nikula@bitmer.com, lgirdwood@gmail.com,
broonie@kernel.org, alsa-devel@alsa-project.org
Cc: "Dr. H. Nikolaus Schaller" <hns@goldelico.com>
Subject: Re: dummy codec + simple card combination
Date: Fri, 13 Mar 2015 11:28:57 +0200 [thread overview]
Message-ID: <5502ADD9.9070603@ti.com> (raw)
In-Reply-To: <CAAfyv36tTpvWgrKaMySdfYnBcoSAr64NzAH6fCsNt2MN5PX3wg@mail.gmail.com>
Hi,
On 03/12/2015 08:33 PM, Belisko Marek wrote:
> Hi,
>
> I posted same question on alsa-devel ML this week but I forgot to add
> sound omap + asoc maintainers (sorry about that)
>
> I'm trying to add audio support for gta04 (for gsm + bt and fm audio).
> All audio sources are clock masters so basically connection is dummy
> codecs -> cpu dai (mcbsp ports).
The FM seams to be slave device (Si4705/Si4721) on the I2S bus.
But in any of the cases (FM, GSM and BT) how do you configure the DAI formats
of the 'codecs'? Si47xx has support for I2S, L_JUST and DSP mode for example.
What about the sample formats and rates?
I think there should be a driver for at least the FM. For BT there is a bt-sco
codec driver but w/o DT support.
> For implementing such thing I can see 2 options:
> 1. simple card driver which can easily describe cpu dai interface but
> dummy codec cannot because there are no DT bindings (there was sever
> attempts to add DT bindings for dummy-codec but AFAIK none was
> accepted)
Yes, the dummy-codec is Linux/ASoC concept and should not be described in DT.
However I think there should be a way to describing passive DAIs. Slave
devices only listening, or masters streaming the data.
But, I think even if you have such a device you do have some control, at least
to enable/disable them...
> This turns it to only solution to create gta04 soundcard which will
> get from DT cpu dai links and use in card driver dummy codecs
> directly.
I would look up the driver for the FM and write the codec driver for it,
probably the same can be done for the GSM and add bindings for the bt-sco so
all of this can work with simple-card.
Or write a custom machine driver and get it done ;)
> 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
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2015-03-13 9:29 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 [this message]
2015-03-13 9:54 ` Dr. H. Nikolaus Schaller
2015-03-17 14:07 ` Peter Ujfalusi
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=5502ADD9.9070603@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox