From: Guanbing Huang <albanhuang0@gmail.com>
To: gregkh@linuxfoundation.org, andriy.shevchenko@intel.com,
rafael.j.wysocki@intel.com
Cc: 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: [PATCH v7 0/3] serial: 8250_pnp: Support configurable reg shift property
Date: Fri, 12 Apr 2024 11:23:51 +0800 [thread overview]
Message-ID: <cover.1712890897.git.albanhuang@tencent.com> (raw)
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.
Guanbing Huang (3):
PNP: Add dev_is_pnp() macro
serial: port: Add support of PNP IRQ to __uart_read_properties()
serial: 8250_pnp: Support configurable reg shift property
drivers/tty/serial/8250/8250_pnp.c | 40 +++++++++++++++++++-----------
drivers/tty/serial/serial_port.c | 7 +++++-
include/linux/pnp.h | 4 +++
3 files changed, 35 insertions(+), 16 deletions(-)
--
2.17.1
next reply other threads:[~2024-04-12 3:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-12 3:23 Guanbing Huang [this message]
2024-04-12 3:24 ` [PATCH v7 1/3] PNP: Add dev_is_pnp() macro Guanbing Huang
2024-04-12 15:29 ` Andy Shevchenko
2024-04-12 15:52 ` Andy Shevchenko
2024-04-12 3:24 ` [PATCH v7 2/3] serial: port: Add support of PNP IRQ to __uart_read_properties() Guanbing Huang
2024-04-12 3:24 ` [PATCH v7 3/3] serial: 8250_pnp: Support configurable reg shift property Guanbing Huang
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=cover.1712890897.git.albanhuang@tencent.com \
--to=albanhuang0@gmail.com \
--cc=albanhuang@tencent.com \
--cc=andriy.shevchenko@intel.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 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.