From: Matthias Fuchs <mfuchs@ma-fu.de>
To: Laurent Pinchart <laurentp@cse-semaphore.com>
Cc: linux-serial@vger.kernel.org
Subject: Re: [PATCH/RFC] serial: Add ioctl to enable auto rs485 mode with some Exar UARTs
Date: Mon, 22 Dec 2008 18:57:04 +0100 [thread overview]
Message-ID: <200812221857.05319.mfuchs@ma-fu.de> (raw)
In-Reply-To: <200812191128.01546.laurentp@cse-semaphore.com>
Hi Laurent,
I agree with your comments and will update and repost my patch
during the upcoming holy days.
Matthias
> Hi Matthias,
>
> On Friday 19 December 2008 00:48:34 Matthias Fuchs wrote:
> > Hi,
> >
> > please see my patch for enabling the RS485 half-duplex control below.
> > Please note that I am using this on a PowerPC platform. So I needed to
> > add the ioctl to the PowerPC header. As Wolfgang stated, it is
> > already in the x86 header. I am not sure if I have to post the
> > modification on the powerpc header to the PowerPC list or if it will be
> > accepted here as well. .... But first I will have to see what you think
> > of this patch
> >
> > :-)
>
> You will have to submit ioctls.h modifications as a separate patch to the
> powerpc-dev mailing list.
>
> The patch looks good, a few comments below.
>
> > Matthias
> >
> >
> > Some Exar UARTs support a auto rs485 mode. In this mode
> > the UART's RTS# pin is activated during transmitting and
> > can be used to enable a rs485 line driver. This has nothing
> > to do with attempts to do this by manually by asserting/
> > deasserting handshake lines.
> >
> > Signed-off-by: Matthias Fuchs <mfuchs@ma-fu.de>
> > ---
> > arch/powerpc/include/asm/ioctls.h | 2 +
> > drivers/serial/8250.c | 59
> > +++++++++++++++++++++++++++++++++++++ 2 files changed, 61 insertions(+),
> > 0 deletions(-)
> >
> > diff --git a/arch/powerpc/include/asm/ioctls.h
> > b/arch/powerpc/include/asm/ioctls.h index 279a622..1842186 100644
> > --- a/arch/powerpc/include/asm/ioctls.h
> > +++ b/arch/powerpc/include/asm/ioctls.h
> > @@ -89,6 +89,8 @@
> > #define TIOCSBRK 0x5427 /* BSD compatibility */
> > #define TIOCCBRK 0x5428 /* BSD compatibility */
> > #define TIOCGSID 0x5429 /* Return the session ID of FD */
> > +#define TIOCGRS485 0x542e
> > +#define TIOCSRS485 0x542f
> > #define TIOCGPTN _IOR('T',0x30, unsigned int) /* Get Pty Number (of
> > pty-mux device) */ #define TIOCSPTLCK _IOW('T',0x31, int) /* Lock/unlock
> > Pty */
> >
> > diff --git a/drivers/serial/8250.c b/drivers/serial/8250.c
> > index 303272a..e6df50f 100644
> > --- a/drivers/serial/8250.c
> > +++ b/drivers/serial/8250.c
> > @@ -2511,6 +2511,64 @@ serial8250_type(struct uart_port *port)
> > return uart_config[type].name;
> > }
> >
> > +static int
> > +serial8250_ioctl_port(struct uart_port *port, unsigned int cmd, unsigned
> > long arg) +{
> > + struct uart_8250_port *up = (struct uart_8250_port *)port;
> > +
> > + switch (cmd) {
> > + case TIOCSRS485:
> > + {
> > + struct serial_rs485 rs485ctrl;
> > + unsigned char fctr;
> > +
> > + if (port->type != PORT_16850)
> > + return -ENODEV;
>
> According to the ioctl manpage, -ENOTTY might be better:
>
> "ENOTTY The specified request does not apply to the kind of object that the
> descriptor d references."
>
> > + if (copy_from_user(&rs485ctrl,
> > + (struct serial_rs485 *)arg,
> > + sizeof(rs485ctrl)))
> > + return -EFAULT;
> > +
> > + serial_outp(up, UART_LCR, 0xbf);
> > + fctr = serial_inp(up, UART_FCTR);
> > + if (rs485ctrl.flags & SER_RS485_ENABLED)
> > + fctr |= 0x08;
> > + else
> > + fctr &= ~0x08;
> > + serial_outp(up, UART_FCTR, fctr);
> > + serial_outp(up, UART_LCR, 0);
>
> Doesn't this require locking ? serial8250_break_ctl and
> serial8250_set_termios both take the port.lock spinlock to prevent races
> from messing up with UART_LCR.
>
> > + return 0;
> > + }
> > +
> > + case TIOCGRS485:
> > + {
> > + struct serial_rs485 rs485ctrl;
> > +
> > + if (port->type != PORT_16850)
> > + return -ENODEV;
>
> What about setting rs485ctrl.flags to 0 and returning with success when
> RS485 auto direction control is not supported by the hardware ? I'm not
> sure if the preferred semantic for get requests on unsupported features is
> to return an error or return a 'feature disabled' value.
>
> > + serial_outp(up, UART_LCR, 0xbf);
> > + if (serial_inp(up, UART_FCTR) & 0x08)
> > + rs485ctrl.flags = SER_RS485_ENABLED;
> > + else
> > + rs485ctrl.flags = 0;
> > + serial_outp(up, UART_LCR, 0);
>
> Ditto, doesn't this require locking ?
>
> > +
> > + if (copy_to_user((struct serial_rs485 *)arg,
> > + &rs485ctrl,
> > + sizeof(rs485ctrl)))
> > + return -EFAULT;
> > + return 0;
> > + }
> > +
> > + default:
> > + return -ENOIOCTLCMD;
> > + }
> > +
> > + return 0;
> > +}
> > +
> > static struct uart_ops serial8250_pops = {
> > .tx_empty = serial8250_tx_empty,
> > .set_mctrl = serial8250_set_mctrl,
> > @@ -2529,6 +2587,7 @@ static struct uart_ops serial8250_pops = {
> > .request_port = serial8250_request_port,
> > .config_port = serial8250_config_port,
> > .verify_port = serial8250_verify_port,
> > + .ioctl = serial8250_ioctl_port,
> > #ifdef CONFIG_CONSOLE_POLL
> > .poll_get_char = serial8250_get_poll_char,
> > .poll_put_char = serial8250_put_poll_char,
next prev parent reply other threads:[~2008-12-22 17:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-18 23:48 [PATCH/RFC] serial: Add ioctl to enable auto rs485 mode with some Exar UARTs Matthias Fuchs
2008-12-19 10:28 ` Laurent Pinchart
2008-12-22 17:57 ` Matthias Fuchs [this message]
2008-12-19 15:13 ` Laurent Pinchart
2008-12-21 9:50 ` Chris Gibson
2008-12-22 15:59 ` Wolfram Sang
2008-12-22 18:02 ` Matthias Fuchs
2008-12-23 13:23 ` Christopher Gibson
2009-01-02 15:29 ` Matthias Fuchs
2009-01-07 13:42 ` Christopher Gibson
2008-12-23 14:03 ` Christopher Gibson
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=200812221857.05319.mfuchs@ma-fu.de \
--to=mfuchs@ma-fu.de \
--cc=laurentp@cse-semaphore.com \
--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