From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Xia Fukun <xiafukun@huawei.com>
Cc: andy.shevchenko@gmail.com,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
heikki.krogerus@linux.intel.com,
LKML <linux-kernel@vger.kernel.org>,
linux-serial <linux-serial@vger.kernel.org>
Subject: Re: [PATCH] serial: 8250_dw: Fix assignment error of data in dw8250_probe()
Date: Fri, 4 Aug 2023 15:24:26 +0300 (EEST) [thread overview]
Message-ID: <b22177d4-f911-cb8f-18e6-4ca8b2855c73@linux.intel.com> (raw)
In-Reply-To: <20230804121607.191203-1-xiafukun@huawei.com>
On Fri, 4 Aug 2023, Xia Fukun wrote:
> When the "ri-override" property is present in the device,
> data->msr_mask_on and UART_MSR_RI should be used for
> OR-assignment. Fix the errors in it.
>
> Fixes: 1bd8edba10e6 ("serial: 8250_dw: adapt to unified device property interface")
> Signed-off-by: Xia Fukun <xiafukun@huawei.com>
> ---
> drivers/tty/serial/8250/8250_dw.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/tty/serial/8250/8250_dw.c b/drivers/tty/serial/8250/8250_dw.c
> index 7db51781289e..921b5f07828f 100644
> --- a/drivers/tty/serial/8250/8250_dw.c
> +++ b/drivers/tty/serial/8250/8250_dw.c
> @@ -587,7 +587,7 @@ static int dw8250_probe(struct platform_device *pdev)
>
> if (device_property_read_bool(dev, "ri-override")) {
> /* Always report Ring indicator as inactive */
> - data->msr_mask_off |= UART_MSR_RI;
> + data->msr_mask_on |= UART_MSR_RI;
> data->msr_mask_off |= UART_MSR_TERI;
The comment and also documentation says RI signal is always kept inactive
when ri-override is present.
In Documentation/devicetree/bindings/serial/snps-dw-apb-uart.yaml:
ri-override:
description: Override the RI modem status signal. This signal will always
be reported as inactive instead of being obtained from the modem status
register. Define this if your serial port does not use this pin.
...So why you think this patch is correct? (Please explain it in the v2
changelog clearly if you think your patch is still correct thing to do,
thank you).
--
i.
next prev parent reply other threads:[~2023-08-04 12:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-04 12:16 Xia Fukun
2023-08-04 12:24 ` Ilpo Järvinen [this message]
2023-08-04 12:41 ` Xia Fukun
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=b22177d4-f911-cb8f-18e6-4ca8b2855c73@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=andy.shevchenko@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=xiafukun@huawei.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®