ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Sebastian Reichel <sebastian.reichel@collabora.co.uk>
To: Mark Brown <broonie@kernel.org>
Cc: ksummit-discuss@lists.linuxfoundation.org, Pavel Machek <pavel@ucw.cz>
Subject: Re: [Ksummit-discuss] [TECH TOPIC] mobile phones
Date: Tue, 27 Jun 2017 13:41:22 +0200	[thread overview]
Message-ID: <20170627114122.glrzwray6oi34jla@earth> (raw)
In-Reply-To: <20170626105451.tv4k7ib2g2kiknah@sirena.org.uk>

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

Hi,

On Mon, Jun 26, 2017 at 11:54:51AM +0100, Mark Brown wrote:
> On Sun, Jun 25, 2017 at 12:48:50PM +0200, Pavel Machek wrote:
> 
> > 2) How to handle GSM audio?
> 
> Do you have some more specific concern?  This already works basically
> fine upstream, we happily support off-SoC audio paths.  The digital
> configuration could do with being more flexible but it works and people
> ship it.  It would be awfully nice to have some control/visibility of
> the modem side but that's just a missing driver problem.

This is not a general problem, but only with the Nokia phones,
which sends raw audio data to the CPU. Nokia's userspace did
postprocessing on DSP and then played the audio via pulseaudio.
As you mentioned this requires a low latency setup of ~20ms.

@Pavel: The Nokia phones are the only ones I'm aware of, that
are implemented this way. Basically all other phones provide
a normal digital audio interface. On those systems you only
have to configure soundcard correctly and will have working
audio.

And as Mark mentioned modern 4G basically uses VoIP, so if some
vendor decides to drop audio handling from modem again it can
simply be done in userspace using normal VoIP application.

-- Sebastian

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2017-06-27 11:50 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-25 10:48 Pavel Machek
2017-06-25 23:55 ` NeilBrown
2017-06-26  6:43   ` Geert Uytterhoeven
2017-06-26  6:49   ` Tony Lindgren
2017-06-26 11:12     ` Pavel Machek
2017-06-26 11:49       ` Tony Lindgren
2017-06-26 13:14         ` Pavel Machek
2017-06-26 13:49           ` Tony Lindgren
2017-06-26 20:49             ` Pavel Machek
2017-06-27  7:18               ` Tony Lindgren
2017-06-27 12:14                 ` Sebastian Reichel
2017-06-27 21:57                   ` Pavel Machek
2017-06-28 16:01                     ` Sebastian Reichel
2017-06-28 20:27                       ` Pavel Machek
2017-07-02 12:03                         ` Sebastian Reichel
2017-06-27 21:57                 ` Pavel Machek
2017-06-26  8:34   ` Pavel Machek
2017-06-26 11:20     ` Mark Brown
2017-06-26 12:22       ` Pavel Machek
2017-06-27 11:40         ` Mark Brown
2017-06-28 18:37           ` Pavel Machek
2017-07-02 12:11             ` Sebastian Reichel
2017-06-26 22:23     ` Alexandre Belloni
2017-06-27  7:06       ` Pavel Machek
2017-06-27 12:39     ` Sebastian Reichel
2017-06-27 21:57       ` Pavel Machek
2017-06-28 16:45         ` Sebastian Reichel
2017-06-28 21:10           ` Pavel Machek
2017-07-02 11:28             ` Sebastian Reichel
2017-07-02 18:14               ` Pavel Machek
2017-06-26 10:54 ` Mark Brown
2017-06-26 11:14   ` Pavel Machek
2017-06-26 11:49     ` Mark Brown
2017-06-26 12:38       ` Pavel Machek
2017-06-26 16:34         ` Mark Brown
2017-06-27 11:41   ` Sebastian Reichel [this message]
2017-06-28 14:38 ` Linus Walleij
2017-06-28 15:58   ` Arnd Bergmann
2017-06-28 16:04     ` Laurent Pinchart
2017-06-28 16:25   ` Pavel Machek
2017-06-28 18:26     ` Mark Brown
2017-06-28 17:01   ` Pavel Machek
2017-06-28 19:03     ` Tony Lindgren

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=20170627114122.glrzwray6oi34jla@earth \
    --to=sebastian.reichel@collabora.co.uk \
    --cc=broonie@kernel.org \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --cc=pavel@ucw.cz \
    /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