From: Pavel Machek <pavel@ucw.cz>
To: Tony Lindgren <tony@atomide.com>
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org,
Jarkko Nikula <jarkko.nikula@bitmer.com>,
Johan Hovold <johan@kernel.org>,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
Marcel Partap <mpartap@gmx.net>,
Merlijn Wajer <merlijn@wizzup.org>,
Michael Scott <hashcode0f@gmail.com>, NeKit <nekit1000@gmail.com>,
omerlle@gmail.com, Sebastian Reichel <sre@kernel.org>,
Peter Ujfalusi <peter.ujfalusi@ti.com>,
Rob Herring <robh@kernel.org>
Subject: Re: WIP Droid 4 voice calls, GNSS & PM with a TS 27.010 serdev driver
Date: Sun, 23 Dec 2018 11:33:15 +0100 [thread overview]
Message-ID: <20181223103315.GA1936@amd> (raw)
In-Reply-To: <20181217004450.GW6707@atomide.com>
[-- Attachment #1: Type: text/plain, Size: 3019 bytes --]
Hi!
> So the little elves have been slowly working to get voice calls
> working on droid 4 with the mainline kernel. And just in time for the
> upcoming holidays, it might be possible to call friends and relatives.
>
> I've pushed out an experimental branch containing serdev ts 27.010
> UART multiplexing support. That contains a serdev core driver for the
> mdm6600 modem (that also now idles the modem for PM), support for Alsa
> ASoC voice codec and mixer, and a GNSS driver for the GPS.
>
> Where it does not make sense to do a kernel serdev driver, I've
> exposed the rest of the available 27.010 channels as ten /dev/motmdm*
> character devices. There's /dev/motmdm1 for AT commands to dial voice
> calls, /dev/motmdm3 for SMS eventually, and I think there's also a SIM
> card reader at /dev/motmdm10. Then /dev/motmdm7 seems to be just an
> echo channel. The other channels are still a bit of a mystery.
I suspected it does not work in non-modular case, so I tried with
modules:
root@devuan:/my/ko# insmod gnss.ko
root@devuan:/my/ko# insmod gnss-motmdm.ko
insmod: ERROR: could not insert module gnss-motmdm.ko: Unknown symbol
in module
root@devuan:/my/ko# insmod n_gsm.ko
root@devuan:/my/ko# insmod snd-soc-motmdm.ko
insmod: ERROR: could not insert module snd-soc-motmdm.ko: Unknown
symbol in module
root@devuan:/my/ko# insmod motorola-mdm.ko
root@devuan:/my/ko# insmod snd-soc-motmdm.ko
root@devuan:/my/ko# insmod gnss-motmdm.ko
root@devuan:/my/ko#
But...
root@devuan:/my/ko# ls -al /dev/motmdm*
ls: cannot access '/dev/motmdm*': No such file or directory
root@devuan:/my/ko# ls -al /dev/gnss*
ls: cannot access '/dev/gnss*': No such file or directory
root@devuan:/my/ko#
[ 116.244445] gnss: GNSS driver registered with major 242
[ 119.892547] gnss_motmdm: Unknown symbol motmdm_register_dlci (err
-2)
[ 119.899444] gnss_motmdm: Unknown symbol motmdm_unregister_dlci (err
-2)
[ 129.145935] snd_soc_motmdm: Unknown symbol motmdm_register_dlci
(err -2)
[ 129.153106] snd_soc_motmdm: Unknown symbol motmdm_unregister_dlci
(err -2)
[ 131.120361] cpcap-usb-phy cpcap-usb-phy.0: connected to USB host
[ 161.190216] cpcap-usb-phy cpcap-usb-phy.0: connected to USB host
[ 191.270263] cpcap-usb-phy cpcap-usb-phy.0: connected to USB host
[ 221.360107] cpcap-usb-phy cpcap-usb-phy.0: connected to USB host
[ 251.429962] cpcap-usb-phy cpcap-usb-phy.0: connected to USB host
[ 281.509643] cpcap-usb-phy cpcap-usb-phy.0: connected to USB host
[ 292.816436] g_ether gadget: packet filter 0e
[ 292.825256] g_ether gadget: ecm req21.43 v000e i0000 l0
...do I need to make devices manually or some udev rules?
user@devuan:~$ cat /proc/devices | grep motmdm
user@devuan:~$ cat /proc/devices | grep gnss
242 gnss
user@devuan:~$
Hmm, I suspect the driver just did not recognize the hw.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Pavel Machek <pavel@ucw.cz>
To: Tony Lindgren <tony@atomide.com>
Cc: Rob Herring <robh@kernel.org>, Marcel Partap <mpartap@gmx.net>,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
omerlle@gmail.com, Merlijn Wajer <merlijn@wizzup.org>,
linux-kernel@vger.kernel.org, Johan Hovold <johan@kernel.org>,
Peter Ujfalusi <peter.ujfalusi@ti.com>,
NeKit <nekit1000@gmail.com>,
linux-arm-kernel@lists.infradead.org,
Michael Scott <hashcode0f@gmail.com>,
Sebastian Reichel <sre@kernel.org>,
linux-omap@vger.kernel.org,
Jarkko Nikula <jarkko.nikula@bitmer.com>
Subject: Re: WIP Droid 4 voice calls, GNSS & PM with a TS 27.010 serdev driver
Date: Sun, 23 Dec 2018 11:33:15 +0100 [thread overview]
Message-ID: <20181223103315.GA1936@amd> (raw)
In-Reply-To: <20181217004450.GW6707@atomide.com>
[-- Attachment #1.1: Type: text/plain, Size: 3019 bytes --]
Hi!
> So the little elves have been slowly working to get voice calls
> working on droid 4 with the mainline kernel. And just in time for the
> upcoming holidays, it might be possible to call friends and relatives.
>
> I've pushed out an experimental branch containing serdev ts 27.010
> UART multiplexing support. That contains a serdev core driver for the
> mdm6600 modem (that also now idles the modem for PM), support for Alsa
> ASoC voice codec and mixer, and a GNSS driver for the GPS.
>
> Where it does not make sense to do a kernel serdev driver, I've
> exposed the rest of the available 27.010 channels as ten /dev/motmdm*
> character devices. There's /dev/motmdm1 for AT commands to dial voice
> calls, /dev/motmdm3 for SMS eventually, and I think there's also a SIM
> card reader at /dev/motmdm10. Then /dev/motmdm7 seems to be just an
> echo channel. The other channels are still a bit of a mystery.
I suspected it does not work in non-modular case, so I tried with
modules:
root@devuan:/my/ko# insmod gnss.ko
root@devuan:/my/ko# insmod gnss-motmdm.ko
insmod: ERROR: could not insert module gnss-motmdm.ko: Unknown symbol
in module
root@devuan:/my/ko# insmod n_gsm.ko
root@devuan:/my/ko# insmod snd-soc-motmdm.ko
insmod: ERROR: could not insert module snd-soc-motmdm.ko: Unknown
symbol in module
root@devuan:/my/ko# insmod motorola-mdm.ko
root@devuan:/my/ko# insmod snd-soc-motmdm.ko
root@devuan:/my/ko# insmod gnss-motmdm.ko
root@devuan:/my/ko#
But...
root@devuan:/my/ko# ls -al /dev/motmdm*
ls: cannot access '/dev/motmdm*': No such file or directory
root@devuan:/my/ko# ls -al /dev/gnss*
ls: cannot access '/dev/gnss*': No such file or directory
root@devuan:/my/ko#
[ 116.244445] gnss: GNSS driver registered with major 242
[ 119.892547] gnss_motmdm: Unknown symbol motmdm_register_dlci (err
-2)
[ 119.899444] gnss_motmdm: Unknown symbol motmdm_unregister_dlci (err
-2)
[ 129.145935] snd_soc_motmdm: Unknown symbol motmdm_register_dlci
(err -2)
[ 129.153106] snd_soc_motmdm: Unknown symbol motmdm_unregister_dlci
(err -2)
[ 131.120361] cpcap-usb-phy cpcap-usb-phy.0: connected to USB host
[ 161.190216] cpcap-usb-phy cpcap-usb-phy.0: connected to USB host
[ 191.270263] cpcap-usb-phy cpcap-usb-phy.0: connected to USB host
[ 221.360107] cpcap-usb-phy cpcap-usb-phy.0: connected to USB host
[ 251.429962] cpcap-usb-phy cpcap-usb-phy.0: connected to USB host
[ 281.509643] cpcap-usb-phy cpcap-usb-phy.0: connected to USB host
[ 292.816436] g_ether gadget: packet filter 0e
[ 292.825256] g_ether gadget: ecm req21.43 v000e i0000 l0
...do I need to make devices manually or some udev rules?
user@devuan:~$ cat /proc/devices | grep motmdm
user@devuan:~$ cat /proc/devices | grep gnss
242 gnss
user@devuan:~$
Hmm, I suspect the driver just did not recognize the hw.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 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:[~2018-12-23 10:33 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-17 0:44 WIP Droid 4 voice calls, GNSS & PM with a TS 27.010 serdev driver Tony Lindgren
2018-12-17 0:44 ` Tony Lindgren
2018-12-18 12:46 ` Pavel Machek
2018-12-18 12:46 ` Pavel Machek
2018-12-18 15:36 ` Tony Lindgren
2018-12-18 15:36 ` Tony Lindgren
2018-12-18 20:22 ` Pavel Machek
2018-12-18 20:22 ` Pavel Machek
2018-12-18 21:53 ` Tony Lindgren
2018-12-18 21:53 ` Tony Lindgren
2019-01-16 13:48 ` Pavel Machek
2019-01-16 13:48 ` Pavel Machek
2019-01-17 2:54 ` Tony Lindgren
2019-01-17 2:54 ` Tony Lindgren
2019-01-17 12:51 ` Pavel Machek
2019-01-17 12:51 ` Pavel Machek
2018-12-22 23:05 ` Pavel Machek
2018-12-22 23:05 ` Pavel Machek
2018-12-23 10:33 ` Pavel Machek [this message]
2018-12-23 10:33 ` Pavel Machek
2018-12-23 11:10 ` Pavel Machek
2018-12-23 11:10 ` Pavel Machek
2018-12-23 15:51 ` Tony Lindgren
2018-12-23 15:51 ` Tony Lindgren
2018-12-23 19:59 ` Pavel Machek
2018-12-23 19:59 ` Pavel Machek
2018-12-26 21:16 ` Pavel Machek
2018-12-26 21:16 ` Pavel Machek
2018-12-27 10:16 ` Pavel Machek
2018-12-27 10:16 ` Pavel Machek
2018-12-28 19:31 ` Tony Lindgren
2018-12-28 19:31 ` Tony Lindgren
2018-12-28 20:46 ` Pavel Machek
2018-12-28 20:46 ` Pavel Machek
2018-12-28 22:28 ` Tony Lindgren
2018-12-28 22:28 ` Tony Lindgren
2018-12-28 23:25 ` Pavel Machek
2018-12-28 23:25 ` Pavel Machek
2018-12-28 23:34 ` Tony Lindgren
2018-12-28 23:34 ` Tony Lindgren
2018-12-31 22:20 ` Tony Lindgren
2018-12-31 22:20 ` Tony Lindgren
2019-01-16 13:58 ` Pavel Machek
2019-01-16 13:58 ` Pavel Machek
2019-01-16 14:59 ` Tony Lindgren
2019-01-16 14:59 ` Tony Lindgren
2019-01-16 15:09 ` Tony Lindgren
2019-01-16 15:09 ` Tony Lindgren
2019-01-16 23:06 ` Pavel Machek
2019-01-16 23:06 ` Pavel Machek
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=20181223103315.GA1936@amd \
--to=pavel@ucw.cz \
--cc=hashcode0f@gmail.com \
--cc=jarkko.nikula@bitmer.com \
--cc=johan@kernel.org \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=merlijn@wizzup.org \
--cc=mpartap@gmx.net \
--cc=nekit1000@gmail.com \
--cc=omerlle@gmail.com \
--cc=peter.ujfalusi@ti.com \
--cc=robh@kernel.org \
--cc=sre@kernel.org \
--cc=tony@atomide.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.