Hi Aleksander,
After integrating the mhi drivers, wwan framework loaded the drivers and it
is up and running. However, ModemManager is not able to detect the modem.
Any hint/help is appreciated. Please throw some lights.
*Note*: qmicli is working fine and the modem manager is built with
--without-udev support.
Thanks,
SK
# qmicli -d /dev/wwan0qmi0 --dms-get-manufacturer
[/dev/wwan0qmi0] Device manufacturer retrieved:
Manufacturer: 'QUALCOMM INCORPORATED'
#
# ModemManager --debug --test-plugin-dir=/lib/
ModemManager[1367]: <info> [000002160.912487] ModemManager (version
1.18.4) starting in system bus...
ModemManager[1367]: <debug> [000002160.912729] [charsets] detecting
platform iconv() support...
ModemManager[1367]: <debug> [000002160.912864] [charsets] UTF-8: iconv
conversion to/from charset is supported
ModemManager[1367]: <debug> [000002160.912911] [charsets] UCS-2BE: iconv
conversion to/from charset is supported
ModemManager[1367]: <debug> [000002160.912952] [charsets] ASCII: iconv
conversion to/from charset is supported
ModemManager[1367]: <debug> [000002160.913065] [charsets] ISO8859-1:
iconv conversion to charset not supported
ModemManager[1367]: <debug> [000002160.913102] [charsets] CP437: iconv
conversion to charset not supported
ModemManager[1367]: <debug> [000002160.913136] [charsets] CP850: iconv
conversion to charset not supported
ModemManager[1367]: <debug> [000002160.913169] [charsets] UTF-16BE: iconv
conversion to charset not supported
ModemManager[1367]: <debug> [000002160.916497] bus acquired, creating
manager...
ModemManager[1367]: <debug> [000002160.932536] [auth-provider] singleton
created
ModemManager[1367]: <debug> [000002160.933034] [filter] created
ModemManager[1367]: <debug> [000002160.933130] [filter] explicit
whitelist: yes
ModemManager[1367]: <debug> [000002160.933156] [filter] explicit
blacklist: yes
ModemManager[1367]: <debug> [000002160.933180] [filter] plugin whitelist:
yes
ModemManager[1367]: <debug> [000002160.933204] [filter] qrtr devices
allowed: yes
ModemManager[1367]: <debug> [000002160.933228] [filter] virtual devices
forbidden: yes
ModemManager[1367]: <debug> [000002160.933252] [filter] net devices
allowed: yes
ModemManager[1367]: <debug> [000002160.933276] [filter] usbmisc devices
allowed: yes
ModemManager[1367]: <debug> [000002160.933300] [filter] rpmsg devices
allowed: yes
ModemManager[1367]: <debug> [000002160.933323] [filter] wwan devices
allowed: yes
ModemManager[1367]: <debug> [000002160.933346] [filter] tty devices:
ModemManager[1367]: <debug> [000002160.933369] [filter] platform
driver check: yes
ModemManager[1367]: <debug> [000002160.933396] [filter] driver check:
yes
ModemManager[1367]: <debug> [000002160.933420] [filter] cdc-acm
interface check: yes
ModemManager[1367]: <debug> [000002160.933443] [filter] with net
check: yes
ModemManager[1367]: <debug> [000002160.933467] [filter] default:
forbidden
ModemManager[1367]: <debug> [000002160.933566] [plugin-manager] looking for
plugins in '/lib/'
ModemManager[1367]: <debug> [000002160.959481] [plugin-manager] loaded
plugin 'qcom-soc' from '/lib//libmm-plugin-qcom-soc.so'
ModemManager[1367]: <debug> [000002160.959613] [filter] registered plugin
whitelist tag: ID_MM_QCOM_SOC
ModemManager[1367]: <debug> [000002160.960085] [plugin-manager] loaded
plugin 'generic' from '/lib//libmm-plugin-generic.so'
ModemManager[1367]: <debug> [000002160.960500] [plugin-manager]
successfully loaded 2 plugins registering 6 subsystems: wwan, rpmsg, net,
qrtr, tty, usbmisc
ModemManager[1367]: <debug> [000002160.961432] service name
'org.freedesktop.ModemManager1' was acquired
On Tue, Feb 8, 2022 at 3:43 PM Senthil Kumaresan <sekumarej...@gmail.com>
wrote:
> Hi Aleksander,
>
> I did backport the Linux-5.15 MHI driver and WWAN drivers to Linux-4.19
> (My kernel) and it seems the control port interfaces were created after I
> loaded the wwan.ko & mhi_wwan_ctrl.ko drivers.
> I am expecting now that the ModemManager will be up. Let me try.
>
> # ls -l /dev/wwan0*
> wwan0mbim0 wwan0qcdm0 wwan0qmi0
>
> Thanks,
> SK
>
> On Tue, Feb 8, 2022 at 10:40 AM Senthil Kumaresan <sekumarej...@gmail.com>
> wrote:
>
>> Hi Aleksander,
>>
>> Thanks for your support. I am trying to backport the WWAN system for my
>> kernel.
>> Just a thought. Is there any possibility that we make the modem manager
>> know that there is no WWAN subsystem rather than use "/dev/mhi0_QMI" to
>> detect the modem?
>>
>> Thanks,
>> Senthil
>>
>> On Mon, Feb 7, 2022 at 2:49 PM Senthil Kumaresan <sekumarej...@gmail.com>
>> wrote:
>>
>>> Hi Aleksander,
>>>
>>> Ok. Anyway, I am backporting the last mhi driver from Linux 5.15 to
>>> 4.19. I have compiled the driver successfully and loaded it to the target.
>>> The /dev/wwan0qmi0 is not there, because I did not take the
>>> drivers/net/wwan directory. I need to take them and rebuild and see whether
>>> the ModemManager is coming up or not.
>>>
>>> Thanks,
>>> Senthil
>>>
>>> On Mon, Feb 7, 2022 at 2:42 PM Aleksander Morgado <
>>> aleksan...@aleksander.es> wrote:
>>>
>>>> Hey!
>>>>
>>>>
>>>>> I did use the following driver that you have shared earlier. Is that
>>>>> below not the correct one ? I have copied the below into my kernel which
>>>>> is
>>>>> 4.19.
>>>>>
>>>>> ttps://github.com/kristrev/mhi-for-kernel-4.14
>>>>> <https://github.com/kristrev/mhi-for-kernel-4.14>
>>>>>
>>>>>
>>>> Oh, really? Does this mean that 4.14 backport doesn't have the WWAN
>>>> subsystem support? I truly believed it would have had it, or so I was told
>>>> by some dev team that had tested it. Sorry if that's not the case :/ If so,
>>>> it would mean the backport from that repo isn't usable for MM. I have my
>>>> own patch-by-patch backport to 5.4 including the wwan subsystem, but
>>>> haven't tried to go back further yet, not sure how complex that would be to
>>>> include everything for 4.14.
>>>>
>>>> Not sure if I'm missing something, but I definitely wouldn't have
>>>> expected the mhi0_QMI port name.
>>>>
>>>> --
>>>> Aleksander
>>>> https://aleksander.es
>>>>
>>>
