From: ivo.g.dimitrov.75@gmail.com (Ivaylo Dimitrov)
To: linux-arm-kernel@lists.infradead.org
Subject: N900 modem support in 3.18-rc1
Date: Fri, 14 Nov 2014 21:54:42 +0200 [thread overview]
Message-ID: <54665E02.8050108@gmail.com> (raw)
In-Reply-To: <20141114172008.GB12250@earth.universe>
On 14.11.2014 19:20, Sebastian Reichel wrote:
>
> The patch looks ok. It does not cleanup the cmt-speech driver for
> mainline usage, but it should work. Before adding this driver to the
> mainline kernel there should be open source userspace support anyway.
>
I am aware of that(patch not ready), it's one of the reasons this patch
still sits on gitorious IMO.
libcmtspeechdata was opened by Nokia long ago, so I don't understand
what userspace support (for inclusion of the driver in the mainline
kernel that is) is needed. see
https://gitorious.org/meego-cellular/libcmtspeechdata/source/7f8f3ce357513e4849e1bf6d657980a514529c1a:
REed pulseaudio modules that use cmtspeech will be ready sooner than
later (I believe in 2-3 monts from now), see on gitorious how fast we
progressed with -record and -music modules. Sure, -voice module is way
more complicated, but lots of it is already opensourced, we just need to
figure out a couple of DSP algorithms(drc, agc, aec, etc) related to
call quality. But I don't think the driver should wait for those modules
to be REed, they can be used as is even now, in their closed form for
testing. Unfortunately all my spare time is dedicated to that PA stuff,
so I simply can't cleanup cmtspeech driver and send a patch for
upstreaming. (Pavel, what about you?)
> Btw. I am aware that this would break existing pulse audio stuff,
> but wouldn't it make sense to export a V4L2 device instead of the
> custom /dev/cmt_speech ABI?
>
Nokia PA guys did a great job integrating lots of things related to
audio and honestly, I don't see a reason why should we reinvent the
wheel. There is lot more behind the scenes than simple PCM streaming
(like audio policies and routing, sideband audio, speakers protection,
etc) and reiplementing all this using different API wouldn't worth it IMO.
Not to say that I agree with Pali's reply that working userspace should
not be broken just for the sake of it.
Ivo
next prev parent reply other threads:[~2014-11-14 19:54 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-04 20:51 N900 modem support in 3.18-rc1 Pavel Machek
2014-11-05 1:11 ` Sebastian Reichel
2014-11-05 20:31 ` Pavel Machek
2014-11-05 20:37 ` Pali Rohár
2014-11-05 20:39 ` Pavel Machek
2014-11-05 21:06 ` Pali Rohár
2014-11-05 22:03 ` Pavel Machek
2014-11-05 23:45 ` Sebastian Reichel
2014-11-06 12:47 ` Pavel Machek
2014-11-06 18:03 ` Sebastian Reichel
2014-11-06 22:50 ` Pavel Machek
2014-11-06 23:01 ` Pali Rohár
2014-11-07 7:04 ` Ivaylo Dimitrov
2014-11-13 16:24 ` Pavel Machek
2014-11-14 7:04 ` Ivaylo Dimitrov
2014-11-14 17:20 ` Sebastian Reichel
2014-11-14 17:34 ` Pali Rohár
2014-11-14 22:05 ` Sebastian Reichel
2014-11-14 19:54 ` Ivaylo Dimitrov [this message]
2014-11-14 21:14 ` Pavel Machek
2014-11-14 21:57 ` Sebastian Reichel
2014-11-20 10:13 ` voice calls on N900 working (off-line) was " Pavel Machek
2014-11-20 10:17 ` Pavel Machek
2014-11-25 23:21 ` GPRS data on N900 working " Pavel Machek
2015-02-11 18:32 ` Voice calls working on N900 (*) (was Re: N900 modem support in 3.18-rc1) Pavel Machek
2015-02-11 20:56 ` Pavel Machek
2014-11-13 16:21 ` N900 modem support in 3.18-rc1 Pavel Machek
2014-11-13 17:45 ` Tony Lindgren
2014-11-13 18:18 ` Aaro Koskinen
2014-11-16 10:12 ` Pavel Machek
2014-11-16 12:29 ` Robert Jarzmik
2014-11-18 7:42 ` Pavel Machek
2014-11-19 19:01 ` Robert Jarzmik
2014-11-14 7:37 ` Pavel Machek
2014-11-14 16:53 ` Sebastian Reichel
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=54665E02.8050108@gmail.com \
--to=ivo.g.dimitrov.75@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).