From: Mark Brown <broonie@kernel.org>
To: "Ali Burak Parım" <aliburakparim@gmail.com>
Cc: maxime.ripard@bootlin.com, linux-arm-kernel@lists.infradead.org
Subject: Re: Best representation for TDM devices
Date: Wed, 14 Aug 2019 17:02:34 +0100 [thread overview]
Message-ID: <20190814160234.GG4640@sirena.co.uk> (raw)
In-Reply-To: <CAMTEBE2L6KXH6JW2Z_6RSKdtFJc9ncFvfakwW_Vm88BCGC6aeQ@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1458 bytes --]
On Wed, Aug 14, 2019 at 12:53:24PM +0200, Ali Burak Parım wrote:
> On Thu, 1 Aug 2019 at 13:48, Mark Brown <broonie@kernel.org> wrote:
> > On Thu, Aug 01, 2019 at 01:43:06PM +0200, Ali Burak Parım wrote:
> > > On Thu, Jul 25, 2019 at 03:01:12PM +0200, Maxime Ripard wrote:
> > > Hardware is a custom board I designed with 4 PDM output microphones
> > > and 2 adau7002 devices as the codec for PDM-to-PCM. We want to do
> > > signal processing with this board. Therefore having separate streams for
> > > each microphone is crucial to the application though I am not sure where
> > > we should implement this exactly.
> > What is this processing - are the streams from these microphones
> > logically related in any way (eg, is this a microphone array)? There's
> Yes, it is a microphone array application for speech enhancement. Thus,
> signal levels and physical time delays are important.
> > probably going to be some overlap in the input signals at least. If you
> > need to for example correlate different microphones then that's
> > relevant.
> Yes, we correlate different microphone signals in some of our algorithms.
OK, in that case I'd recommend providing them to userspace as a single
four channel stream - keeping everything bundled together as long as
possible to make it easier to keep the processing synced up.
> P.S.: I am so sorry for late reply, the thread went to my junk box somehow.
No problem.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-08-14 16:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAMTEBE0mPY=44txPC2G+Cb=NqeH6Cqesar9Vkq0afXBv4dUWHQ@mail.gmail.com>
2019-08-01 11:48 ` Best representation for TDM devices Mark Brown
2019-08-14 10:53 ` Ali Burak Parım
2019-08-14 16:02 ` Mark Brown [this message]
2019-08-19 8:41 ` Maxime Ripard
2019-08-19 15:45 ` Mark Brown
2019-08-20 14:06 ` Maxime Ripard
2019-07-25 13:01 Maxime Ripard
2019-07-25 17:44 ` 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=20190814160234.GG4640@sirena.co.uk \
--to=broonie@kernel.org \
--cc=aliburakparim@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=maxime.ripard@bootlin.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).