From: Mark Brown <broonie@kernel.org>
To: Pavel Machek <pavel@ucw.cz>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [TECH TOPIC] mobile phones
Date: Mon, 26 Jun 2017 12:49:46 +0100 [thread overview]
Message-ID: <20170626114946.bw35etwxa2nungsi@sirena.org.uk> (raw)
In-Reply-To: <20170626111422.GB11688@amd>
[-- Attachment #1: Type: text/plain, Size: 1548 bytes --]
On Mon, Jun 26, 2017 at 01:14:22PM +0200, Pavel Machek wrote:
> > 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.
> Well, I was told gsm audio is different, because it is packetized, has
> additional timing info, and does not transmit silence.
Those things are true, however this is all handled inside the modem so
nothing else in the system sees anything there. Even if we were to see
things this is pretty much just VoIP over a funny carrier (some of the
4G standards are just SIP AIUI) which isn't too hard.
> So we have /dev/cmtspeech instead of second sound card.
That's just whatever random thing you're working on. It really
shouldn't be a second sound card on a well designed system, the phone
audio generally doesn't go anywhere near the CPU for latency reasons so
the whole system is one sound card.
> Is there any GSM audio driver that actually uses sound framework
> properly?
The modems tend to just be stub drivers to Linux as the audio port
doesn't vary configuration at runtime but I'd be a bit surprised if a
modern phone wasn't broadly aiming towards the right thing, this stuff
started appearing in flagship devices in about 2012. The speyside
system in mainline isn't actually a phone but models what's going on.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2017-06-26 11:49 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 [this message]
2017-06-26 12:38 ` Pavel Machek
2017-06-26 16:34 ` Mark Brown
2017-06-27 11:41 ` Sebastian Reichel
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=20170626114946.bw35etwxa2nungsi@sirena.org.uk \
--to=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