All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: Koro Chen <koro.chen@mediatek.com>,
	robh+dt@kernel.org, matthias.bgg@gmail.com, perex@perex.cz,
	tiwai@suse.de, srv_heupstream@mediatek.com,
	linux-mediatek@lists.infradead.org, galak@codeaurora.org,
	lgirdwood@gmail.com, devicetree@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, alsa-devel@alsa-project.org
Subject: Re: [RESEND RFC PATCH 1/3] ASoC: mediatek: Add binding support for AFE driver
Date: Tue, 21 Apr 2015 11:14:16 +0100	[thread overview]
Message-ID: <20150421101416.GC22845@sirena.org.uk> (raw)
In-Reply-To: <20150421094926.GU6325@pengutronix.de>

[-- Attachment #1: Type: text/plain, Size: 939 bytes --]

On Tue, Apr 21, 2015 at 11:49:26AM +0200, Sascha Hauer wrote:

> I think this could be done. I checked the possible connections in the
> crossbar switch and it seems all memory interfaces can be connected with
> all relevant external interfaces. So indeed the memory interfaces could
> be dynamically allocated instead of statically associated to an
> external interface. There are two problems I see: Some memory interfaces
> are limited in the rates they support, they can only do 8k/16k/32k (for
> speech). How can we know such memory interface should be used? Also
> there are two programmable hardware gain blocks which can be inserted to
> the digital audio path using the crossbar switch. There must be some
> mechanism to configure them into different places.

This (particularly the gain controls) sounds like you want to expose the
routing to userspace and use DPCM, the code also seemed to look like it
was a good fit for DPCM.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: broonie@kernel.org (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [RESEND RFC PATCH 1/3] ASoC: mediatek: Add binding support for AFE driver
Date: Tue, 21 Apr 2015 11:14:16 +0100	[thread overview]
Message-ID: <20150421101416.GC22845@sirena.org.uk> (raw)
In-Reply-To: <20150421094926.GU6325@pengutronix.de>

On Tue, Apr 21, 2015 at 11:49:26AM +0200, Sascha Hauer wrote:

> I think this could be done. I checked the possible connections in the
> crossbar switch and it seems all memory interfaces can be connected with
> all relevant external interfaces. So indeed the memory interfaces could
> be dynamically allocated instead of statically associated to an
> external interface. There are two problems I see: Some memory interfaces
> are limited in the rates they support, they can only do 8k/16k/32k (for
> speech). How can we know such memory interface should be used? Also
> there are two programmable hardware gain blocks which can be inserted to
> the digital audio path using the crossbar switch. There must be some
> mechanism to configure them into different places.

This (particularly the gain controls) sounds like you want to expose the
routing to userspace and use DPCM, the code also seemed to look like it
was a good fit for DPCM.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20150421/e006ea93/attachment.sig>

  reply	other threads:[~2015-04-21 10:14 UTC|newest]

Thread overview: 59+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-10  8:14 [RESEND RFC PATCH 0/3] ASoC: Mediatek: Add support for MT8173 SOC Koro Chen
2015-04-10  8:14 ` [RESEND RFC PATCH 1/3] ASoC: mediatek: Add binding support for AFE driver Koro Chen
2015-04-18 17:34   ` Mark Brown
2015-04-18 17:34     ` Mark Brown
2015-04-20  4:37     ` Sascha Hauer
2015-04-20  4:37       ` Sascha Hauer
2015-04-20  4:37       ` Sascha Hauer
2015-04-20 20:48       ` Mark Brown
2015-04-20 20:48         ` Mark Brown
2015-04-20 20:48         ` Mark Brown
2015-04-21  9:49         ` Sascha Hauer
2015-04-21  9:49           ` Sascha Hauer
2015-04-21  9:49           ` Sascha Hauer
2015-04-21 10:14           ` Mark Brown [this message]
2015-04-21 10:14             ` Mark Brown
2015-04-21 10:15           ` Koro Chen
2015-04-21 10:15             ` Koro Chen
2015-04-21 10:15             ` Koro Chen
2015-04-21 10:56             ` Mark Brown
2015-04-21 10:56               ` Mark Brown
2015-04-22  3:17         ` Koro Chen
2015-04-22  3:17           ` Koro Chen
2015-04-22  3:17           ` Koro Chen
2015-04-30 20:12           ` Mark Brown
2015-04-30 20:12             ` Mark Brown
2015-04-30 20:12             ` Mark Brown
2015-05-04  1:57             ` Koro Chen
2015-05-04  1:57               ` Koro Chen
2015-05-04  1:57               ` Koro Chen
2015-04-10  8:14 ` [RESEND RFC PATCH 2/3] ASoC: mediatek: Add AFE connection control Koro Chen
2015-04-18 17:37   ` Mark Brown
2015-04-18 17:37     ` Mark Brown
2015-04-18 17:37     ` Mark Brown
2015-04-20  4:50     ` Sascha Hauer
2015-04-20  4:50       ` Sascha Hauer
2015-04-20  4:50       ` Sascha Hauer
2015-04-20 20:52       ` Mark Brown
2015-04-20 20:52         ` Mark Brown
2015-04-20 20:52         ` Mark Brown
2015-04-21  5:50         ` Sascha Hauer
2015-04-21  5:50           ` Sascha Hauer
2015-04-21  5:50           ` Sascha Hauer
2015-04-21 10:15           ` Mark Brown
2015-04-21 10:15             ` Mark Brown
2015-04-21 10:15             ` Mark Brown
2015-04-10  8:14 ` [RESEND RFC PATCH 3/3] ASoC: mediatek: Add AFE platform driver Koro Chen
2015-04-18 17:51   ` Mark Brown
2015-04-18 17:51     ` Mark Brown
2015-04-20  6:22     ` Koro Chen
2015-04-20  6:22       ` Koro Chen
2015-04-20  6:22       ` Koro Chen
2015-04-20 20:55       ` Mark Brown
2015-04-20 20:55         ` Mark Brown
2015-04-20 20:55         ` Mark Brown
2015-04-21  2:27         ` Koro Chen
2015-04-21  2:27           ` Koro Chen
2015-04-21  2:27           ` Koro Chen
2015-04-21 10:05           ` Mark Brown
2015-04-21 10:05             ` Mark Brown

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=20150421101416.GC22845@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=devicetree@vger.kernel.org \
    --cc=galak@codeaurora.org \
    --cc=koro.chen@mediatek.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=matthias.bgg@gmail.com \
    --cc=perex@perex.cz \
    --cc=robh+dt@kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=srv_heupstream@mediatek.com \
    --cc=tiwai@suse.de \
    /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.