From: "Kilau, Scott" <Scott_Kilau@digi.com>
To: <linux-kernel@vger.kernel.org>
Cc: <greg@kroah.com>, "Wen Xiong" <wenxiong@us.ibm.com>
Subject: Re: [ patch 4/7] drivers/serial/jsm: new serial device driver
Date: Tue, 8 Mar 2005 15:47:45 -0600 [thread overview]
Message-ID: <71A17D6448EC0140B44BCEB8CD0DA36E04B9D9E2@minimail.digi.com> (raw)
> Who needs to know if a port is open or not?
>
<snipped some code>
>
> +static ssize_t jsm_tty_baud_show(struct class_device *class_dev, char
*buf)
> No, please delete these, and the other sysfs files that duplicate the
> same info that you can get by using the standard Linux termios calls.
> There is no need for them here.
>
> thanks,
> greg k-h
Hi Greg, Wendy, all,
Our serial port monitoring tools need to know these things, and to
find them out *without* opening up the serial port to do an ioctl().
For example, lets say a customer has a modem connected to a serial port.
If you were to open up the port with an "stty -a" to get the current
settings and signals, you would unintentionally raise RTS and DTR.
Now the modem sees DTR raised, and might react to it by mistake.
Usually raising and dropping RTS/DTR quickly on a modem won't hurt
anything,
but its not particularly a "good" when the modem is not expecting it.
This is why we export the various signals/stats/signals to sysfs (used
to be proc),
so our management tools can get the information about the serial port
without being
intrusive by opening up the port.
Scott
next reply other threads:[~2005-03-08 21:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-08 21:47 Kilau, Scott [this message]
2005-03-09 0:02 ` Greg KH
2005-03-09 16:16 ` Russell King
-- strict thread matches above, loose matches on Subject: below --
2005-03-09 2:36 Kilau, Scott
2005-03-09 5:50 ` Greg KH
2005-02-27 23:39 Wen Xiong
2005-02-28 3:21 ` Christoph Hellwig
2005-02-28 6:39 ` Greg KH
2005-03-04 21:08 ` Wen Xiong
2005-03-04 22:01 ` Greg KH
2005-03-07 22:46 ` Wen Xiong
2005-03-08 6:44 ` Greg KH
2005-03-08 18:55 ` Wen Xiong
2005-03-08 23:58 ` Greg KH
2005-03-09 15:47 ` Wen Xiong
2005-03-09 16:35 ` Greg KH
2005-03-09 17:18 ` Wen Xiong
2005-03-09 18:58 ` Greg KH
2005-03-09 16:11 ` Russell King
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=71A17D6448EC0140B44BCEB8CD0DA36E04B9D9E2@minimail.digi.com \
--to=scott_kilau@digi.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=wenxiong@us.ibm.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
all inboxes | Powered by JetHome®