From: Greg KH <gregkh@linuxfoundation.org>
To: "Starke, Daniel" <daniel.starke@siemens.com>
Cc: "linux-serial@vger.kernel.org" <linux-serial@vger.kernel.org>,
"jirislaby@kernel.org" <jirislaby@kernel.org>,
"ilpo.jarvinen@linux.intel.com" <ilpo.jarvinen@linux.intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 3/3] tty: n_gsm: add TIOCMIWAIT support
Date: Wed, 1 Feb 2023 13:51:27 +0100 [thread overview]
Message-ID: <Y9pgT4VcW3oGaSbY@kroah.com> (raw)
In-Reply-To: <DB9PR10MB588166BD5DA668E4F6DEA597E0D19@DB9PR10MB5881.EURPRD10.PROD.OUTLOOK.COM>
On Wed, Feb 01, 2023 at 09:30:28AM +0000, Starke, Daniel wrote:
> > > Add support for the TIOCMIWAIT ioctl on the virtual ttys. This enables the
> > > user to wait for virtual modem signals like RING.
> > >
> > > Signed-off-by: Daniel Starke <daniel.starke@siemens.com>
> > > ---
> > > drivers/tty/n_gsm.c | 32 ++++++++++++++++++++++++++++++++
> > > 1 file changed, 32 insertions(+)
> > >
> > > diff --git a/drivers/tty/n_gsm.c b/drivers/tty/n_gsm.c
> > > index 118511c1fa37..48fb7dad44cd 100644
> > > --- a/drivers/tty/n_gsm.c
> > > +++ b/drivers/tty/n_gsm.c
> > > @@ -1542,6 +1542,7 @@ static void gsm_process_modem(struct tty_struct *tty, struct gsm_dlci *dlci,
> > > if (brk & 0x01)
> > > tty_insert_flip_char(&dlci->port, 0, TTY_BREAK);
> > > dlci->modem_rx = mlines;
> > > + wake_up_interruptible(&dlci->gsm->event);
> > > }
> > >
> > > /**
> > > @@ -3848,6 +3849,35 @@ static int gsm_modem_update(struct gsm_dlci *dlci, u8 brk)
> > > return -EPROTONOSUPPORT;
> > > }
> > >
> > > +/**
> > > + * gsm_wait_modem_change - wait for modem status line change
> >
> > No need for tabs.
> >
> > Or for kernel doc for static functions, but that's not a big deal.
>
> All other functions follow the same style here. Nevertheless, I will
> replace the tabs with spaces. Originally, I had planned a code clean-up
> after committing all the changes from my original RFC.
Ah, ok, nevermind then, I didn't see that as it's not in the diffs.
Cleaning up later is fine.
> > > +static int gsm_wait_modem_change(struct gsm_dlci *dlci, u32 mask)
> > > +{
> > > + struct gsm_mux *gsm = dlci->gsm;
> > > + u32 old = dlci->modem_rx & mask;
> > > + int ret;
> > > +
> > > + if (gsm->dead)
> > > + return -ENODEV;
> > > +
> > > + do {
> > > + ret = wait_event_interruptible(gsm->event, gsm->dead
> > > + || old ^ (dlci->modem_rx & mask));
> > > + if (ret)
> > > + return ret;
> > > + if (dlci->state != DLCI_OPEN)
> > > + return -EL2NSYNC;
> > > + if (gsm->dead)
> > > + return -ENODEV;
> > > + } while ((old ^ (dlci->modem_rx & mask)) == 0);
> >
> > No way to break out of the loop if it goes for forever?
>
> I assume that this is the expected behavior for TIOCMIWAIT. The functions
> returns if:
> - the requested modem signal changed
> - the wait function got interrupted (e.g. by a signal)
> - the underlying DLCI was closed
> - the underlying ldisc device was removed
Hm, I guess you are right. But wow, reading that
wait_event_interruptible() condition is crazy, please document that
really well to explain this properly so you will be able to understand
it in a year when you next have to fix it up :)
> I can add that the function returns immediate if a mask has been passed
> which matches no modem signal if this is preferred?
I don't think that would work, try it on some existing serial ports to
see what they do.
thanks,
greg k-h
next prev parent reply other threads:[~2023-02-01 12:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-01 8:01 [PATCH 1/3] tty: n_gsm: add keep alive support D. Starke
2023-02-01 8:01 ` [PATCH 2/3] tty: n_gsm: add RING/CD control support D. Starke
2023-02-01 8:01 ` [PATCH 3/3] tty: n_gsm: add TIOCMIWAIT support D. Starke
2023-02-01 8:41 ` Greg KH
2023-02-01 9:30 ` Starke, Daniel
2023-02-01 12:51 ` Greg KH [this message]
2023-02-01 8:40 ` [PATCH 1/3] tty: n_gsm: add keep alive support Greg KH
2023-02-01 9:17 ` Starke, Daniel
2023-02-01 9:27 ` Greg KH
2023-02-01 9:48 ` Starke, Daniel
2023-02-01 12:48 ` Greg KH
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=Y9pgT4VcW3oGaSbY@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=daniel.starke@siemens.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=jirislaby@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.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).