public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Johan Hovold <johan@kernel.org>
To: One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>
Cc: Johan Hovold <johan@kernel.org>,
	Mathieu OTHACEHE <m.othacehe@gmail.com>,
	gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
	linux-usb@vger.kernel.org
Subject: Re: [PATCH v5] USB: serial: add Moxa UPORT 11x0 driver
Date: Mon, 28 Dec 2015 16:32:38 +0100	[thread overview]
Message-ID: <20151228153238.GB18146@localhost> (raw)
In-Reply-To: <20151228143944.111a6c7f@lxorguk.ukuu.org.uk>

On Mon, Dec 28, 2015 at 02:39:44PM +0000, One Thousand Gnomes wrote:
> > 	https://lkml.kernel.org/r/201102171210.03474.frode@tennebo.com
> > 
> > However, the TIOCSRS485-ioctl might not even be the right interface for
> > changing transceiver modes, and instead a sysfs-based
> > usb-serial-specific interface could be more appropriate for example.
> 
> sysfs works out very badly if modes can be configured routinely at
> runtime. In particular the sysfs interface is completely disconnected
> from the vhangup() and security model of the tty interface.
> 
> If its the kind if thing just administratively configured at boot then
> it's a great interface, just be careful about who has access to it.

I think this is something that you only want to configure once (e.g. at
boot) and before even opening the tty device as this can change the
functions of the pins (e.g. DCD becoming TxD-).

If a generic usb-serial-specific interface for this makes sense, I think
we should simply prevent mode changes while the port is in use.

Johan

  reply	other threads:[~2015-12-28 15:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-06 11:29 [PATCH v5] USB: serial: add Moxa UPORT 11x0 driver Mathieu OTHACEHE
2015-12-28 14:06 ` Johan Hovold
2015-12-28 14:39   ` One Thousand Gnomes
2015-12-28 15:32     ` Johan Hovold [this message]
2015-12-28 20:21       ` [PATCH v6] " Mathieu OTHACEHE
2015-12-29 12:29         ` Johan Hovold
2016-01-03 14:22           ` Mathieu OTHACEHE

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=20151228153238.GB18146@localhost \
    --to=johan@kernel.org \
    --cc=gnomes@lxorguk.ukuu.org.uk \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=m.othacehe@gmail.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