From: Evgeny Iakovlev <eiakovlev@linux.microsoft.com>
To: qemu-arm@nongnu.org
Cc: qemu-devel@nongnu.org, peter.maydell@linaro.org, philmd@linaro.org
Subject: [PATCH v4 0/5] Series of fixes for PL011 char device
Date: Mon, 23 Jan 2023 17:22:59 +0100 [thread overview]
Message-ID: <20230123162304.26254-1-eiakovlev@linux.microsoft.com> (raw)
v4:
* Fixed post_load hook to be backwards-migratable
* Refactored some code in 5/5 as per review comments
v3:
* Introduced a post_load hook for PL011State migration for
backwards-compatibility due to some input state fragility.
* No longer touching irq lines in reset method
* Minor changes based on review feedback.
v2:
* Moved FIFO depth refactoring part of FIFO flags change into its own
commit.
* Added a reset method for PL011
Evgeny Iakovlev (5):
hw/char/pl011: refactor FIFO depth handling code
hw/char/pl011: add post_load hook for backwards-compatibility
hw/char/pl011: implement a reset method
hw/char/pl011: better handling of FIFO flags on LCR reset
hw/char/pl011: check if UART is enabled before RX or TX operation
hw/char/pl011.c | 121 +++++++++++++++++++++++++++++++++-------
include/hw/char/pl011.h | 5 +-
2 files changed, 105 insertions(+), 21 deletions(-)
--
2.34.1
next reply other threads:[~2023-01-23 16:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-23 16:22 Evgeny Iakovlev [this message]
2023-01-23 16:23 ` [PATCH v4 1/5] hw/char/pl011: refactor FIFO depth handling code Evgeny Iakovlev
2023-01-23 16:23 ` [PATCH v4 2/5] hw/char/pl011: add post_load hook for backwards-compatibility Evgeny Iakovlev
2023-01-23 16:23 ` [PATCH v4 3/5] hw/char/pl011: implement a reset method Evgeny Iakovlev
2023-01-23 16:23 ` [PATCH v4 4/5] hw/char/pl011: better handling of FIFO flags on LCR reset Evgeny Iakovlev
2023-01-23 16:23 ` [PATCH v4 5/5] hw/char/pl011: check if UART is enabled before RX or TX operation Evgeny Iakovlev
2023-02-02 17:54 ` [PATCH v4 0/5] Series of fixes for PL011 char device Peter Maydell
2023-02-14 17:19 ` eiakovlev
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=20230123162304.26254-1-eiakovlev@linux.microsoft.com \
--to=eiakovlev@linux.microsoft.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).