ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Sebastian Reichel <sre@kernel.org>
To: Pavel Machek <pavel@ucw.cz>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [TECH TOPIC] mobile phones
Date: Wed, 28 Jun 2017 18:01:12 +0200	[thread overview]
Message-ID: <20170628160112.ip2ambkzlkkoz2ww@earth> (raw)
In-Reply-To: <20170627215727.GA5250@amd>

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

Hi,

On Tue, Jun 27, 2017 at 11:57:27PM +0200, Pavel Machek wrote:
> Hi!
> 
> > > > Is GSM connected directly to the audio, or does it need real-time
> > > > task, similar to N900?
> > > 
> > > The audio mixer is on CPCAP PMIC, and I think mdm6600 modem audio needs
> > > help from the Linux kernel on the applications processor as it probably
> > > goes to it first then to CPCAP PMIC. I guess it's possible that mdm6600
> > > audio goes directly to CPCAP PMIC too.
> > > 
> > > I believe LTE modem is connected to the second SPI interface on the
> > > CPCAP PMIC and can use it directly for audio depending on how Linux
> > > kernel configures the PMIC secondary interface device access. What
> > > seems to be a similar PMIC for the CPCAP internal devices is documented
> > > in MC13783UG.pdf on NXP site so that might be worth looking at for
> > > the audio overview.
> > 
> > GSM audio is connected to the audio codec using digital audio
> > interface. The audio data normally does not flow through the CPU
> > (but as far as I can see it could be routed that way, if desired).
> > So no need for any low latency stuff on CPU side. Actually no need
> > to do anything except for proper setup of modem & audio codec :)
> 
> Thanks. Droid 4 just got more desirable ;-).
>
> > > > It looks like nice machine. OTOH N950 looks like a nice machine, too,
> > > > and N900 is actually nicer because of the resistive touch, battery,
> > > > and friendly bootloader...
> > > 
> > > Sure, my n950 just got so worn down I was afraid I don't have any
> > > replacement. And we need some kind of potential community upgrade for
> > > n900/n9/n950 anyways while waiting for better devices :)
> > 
> > I think Droid4 and N950 are almost on par regarding to mainline
> > support. N900 is has better hardware support in mainline - actually
> > once your camera bits land it reached basically 100% with just the
> > GPU missing. OTOH it's quite slow and has only 256MB of memory.
> 
> Well, the camera pieces only work with 1.2Mpix resolution... and still
> need a ton of userland code to be useful. But yes, major pieces are
> there, with exception of ... useful audio for voice calls (and tons of
> little omissions and flakiness and bugs).
> 
> Oh, another major piece is DSP coprocessor that is there. Unlike
> graphics, we don't even know how support for it should like.

https://www.kernel.org/doc/Documentation/remoteproc.txt

config OMAP_REMOTEPROC
	tristate "OMAP remoteproc support"
	[...]
	help
	  Say y here to support OMAP's remote processors (dual M3
	  and DSP on OMAP4) via the remote processor framework.

	  Currently only supported on OMAP4.

	  Usually you want to say Y here, in order to enable multimedia
	  use-cases to run on your platform (multimedia codecs are
	  offloaded to remote DSP processors using this framework).

	  It's safe to say N here if you're not interested in multimedia
	  offloading or just want a bare minimum kernel.

I have been told by some Nokia people (I do not remember who it
was, possibly Sakari), that the DSP is not that powerful and any
calculation should also be possible on CPU (wasting a bit of energy).

> And actually, N950 has working Bluetooth, which gives some
> interesting possibilities, too.

Patches for bluetooth on Droid4 are in -next :)

-- Sebastian

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

  reply	other threads:[~2017-06-28 16:01 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 [this message]
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
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=20170628160112.ip2ambkzlkkoz2ww@earth \
    --to=sre@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