From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Guanbing Huang <albanhuang@outlook.com>
Cc: gregkh@linuxfoundation.org, rafael.j.wysocki@intel.com,
linux-acpi@vger.kernel.org, tony@atomide.com,
john.ogness@linutronix.de, yangyicong@hisilicon.com,
jirislaby@kernel.org, linux-kernel@vger.kernel.org,
linux-serial@vger.kernel.org, lvjianmin@loongson.cn,
albanhuang@tencent.com, tombinfan@tencent.com
Subject: Re: [PATCH v5 0/3] serial: 8250_pnp: Support configurable reg shift property
Date: Mon, 8 Apr 2024 18:11:48 +0300 [thread overview]
Message-ID: <ZhQJNMM4J2KAAycn@smile.fi.intel.com> (raw)
In-Reply-To: <ZhQI1RgQtQuctUuL@smile.fi.intel.com>
On Mon, Apr 08, 2024 at 06:10:13PM +0300, Andy Shevchenko wrote:
> On Mon, Apr 08, 2024 at 11:36:21AM +0800, Guanbing Huang wrote:
> > From: Guanbing Huang <albanhuang@tencent.com>
> >
> > The 16550a serial port based on the ACPI table requires obtaining the
> > reg-shift attribute. In the ACPI scenario, If the reg-shift property
> > is not configured like in DTS, the 16550a serial driver cannot read or
> > write controller registers properly during initialization.
> >
> > To address the issue of configuring the reg-shift property, the
> > __uart_read_properties() universal interface is called to implement it.
> > Adaptation of PNP devices is done in the __uart_read_properties() function.
>
> Seems okay to me now,
> Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Note, you have an issue with your email server. The cover letter is not chained
with the patch series. You really want to fix that if you wish to contribute
to Linux kernel project via respective mailing lists.
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2024-04-08 15:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-08 3:36 [PATCH v5 0/3] serial: 8250_pnp: Support configurable reg shift property Guanbing Huang
2024-04-08 15:10 ` Andy Shevchenko
2024-04-08 15:11 ` Andy Shevchenko [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=ZhQJNMM4J2KAAycn@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=albanhuang@outlook.com \
--cc=albanhuang@tencent.com \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=john.ogness@linutronix.de \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=lvjianmin@loongson.cn \
--cc=rafael.j.wysocki@intel.com \
--cc=tombinfan@tencent.com \
--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