From: Stepan Moskovchenko <stepanm@codeaurora.org>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Jamie Iles <jamie@jamieiles.com>,
linux-arm-msm@vger.kernel.org, davidb@codeaurora.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, rlove@google.com
Subject: Re: [PATCH 2/2] serial: msm: Add support for UARTDM cores
Date: Wed, 19 Jan 2011 18:38:14 -0800 [thread overview]
Message-ID: <4D37A016.8060902@codeaurora.org> (raw)
In-Reply-To: <20110119222407.GD6335@n2100.arm.linux.org.uk>
On 1/19/2011 2:24 PM, Russell King - ARM Linux wrote:
> On Wed, Jan 19, 2011 at 02:08:29PM -0800, Stepan Moskovchenko wrote:
>>>> + /* Mask conditions we're ignorning. */
>>>> + sr&= port->read_status_mask;
>>>> + if (sr& UART_SR_RX_BREAK)
>>>> + flag = TTY_BREAK;
>>>> + else if (sr& UART_SR_PAR_FRAME_ERR)
>>>> + flag = TTY_FRAME;
>>> It doesn't look like the flag is used anywhere after it has been
>>> assigned.
>> An artifact of an old driver. Removed.
> But still required to support proper error signalling.
>
On second thought, from poking around the kernel some more, I believe
the following should be a better approach:
if (sr & UART_SR_RX_BREAK) {
tty_insert_flip_char(tty, 0, TTY_BREAK);
} else if (sr & UART_SR_PAR_FRAME_ERR) {
tty_insert_flip_char(tty, 0, TTY_FRAME);
}
Russell, what do you think? Shall I make the change in v2?
Thanks
Steve
--
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
WARNING: multiple messages have this Message-ID (diff)
From: stepanm@codeaurora.org (Stepan Moskovchenko)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] serial: msm: Add support for UARTDM cores
Date: Wed, 19 Jan 2011 18:38:14 -0800 [thread overview]
Message-ID: <4D37A016.8060902@codeaurora.org> (raw)
In-Reply-To: <20110119222407.GD6335@n2100.arm.linux.org.uk>
On 1/19/2011 2:24 PM, Russell King - ARM Linux wrote:
> On Wed, Jan 19, 2011 at 02:08:29PM -0800, Stepan Moskovchenko wrote:
>>>> + /* Mask conditions we're ignorning. */
>>>> + sr&= port->read_status_mask;
>>>> + if (sr& UART_SR_RX_BREAK)
>>>> + flag = TTY_BREAK;
>>>> + else if (sr& UART_SR_PAR_FRAME_ERR)
>>>> + flag = TTY_FRAME;
>>> It doesn't look like the flag is used anywhere after it has been
>>> assigned.
>> An artifact of an old driver. Removed.
> But still required to support proper error signalling.
>
On second thought, from poking around the kernel some more, I believe
the following should be a better approach:
if (sr & UART_SR_RX_BREAK) {
tty_insert_flip_char(tty, 0, TTY_BREAK);
} else if (sr & UART_SR_PAR_FRAME_ERR) {
tty_insert_flip_char(tty, 0, TTY_FRAME);
}
Russell, what do you think? Shall I make the change in v2?
Thanks
Steve
--
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
next prev parent reply other threads:[~2011-01-20 2:38 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-19 3:26 [PATCH 2/2] serial: msm: Add support for UARTDM cores Stepan Moskovchenko
2011-01-19 3:26 ` Stepan Moskovchenko
2011-01-19 8:25 ` Jamie Iles
2011-01-19 8:25 ` Jamie Iles
2011-01-19 17:31 ` David Brown
2011-01-19 17:31 ` David Brown
2011-01-19 17:37 ` Jamie Iles
2011-01-19 17:37 ` Jamie Iles
2011-01-19 19:52 ` David Brown
2011-01-19 19:52 ` David Brown
2011-01-19 22:08 ` Stepan Moskovchenko
2011-01-19 22:08 ` Stepan Moskovchenko
2011-01-19 22:24 ` Russell King - ARM Linux
2011-01-19 22:24 ` Russell King - ARM Linux
2011-01-20 0:11 ` Stepan Moskovchenko
2011-01-20 0:11 ` Stepan Moskovchenko
2011-01-20 2:38 ` Stepan Moskovchenko [this message]
2011-01-20 2:38 ` Stepan Moskovchenko
2011-01-20 9:04 ` Russell King - ARM Linux
2011-01-20 9:04 ` Russell King - ARM Linux
2011-01-20 21:56 ` [PATCH v2 " Stepan Moskovchenko
2011-01-20 21:56 ` Stepan Moskovchenko
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=4D37A016.8060902@codeaurora.org \
--to=stepanm@codeaurora.org \
--cc=davidb@codeaurora.org \
--cc=jamie@jamieiles.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=rlove@google.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.