[PATCH qemu v2 0/7] Update opentitan uart (part of supporting opentitan version 1)

~lexbaileylowrisc posted 7 patches 3 days, 6 hours ago
Patches applied successfully (tree, apply log)
git fetch https://github.com/patchew-project/qemu tags/patchew/177564643888.23414.7922925369077631439-0@git.sr.ht
Maintainers: Paolo Bonzini <pbonzini@redhat.com>, "Marc-André Lureau" <marcandre.lureau@redhat.com>, Alistair Francis <Alistair.Francis@wdc.com>, Palmer Dabbelt <palmer@dabbelt.com>, Weiwei Li <liwei1518@gmail.com>, Daniel Henrique Barboza <daniel.barboza@oss.qualcomm.com>, Liu Zhiwei <zhiwei_liu@linux.alibaba.com>, Chao Liu <chao.liu.zevorn@gmail.com>
MAINTAINERS                  |   1 +
hw/char/Kconfig              |   3 +
hw/char/ibex_uart.c          | 569 ---------------------------
hw/char/meson.build          |   2 +-
hw/char/ot_uart.c            | 741 +++++++++++++++++++++++++++++++++++
hw/char/trace-events         |   8 +
hw/riscv/Kconfig             |   1 +
hw/riscv/opentitan.c         |   3 +-
include/hw/char/ibex_uart.h  |  73 ----
include/hw/char/ot_uart.h    |  61 +++
include/hw/riscv/opentitan.h |   4 +-
11 files changed, 820 insertions(+), 646 deletions(-)
delete mode 100644 hw/char/ibex_uart.c
create mode 100644 hw/char/ot_uart.c
delete mode 100644 include/hw/char/ibex_uart.h
create mode 100644 include/hw/char/ot_uart.h
[PATCH qemu v2 0/7] Update opentitan uart (part of supporting opentitan version 1)
Posted by ~lexbaileylowrisc 3 days, 6 hours ago
Second revision of the patch set that updates the OpenTitan uart to
version 1

I have made changes as per the review comments from last time. This is
now split into smaller commits. The first renames ibex_uart to ot_uart,
and the rest introduce the various changes step by step.

The details of the version 1 of the UART are found here:
https://opentitan.org/book/hw/ip/uart/index.html
(This URL is added to the file header in one of these commits)

The changes, as split across these commits, are: switching to new reset
api, updating the register and field definitions to match the latest
version of the UART, adding the missing IRQs required for the latest
version, implementing the features the various hardware features that
were missing.

Finally, I have also updated the file headers and added the tracing
changes.

Lex Bailey (7):
  Rename ibex_uart to ot_uart
  ot_uart: move to new reset API
  ot_uart: update register defs, switch to Fifo8 for tx/rx buffers
  ot_uart: replace individual IRQ fields with array, add missing IRQs
  ot_uart: implement missing features
  ot_uart: update file headers with new authorship and documentation URL
  ot_uart: add tracing

 MAINTAINERS                  |   1 +
 hw/char/Kconfig              |   3 +
 hw/char/ibex_uart.c          | 569 ---------------------------
 hw/char/meson.build          |   2 +-
 hw/char/ot_uart.c            | 741 +++++++++++++++++++++++++++++++++++
 hw/char/trace-events         |   8 +
 hw/riscv/Kconfig             |   1 +
 hw/riscv/opentitan.c         |   3 +-
 include/hw/char/ibex_uart.h  |  73 ----
 include/hw/char/ot_uart.h    |  61 +++
 include/hw/riscv/opentitan.h |   4 +-
 11 files changed, 820 insertions(+), 646 deletions(-)
 delete mode 100644 hw/char/ibex_uart.c
 create mode 100644 hw/char/ot_uart.c
 delete mode 100644 include/hw/char/ibex_uart.h
 create mode 100644 include/hw/char/ot_uart.h

-- 
2.49.1
Re: [PATCH qemu v2 0/7] Update opentitan uart (part of supporting opentitan version 1)
Posted by Alistair Francis 1 day, 14 hours ago
On Thu, Apr 9, 2026 at 5:31 AM ~lexbaileylowrisc
<lexbaileylowrisc@git.sr.ht> wrote:
>
> Second revision of the patch set that updates the OpenTitan uart to
> version 1
>
> I have made changes as per the review comments from last time. This is
> now split into smaller commits. The first renames ibex_uart to ot_uart,
> and the rest introduce the various changes step by step.
>
> The details of the version 1 of the UART are found here:
> https://opentitan.org/book/hw/ip/uart/index.html
> (This URL is added to the file header in one of these commits)

Can you include a version as well. So we can say we specifically
support version ... (git commit or release is fine)

Alistair