devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lars-Peter Clausen <lars@metafoo.de>
To: Qais Yousef <qais.yousef@imgtec.com>,
	Clemens Ladisch <clemens@ladisch.de>,
	linux-kernel@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	alsa-devel@alsa-project.org, Neil Jones <neil.jones@imgtec.com>,
	Arnd Bergmann <arnd@arndb.de>,
	devicetree@vger.kernel.org
Subject: Re: [alsa-devel] [PATCH 00/11] Add AXD Audio Processing IP driver
Date: Tue, 28 Oct 2014 17:04:07 +0100	[thread overview]
Message-ID: <544FBE77.4020009@metafoo.de> (raw)
In-Reply-To: <544FB763.6040904@imgtec.com>

On 10/28/2014 04:33 PM, Qais Yousef wrote:
> On 10/28/2014 02:54 PM, Lars-Peter Clausen wrote:
>> On 10/28/2014 02:18 PM, Qais Yousef wrote:
>>> On 10/28/2014 11:55 AM, Clemens Ladisch wrote:
>>>> Qais Yousef wrote:
>>>>> AXD Audio Processing IP performs audio decoding, encoding, mixing,
>>>>> equalisation,
>>>>> synchronisation and playback.
>>>> What exactly do you mean with "synchronisation" and "playback"?
>>>
>>> Synchronisation refers to accurate audio playout relative to a master
>>> clock source including compensation of drift between the master clock
>>> source and the playout clock of the audio hardware. Hence allowing
>>> synchronised audio playout across multiple independent devices.
>>>
>>> Playback simple refers to the fact that AXD is capable of managing audio
>>> playout hardware like I2S and SPDIF interfaces.
>>>
>>>
>>>>> It doesn't fit in alsa subsystem but I Cced them to confirm.
>>>> ... because those two words sound like something that a sound card could
>>>> do.
>>>
>>> The problem mainly stems from the fact that we take a variety of
>>> compressed audio as input and we could perform audio encoding. The
>>> problem with the compressed audio is that the range of decoders and
>>> configuration supported in alsa is limited and there's no support for
>>> taking raw pcm and producing compressed output. I'm not an expert on
>>> alsa but when I looked it looked like there's more infra structure
>>> required.
>>>
>>> [...]
>>
>> This doesn't sound to different from any of the other supported audio
>> DSPs. ALSA seems to have 95% of what you need. And the missing 5% is
>> probably stuff that is not specific to your hardware but rather something
>> that other hardware will need as well. The framework is not set in stone
>> you can make modifications and add the features that are missing to make
>> your hardware work.
>>
>> E.g. look at sound/soc/intel/ for an example of a audio DSP.
>>
>> No integrating this into ALSA will quite likely result in a quite messy
>> situation for you on the long run.
>>
>> - Lars
>>
>>
>>
> OK thanks for the reference. To be honest it felt like 15-20% of the
> features are missing but I'll need to look at the specifics and
> judge/estimate better.

Even then you'd want ALSA integration. You (or your customers) will 
eventually want to hook some external devices up to the I2S or SPDIF ports. 
All the drivers for the external devices are implemented in ALSA/ASoC.

- Lars

  reply	other threads:[~2014-10-28 16:04 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-28 11:26 [PATCH 00/11] Add AXD Audio Processing IP driver Qais Yousef
2014-10-28 11:26 ` [PATCH 02/11] dt: bindings: add AXD Audio Processing IP binding document Qais Yousef
2014-10-28 11:26 ` [PATCH 03/11] drivers: char: add AXD Audio Processing IP driver Qais Yousef
2014-10-28 14:10   ` Greg Kroah-Hartman
     [not found]     ` <20141028141038.GA18384-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2014-10-28 14:36       ` Qais Yousef
     [not found]         ` <544FA9F7.1020101-1AXoQHu6uovQT0dZR+AlfA@public.gmane.org>
2014-10-28 14:50           ` Greg Kroah-Hartman
2014-10-29  5:33   ` [alsa-devel] " Vinod Koul
2014-10-28 11:55 ` [PATCH 00/11] Add " Clemens Ladisch
2014-10-28 13:18   ` Qais Yousef
     [not found]     ` <544F97A4.7080209-1AXoQHu6uovQT0dZR+AlfA@public.gmane.org>
2014-10-28 14:13       ` Greg Kroah-Hartman
2014-10-28 15:05         ` Qais Yousef
2014-10-29  2:50           ` Greg Kroah-Hartman
2014-10-29  5:24             ` [alsa-devel] " Vinod Koul
2014-10-29 10:48               ` Qais Yousef
2014-10-29  5:20         ` Vinod Koul
2014-10-28 14:54     ` Lars-Peter Clausen
2014-10-28 15:33       ` Qais Yousef
2014-10-28 16:04         ` Lars-Peter Clausen [this message]
2014-10-29  5:18     ` [alsa-devel] " Vinod Koul
2014-10-29 15:06     ` Pierre-Louis Bossart
2014-10-28 12:06 ` Lars-Peter Clausen
2014-10-28 13:21   ` Qais Yousef

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=544FBE77.4020009@metafoo.de \
    --to=lars@metafoo.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=arnd@arndb.de \
    --cc=clemens@ladisch.de \
    --cc=devicetree@vger.kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neil.jones@imgtec.com \
    --cc=qais.yousef@imgtec.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).