From: Sergey Ryazanov <ryazanov.s.a@gmail.com>
To: Loic Poulain <loic.poulain@oss.qualcomm.com>,
Muhammad Nuzaihan <zaihan@unrealasia.net>
Cc: Slark Xiao <slark_xiao@163.com>,
Loic Poulain <loic.poulain@linaro.org>,
manivannan.sadhasivam@linaro.org, netdev@vger.kernel.org,
Qiang Yu <quic_qianyu@quicinc.com>,
johan@kernel.org, mhi@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: GNSS support for Qualcomm PCIe modem device
Date: Tue, 08 Apr 2025 13:26:38 +0300 [thread overview]
Message-ID: <BB06D58C-E27D-42FA-8043-AE767E9B5E91@gmail.com> (raw)
In-Reply-To: <CAFEp6-2_+25Z+2nPOQtOzJPgfJM8DAs2h_e6HTQ4fAVLt0+bwQ@mail.gmail.com>
On April 8, 2025 12:13:17 PM GMT+03:00, Loic Poulain <loic.poulain@oss.qualcomm.com> wrote:
>Hi Zhaihan, Sergey.
>
>On Fri, Apr 4, 2025 at 7:42 AM Muhammad Nuzaihan <zaihan@unrealasia.net> wrote:
>>
>> Hi Sergey, Slark,
>>
>> Using wwan subsystem and it works without issues, maybe i might miss
>> something, perhaps the flow control but i never have any problems even
>> without flow control.
>>
>> I am using gpsd + cgps and xgps with a small modification to Linux
>> kernel's wwan subsystem in the kernel to get NMEA data.
>>
>> I had posted the patch previously and i can post the patch again if you like.
>>
>> Attached in this email is the screenshot of cgps + gpsd.
>>
>> Maybe it should be in GPS subsystem but it's working for me even using
>> wwan subsystem for months now.
>
>Yes, I would strongly recommend doing the extra step of making it
>registered to the GNSS subsystem so that device is exposed with the
>correct class.
>From WWAN driver perspective, it will not change anything, as we could
>have the WWAN framework handling this properly (bridging to gnss
>intead of exposing the port as wwan character device).
>Sergey, is it your plan?
Yep. I made the prototype exactly in this way. So a modem driver should not care about the port type. Just call WWAN core and it will do the job for the driver.
The prototype is done. Needs some polishing, proper description, and probably, today night I'm going to publish the RFC.
Hi Loic,
next prev parent reply other threads:[~2025-04-08 10:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-03 6:06 Slark Xiao
[not found] ` <DBU4US.LSH9IZJH4Q933@unrealasia.net>
2025-04-03 8:42 ` Muhammad Nuzaihan
2025-04-03 21:47 ` Sergey Ryazanov
2025-04-04 5:41 ` Muhammad Nuzaihan
2025-04-08 9:13 ` Loic Poulain
2025-04-08 10:26 ` Sergey Ryazanov [this message]
2025-04-08 14:45 ` Muhammad Nuzaihan
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=BB06D58C-E27D-42FA-8043-AE767E9B5E91@gmail.com \
--to=ryazanov.s.a@gmail.com \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=loic.poulain@linaro.org \
--cc=loic.poulain@oss.qualcomm.com \
--cc=manivannan.sadhasivam@linaro.org \
--cc=mhi@lists.linux.dev \
--cc=netdev@vger.kernel.org \
--cc=quic_qianyu@quicinc.com \
--cc=slark_xiao@163.com \
--cc=zaihan@unrealasia.net \
/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
all inboxes | Powered by JetHome®