From: Maksim Salau <maksim.salau-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Stuart Longland <stuartl-EoQOJlg3kTYQrrorzV6ljw@public.gmane.org>
Cc: linux-serial-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
alborchers-2TsfIrYsZRL7O9PZeWXHPg@public.gmane.org,
linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] USB: serial: ti_usb_3410_5052: Port uart_mode from io_ti.
Date: Sat, 19 Aug 2017 23:40:56 +0300 [thread overview]
Message-ID: <20170819234056.37c7d339@gmail.com> (raw)
In-Reply-To: <20170818025659.4402-1-stuartl-EoQOJlg3kTYQrrorzV6ljw@public.gmane.org>
Hi Stuart,
> This introduces the `uart_mode` sysfs attribute as seen in the `io_ti`
> USB serial driver, allowing this USB serial interface to be switched
> between RS-232, 2-wire RS-485 and 4-wire RS-485.
Recently I've discovered a blog post by Greg Kroah-Hartman on sysfs files [1].
I believe this information will help you to create the new file in a better way.
[1] http://kroah.com/log/blog/2013/06/26/how-to-create-a-sysfs-file-correctly/
Best regards,
Maksim.
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-08-19 20:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4a469222-d48d-f498-f2db-ca582295adc3@longlandclan.id.au>
[not found] ` <4a469222-d48d-f498-f2db-ca582295adc3-3e+Fe6x+DsgJbe36r25VNhCuuivNXqWP@public.gmane.org>
2017-06-27 9:04 ` Moxa UPort 1150 and RS-422/485… what's the "proper" way to switch modes Johan Hovold
2017-06-27 9:43 ` Stuart Longland
[not found] ` <42601356-656d-57d0-d366-a0933780b8f9-3e+Fe6x+DsgJbe36r25VNhCuuivNXqWP@public.gmane.org>
2017-06-27 12:08 ` Oliver Neukum
[not found] ` <1498565331.30390.5.camel-IBi9RG/b67k@public.gmane.org>
2017-06-27 22:07 ` Stuart Longland
[not found] ` <ae2907c2-cb0f-61e4-c6f2-af3dcec93ace-3e+Fe6x+DsgJbe36r25VNhCuuivNXqWP@public.gmane.org>
2017-06-28 9:19 ` Oliver Neukum
[not found] ` <1498641549.10278.5.camel-IBi9RG/b67k@public.gmane.org>
2017-06-28 12:01 ` Greg KH
[not found] ` <20170628120120.GA10502-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2017-06-28 12:41 ` Oliver Neukum
[not found] ` <1498653709.10278.17.camel-IBi9RG/b67k@public.gmane.org>
2017-06-28 14:59 ` Bjørn Mork
2017-06-28 15:35 ` Johan Hovold
2017-06-28 15:34 ` Johan Hovold
2017-06-29 19:50 ` Alan Cox
2017-07-03 8:51 ` Johan Hovold
2017-06-28 15:16 ` Johan Hovold
2017-08-18 2:56 ` [PATCH] USB: serial: ti_usb_3410_5052: Port uart_mode from io_ti Stuart Longland
[not found] ` <20170818025659.4402-1-stuartl-EoQOJlg3kTYQrrorzV6ljw@public.gmane.org>
2017-08-18 3:16 ` Stuart Longland
2017-08-19 20:40 ` Maksim Salau [this message]
[not found] ` <20170819234056.37c7d339-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-08-19 20:47 ` Stuart Longland
2017-08-28 8:56 ` 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=20170819234056.37c7d339@gmail.com \
--to=maksim.salau-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=alborchers-2TsfIrYsZRL7O9PZeWXHPg@public.gmane.org \
--cc=linux-serial-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=stuartl-EoQOJlg3kTYQrrorzV6ljw@public.gmane.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).