From: Tony Lindgren <tony@atomide.com>
To: Pavel Machek <pavel@denx.de>
Cc: Johan Hovold <johan@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Rob Herring <robh@kernel.org>,
Alan Cox <gnomes@lxorguk.ukuu.org.uk>,
Lee Jones <lee.jones@linaro.org>, Jiri Slaby <jslaby@suse.cz>,
Merlijn Wajer <merlijn@wizzup.org>,
Peter Hurley <peter@hurleysoftware.com>,
Sebastian Reichel <sre@kernel.org>,
linux-serial@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org
Subject: Re: [PATCHv8 0/6] n_gsm serdev support and GNSS driver for droid4
Date: Tue, 28 Jul 2020 01:36:31 -0700 [thread overview]
Message-ID: <20200728083631.GE2811@atomide.com> (raw)
In-Reply-To: <20200726082520.GA16953@amd>
* Pavel Machek <pavel@denx.de> [200726 08:25]:
> Hi!
>
> > > Here's the updated set of these patches fixed up for Johan's and
> > > Pavel's earlier comments.
> > >
> > > This series does the following:
> > >
> > > 1. Adds functions to n_gsm.c for serdev-ngsm.c driver to use
> > >
> > > 2. Adds a generic serdev-ngsm.c driver that brings up the TS 27.010
> > > TTY ports configured in devicetree with help of n_gsm.c
> > >
> > > 3. Allows the use of standard Linux device drivers for dedicated
> > > TS 27.010 channels for devices like GNSS and ALSA found on some
> > > modems for example
> >
> > Unfortunately that does not seem to be the case just yet. Your gnss
> > driver is still aware that it's using n_gsm for the transport and calls
> > into the "parent" serdev-ngsm driver instead of using the serdev
> > interface (e.g. as if this was still and MFD driver).
> >
> > If you model this right, the GNSS driver should work equally well
> > regardless of whether you use the serial interface (with n_gsm) or USB
> > (e.g. cdc-acm or usb-serial).
>
> We are not going to see that protocol anywhere else, so why is that
> a good goal?
Yes it seems this GNSS implementation is different from the one
provided by gobi.
> Anyway, Tony, is there newer version of this patchset? It would be
> good to get something in...
Sorry it will likely be few more weeks before I can look at this
stuff again.
> Can I help somehow?
I think I'm pretty clear on what needs to be done regarding this
patchset. Probably taking a look at if we could implement a
minimal raw /dev/gsmtty* read/write access in ofono using ell
instead of gatchat would help most :)
So something that mbim modem is already doing I think, sorry have
not had a chance to look at that either.
The /dev/gsmtty* devices should not change even with the further
changes to this patchset.
Regards,
Tony
next prev parent reply other threads:[~2020-07-28 8:36 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-12 21:47 [PATCHv8 0/6] n_gsm serdev support and GNSS driver for droid4 Tony Lindgren
2020-05-12 21:47 ` [PATCH 1/6] tty: n_gsm: Add support for serdev drivers Tony Lindgren
2020-05-13 19:24 ` Pavel Machek
2020-05-28 9:31 ` Johan Hovold
2020-11-29 20:51 ` Pavel Machek
2020-05-12 21:47 ` [PATCH 2/6] dt-bindings: serdev: ngsm: Add binding for serdev-ngsm Tony Lindgren
2020-05-28 9:38 ` Johan Hovold
2020-05-12 21:47 ` [PATCH 3/6] dt-bindings: serdev: ngsm: Add binding for GNSS child node Tony Lindgren
2020-05-13 19:26 ` Pavel Machek
2020-05-27 19:28 ` Rob Herring
2020-05-28 9:51 ` Johan Hovold
2021-03-05 10:46 ` Pavel Machek
2021-03-05 10:52 ` Johan Hovold
2021-03-24 1:09 ` Pavel Machek
2021-04-01 9:43 ` Johan Hovold
2020-05-12 21:47 ` [PATCH 4/6] serdev: ngsm: Add generic serdev-ngsm driver Tony Lindgren
2020-05-28 12:43 ` Johan Hovold
2020-05-12 21:47 ` [PATCH 5/6] gnss: motmdm: Add support for Motorola Mapphone MDM6600 modem Tony Lindgren
2020-05-28 13:06 ` Johan Hovold
2020-05-28 23:38 ` Tony Lindgren
2020-05-12 21:47 ` [PATCH 6/6] ARM: dts: omap4-droid4: Configure modem for serdev-ngsm Tony Lindgren
2020-05-13 19:27 ` Pavel Machek
2020-05-13 19:09 ` [PATCHv8 0/6] n_gsm serdev support and GNSS driver for droid4 Pavel Machek
2020-05-14 17:31 ` Tony Lindgren
2020-05-22 9:17 ` Greg Kroah-Hartman
2020-05-25 7:44 ` Johan Hovold
2020-05-28 8:39 ` Johan Hovold
2020-05-28 12:57 ` Pavel Machek
2020-07-26 8:25 ` Pavel Machek
2020-07-28 8:36 ` Tony Lindgren [this message]
2020-12-16 22:56 ` 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=20200728083631.GE2811@atomide.com \
--to=tony@atomide.com \
--cc=devicetree@vger.kernel.org \
--cc=gnomes@lxorguk.ukuu.org.uk \
--cc=gregkh@linuxfoundation.org \
--cc=johan@kernel.org \
--cc=jslaby@suse.cz \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=merlijn@wizzup.org \
--cc=pavel@denx.de \
--cc=peter@hurleysoftware.com \
--cc=robh@kernel.org \
--cc=sre@kernel.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).