From: Yicong Yang <yangyicong@huawei.com>
To: John Ogness <john.ogness@linutronix.de>
Cc: <gregkh@linuxfoundation.org>, <jirislaby@kernel.org>,
<tony@atomide.com>, <linux-kernel@vger.kernel.org>,
<linux-serial@vger.kernel.org>, <yangyicong@hisilicon.com>,
<andriy.shevchenko@linux.intel.com>, <tglx@linutronix.de>,
<linuxarm@huawei.com>, <prime.zeng@hisilicon.com>,
<jonathan.cameron@huawei.com>, <fanghao11@huawei.com>
Subject: Re: [PATCH] serial: port: Don't suspend if the port is still busy
Date: Mon, 5 Feb 2024 17:00:11 +0800 [thread overview]
Message-ID: <d25d1d33-6a10-4e23-5ab2-f02ed4b72fac@huawei.com> (raw)
In-Reply-To: <878r3zpaba.fsf@jogness.linutronix.de>
On 2024/2/5 16:47, John Ogness wrote:
> On 2024-02-04, Yicong Yang <yangyicong@huawei.com> wrote:
>> diff --git a/drivers/tty/serial/serial_port.c b/drivers/tty/serial/serial_port.c
>> index 88975a4df306..60d1eec6b6b7 100644
>> --- a/drivers/tty/serial/serial_port.c
>> +++ b/drivers/tty/serial/serial_port.c
>> @@ -46,8 +46,28 @@ static int serial_port_runtime_resume(struct device *dev)
>> return 0;
>> }
>>
>> +static int serial_port_runtime_suspend(struct device *dev)
>> +{
>> + struct serial_port_device *port_dev = to_serial_base_port_device(dev);
>> + struct uart_port *port;
>> + unsigned long flags;
>> +
>> + port = port_dev->port;
>> +
>> + if (port->flags & UPF_DEAD)
>> + return 0;
>> +
>> + spin_lock_irqsave(&port->lock, flags);
>> + if (__serial_port_busy(port))
>> + pm_request_resume(dev);
>> + spin_unlock_irqrestore(&port->lock, flags);
>
> Please use the wrapper functions for the uart port lock:
>
> uart_port_lock_irqsave()
> uart_port_unlock_irqrestore()
>
Sure. Thanks for the information.
prev parent reply other threads:[~2024-02-05 9:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-04 3:19 Yicong Yang
2024-02-05 6:51 ` Tony Lindgren
2024-02-05 8:55 ` Yicong Yang
2024-02-05 9:07 ` Tony Lindgren
2024-02-06 8:02 ` Yicong Yang
2024-02-05 8:47 ` John Ogness
2024-02-05 9:00 ` Yicong Yang [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=d25d1d33-6a10-4e23-5ab2-f02ed4b72fac@huawei.com \
--to=yangyicong@huawei.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=fanghao11@huawei.com \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=john.ogness@linutronix.de \
--cc=jonathan.cameron@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=prime.zeng@hisilicon.com \
--cc=tglx@linutronix.de \
--cc=tony@atomide.com \
--cc=yangyicong@hisilicon.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®