From: Yoshihiro YUNOMAE <yoshihiro.yunomae.ez@hitachi.com>
To: Heikki Krogerus <heikki.krogerus@linux.intel.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Alan <gnomes@lxorguk.ukuu.org.uk>,
Stephen Warren <swarren@nvidia.com>,
Jingoo Han <jg1.han@samsung.com>,
linux-kernel@vger.kernel.org,
Hidehiro Kawai <hidehiro.kawai.ez@hitachi.com>,
linux-serial@vger.kernel.org, yrl.pp-manager.tt@hitachi.com,
Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>,
Aaron Sierra <asierra@xes-inc.com>, Jiri Slaby <jslaby@suse.cz>
Subject: Re: Re: [PATCH V3] serial/uart/8250: Add tunable RX interrupt trigger I/F of FIFO buffers
Date: Mon, 17 Mar 2014 12:03:09 +0900 [thread overview]
Message-ID: <532665ED.7090401@hitachi.com> (raw)
In-Reply-To: <20140314141602.GA11603@xps8300>
Hi Heikki,
Thank you for your reply.
(2014/03/14 23:16), Heikki Krogerus wrote:
> Hi,
>
> On Fri, Mar 14, 2014 at 11:21:54AM +0900, Yoshihiro YUNOMAE wrote:
>> void serial8250_clear_and_reinit_fifos(struct uart_8250_port *p)
>> {
>> - unsigned char fcr;
>> -
>> serial8250_clear_fifos(p);
>> - fcr = uart_config[p->port.type].fcr;
>> - serial_out(p, UART_FCR, fcr);
>> + p->fcr = uart_config[p->port.type].fcr;
>> + serial_out(p, UART_FCR, p->fcr);
>
> You should allow also the probe drivers to set this..
>
> if (!p->fcr)
> p->fcr = uart_config[p->port.type].fcr;
Oh, I'll fix it.
>> }
>> EXPORT_SYMBOL_GPL(serial8250_clear_and_reinit_fifos);
>>
>> @@ -2325,10 +2323,19 @@ serial8250_do_set_termios(struct uart_port *port, struct ktermios *termios,
>> if ((baud < 2400 && !up->dma) || fifo_bug) {
>> fcr &= ~UART_FCR_TRIGGER_MASK;
>> fcr |= UART_FCR_TRIGGER_1;
>> + /* Don't use user setting RX trigger */
>> + up->fcr = 0;
>
> I don't know about this but..
>
>> }
>> }
>>
>> /*
>> + * If up->fcr exists, a user has opened this port, changed RX trigger,
>> + * or read RX trigger before. So, we don't need to change up->fcr here.
>> + */
>> + if (!up->fcr)
>> + up->fcr = fcr;
>
> Why not just set fcr = up->fcr in the beginning of the function?
Ah, we don't need to set up->fcr = 0 in the previous flow when we
implement as follows:
unsigned char fcr = up->fcr;
... <snip> ...
/*
* If fcr exists, a user has opened this port, changed RX
* trigger, or read RX trigger before. If so, we do not change
* fcr.
*/
if (!fcr)
fcr = uart_config[port_type].fcr;
if ((baud < 2400 && !up->dma) || fifo_bug) {
fcr &= ~UART_FCR_TRIGGER_MASK;
fcr |= UART_FCR_TRIGGER_1;
}
up->fcr = fcr;
> <snip>
>
>> +static int do_set_rx_int_trig(struct tty_port *port, unsigned char val)
>> +{
>> + struct uart_state *state = container_of(port, struct uart_state, port);
>> + struct uart_port *uport = state->uart_port;
>> + struct uart_8250_port *up =
>> + container_of(uport, struct uart_8250_port, port);
>> + unsigned char fcr;
>> + int rx_trig;
>> +
>> + if (!(up->capabilities & UART_CAP_FIFO) || uport->fifosize <= 1)
>> + return -EINVAL;
>> +
>> + rx_trig = convert_val2rxtrig(up, val);
>> + if (rx_trig < 0)
>> + return rx_trig;
>> +
>> + serial8250_clear_fifos(up);
>> + if (!up->fcr)
>> + /* termios is not set yet */
>> + fcr = uart_config[up->port.type].fcr;
>> + else
>> + fcr = up->fcr;
>> + fcr &= ~UART_FCR_TRIGGER_MASK;
>> + fcr |= (unsigned char)rx_trig;
>> + up->fcr = fcr;
>> + serial_out(up, UART_FCR, up->fcr);
>> + return 0;
>> +}
>
> Where are you setting UART_FCR_ENABLE_FIFO bit? Am I missing
> something?
In these implementation, the driver sets up->fcr as
uart_config[up->port.type].fcr first and changes only RX trigger. So,
we don't need to set the bit in a direct way.
Thank you,
Yoshihiro YUNOMAE
--
Yoshihiro YUNOMAE
Software Platform Research Dept. Linux Technology Center
Hitachi, Ltd., Yokohama Research Laboratory
E-mail: yoshihiro.yunomae.ez@hitachi.com
prev parent reply other threads:[~2014-03-17 3:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-14 2:21 [PATCH V3] serial/uart/8250: Add tunable RX interrupt trigger I/F of FIFO buffers Yoshihiro YUNOMAE
2014-03-14 12:04 ` One Thousand Gnomes
2014-03-14 14:38 ` Heikki Krogerus
2014-03-17 6:04 ` Yoshihiro YUNOMAE
2014-03-14 14:16 ` Heikki Krogerus
2014-03-17 3:03 ` Yoshihiro YUNOMAE [this message]
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=532665ED.7090401@hitachi.com \
--to=yoshihiro.yunomae.ez@hitachi.com \
--cc=asierra@xes-inc.com \
--cc=gnomes@lxorguk.ukuu.org.uk \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=hidehiro.kawai.ez@hitachi.com \
--cc=jg1.han@samsung.com \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=swarren@nvidia.com \
--cc=yrl.pp-manager.tt@hitachi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.