From: Ivaylo Dimitrov <ivo.g.dimitrov.75@gmail.com>
To: Jiri Slaby <jslaby@suse.cz>, Pavel Machek <pavel@ucw.cz>,
Johan Hovold <johan@kernel.org>
Cc: Tony Lindgren <tony@atomide.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Rob Herring <robh@kernel.org>,
Alan Cox <gnomes@lxorguk.ukuu.org.uk>,
Lee Jones <lee.jones@linaro.org>,
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,
phone-devel@vger.kernel.org
Subject: Re: [PATCH 1/6] tty: n_gsm: Add support for serdev drivers
Date: Thu, 19 Dec 2024 10:02:24 +0200 [thread overview]
Message-ID: <fa10cf03-ce8d-4fc4-a4fe-ea14c035825d@gmail.com> (raw)
In-Reply-To: <dcdc22f2-587e-4879-a987-71c92c0149e9@suse.cz>
On 19.12.24 г. 9:53 ч., Jiri Slaby wrote:
> On 19. 12. 24, 8:45, Ivaylo Dimitrov wrote:
>> Hi,
>>
>> ...
>>
>> On 29.11.20 г. 22:51 ч., Pavel Machek wrote:
>>>>
>>>> It looks like you may also have a problem with tty hangups, which
>>>> serdev
>>>> does not support currently. There are multiple paths in n_gsm which can
>>>> trigger a hangup (e.g. based on remote input) and would likely lead
>>>> to a
>>>> crash
>>>
>>> I don't believe we need to support hangups for the Droid 4, but
>>> obviously it would be good not to crash. But I don't know where to
>>> start looking, do you have any hints?
>>>
>>
>> I changed the patch so it calls tty_port_register_device_serdev,
>> ported gnss driver to use serdev_device, got it working:
>>
>> root@devuan-droid4:~# cat /dev/gnss0
>> $GPGGA,,,,,,0,,,,,,,,*66
>> $GNGNS,,,,,,NN,,,,,,*53
>> $GNGNS,,,,,,NN,,,,,,*53
>> $GNGNS,,,,,,NN,,,,,,*53
>> $GPVTG,,T,,M,,N,,K,N*2C
>> $GPRMC,,V,,,,,,,,,,N*53
>> $GPGSA,A,1,,,,,,,,,,,,,,,*1E
>> $GLGSV,1,1,01,255,,,37*52
>> $GPGGA,,,,,,0,,,,,,,,*66
>> $GNGNS,,,,,,NN,,,,,,*53
>> $GNGNS,,,,,,NN,,,,,,*53
>> $GNGNS,,,,,,NN,,,,,,*53
>>
>> However, I get:
>>
>> gsmtty gsmtty4: tty_hangup: tty->count(1) != (#fd's(0) + #kopen's(0))
>>
>> when closing /dev/gnss0
>>
>> Any hint what shall be implemented in serdev to properly handle hangups?
>
> Without code, no.
Which code? The $subject patch with changes I made? or gnss driver? both?
Thanks,
Ivo
next prev parent reply other threads:[~2024-12-19 8:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200512214713.40501-1-tony@atomide.com>
[not found] ` <20200512214713.40501-2-tony@atomide.com>
[not found] ` <20200528093102.GC10358@localhost>
2020-11-29 20:51 ` [PATCH 1/6] tty: n_gsm: Add support for serdev drivers Pavel Machek
2024-12-19 7:45 ` Ivaylo Dimitrov
2024-12-19 7:53 ` Jiri Slaby
2024-12-19 8:02 ` Ivaylo Dimitrov [this message]
[not found] ` <20200528083918.GB10358@localhost>
2020-12-16 22:56 ` [PATCHv8 0/6] n_gsm serdev support and GNSS driver for droid4 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=fa10cf03-ce8d-4fc4-a4fe-ea14c035825d@gmail.com \
--to=ivo.g.dimitrov.75@gmail.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@ucw.cz \
--cc=peter@hurleysoftware.com \
--cc=phone-devel@vger.kernel.org \
--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 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).