From: Xia Fukun <xiafukun@huawei.com>
To: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.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 20:41:14 +0800 [thread overview]
Message-ID: <7ff795d4-fb67-4c5d-04be-4eff7f9b70fa@huawei.com> (raw)
In-Reply-To: <b22177d4-f911-cb8f-18e6-4ca8b2855c73@linux.intel.com>
On 2023/8/4 20:24, Ilpo Järvinen wrote:
> 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.
>>
>> 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).
>
Thank you very much for your reply. My understanding of this property is
indeed flawed. That is to say, in the "ri-override" property,
data->msr_mask_on will not be used, there will be no signal transmission?
In that case, you are right. My patch may be redundant.
prev parent reply other threads:[~2023-08-04 12:41 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
2023-08-04 12:41 ` Xia Fukun [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=7ff795d4-fb67-4c5d-04be-4eff7f9b70fa@huawei.com \
--to=xiafukun@huawei.com \
--cc=andy.shevchenko@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®