From: Tobias Klauser <tklauser@distanz.ch>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-serial@vger.kernel.org, nios2-dev@sopc.et.ntust.edu.tw,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] serial: Add driver for the Altera JTAG UART
Date: Fri, 26 Feb 2010 10:04:56 +0100 [thread overview]
Message-ID: <20100226090456.GA32296@distanz.ch> (raw)
In-Reply-To: <20100225152622.7eb479aa@lxorguk.ukuu.org.uk>
On 2010-02-25 at 16:26:22 +0100, Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> > +static void altera_jtaguart_set_termios(struct uart_port *port,
> > + struct ktermios *termios,
> > + struct ktermios *old)
> > +{
> > +}
>
> Erm no .. it may be wrong in the code you are copying but please don't
> further that. The requirement is that the termios handed back reflects
> the actual settings not the requested ones.
>
> Use tty_termios_copy_hw() to copy the old termios hardware settings back
> so that the caller sees it cannot set them.
Would the following be sufficient?
if (old)
tty_termios_copy_hw(termios, old);
> > +static void altera_jtaguart_rx_chars(struct altera_jtaguart *pp)
> > +{
> > + struct uart_port *port = &pp->port;
> > + unsigned char ch, flag;
> > + unsigned long status;
> > +
> > + while ((status = readl(port->membase + ALTERA_JTAGUART_DATA_REG)) &
> > + ALTERA_JTAGUART_DATA_RVALID_MSK) {
> > + ch = status & ALTERA_JTAGUART_DATA_DATA_MSK;
> > + flag = TTY_NORMAL;
> > + port->icount.rx++;
> > +
> > + if (uart_handle_sysrq_char(port, ch))
> > + continue;
> > + uart_insert_char(port, 0, 0, ch, flag);
> > + }
> > +
> > + tty_flip_buffer_push(port->state->port.tty);
>
> port.tty needs to be protected here - you might race an unplug/hangup as
> far as I can see - I think you need to take the lock over a bigger area
So should we take port->lock in altera_jtaguart_interrupt already,
something like the following?
spin_lock(&port->lock);
if (isr & ALTERA_JTAGUART_CONTROL_RE_MSK)
altera_jtaguart_rx_chars(pp);
if (isr & ALTERA_JTAGUART_CONTROL_WE_MSK)
altera_jtaguart_tx_chars(pp);
spin_unlock(&port->lock);
And of course remove the lock/unlock from altera_jtaguart_tx_chars.
> [I'm working on switching this to krefs in all the drivers currently so
> that will end up cleaner]
>
> Basically fine other than that. The proposed UART number clashes with
> some other pending patches but that will get sorted out when they get
> merged
Thanks a lot for your review.
Tobias
next prev parent reply other threads:[~2010-02-26 9:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-25 14:35 [PATCH 1/2] serial: Add driver for the Altera JTAG UART Tobias Klauser
2010-02-25 14:35 ` [PATCH 2/2] serial: Add driver for the Altera UART Tobias Klauser
2010-02-25 14:47 ` [RESEND PATCH " Tobias Klauser
2010-02-26 19:50 ` Dan Carpenter
2010-03-01 8:04 ` Tobias Klauser
2010-02-25 15:26 ` [PATCH 1/2] serial: Add driver for the Altera JTAG UART Alan Cox
2010-02-26 9:04 ` Tobias Klauser [this message]
2010-02-26 11:27 ` Alan Cox
2010-02-25 16:45 ` Peter Korsgaard
2010-02-26 9:06 ` Tobias Klauser
-- strict thread matches above, loose matches on Subject: below --
2010-05-05 8:35 [PATCH v5 0/2] serial: Drivers for Altera UARTs Tobias Klauser
2010-05-05 8:35 ` [PATCH 1/2] serial: Add driver for the Altera JTAG UART Tobias Klauser
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=20100226090456.GA32296@distanz.ch \
--to=tklauser@distanz.ch \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=nios2-dev@sopc.et.ntust.edu.tw \
/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