From: Jeuk Kim <jeuk20.kim@gmail.com>
To: qemu-devel@nongnu.org
Cc: jeuk20.kim@samsung.com, pbonzini@redhat.com,
qemu-block@nongnu.org, j-young.choi@samsung.com,
mikail.sadic@ibm.com, hyenc.jeong@samsung.com
Subject: [PATCH 0/2] hw/ufs: Add a generic SysBus frontend
Date: Fri, 7 Aug 2026 19:36:15 +0900 [thread overview]
Message-ID: <cover.1786096976.git.jeuk20.kim@samsung.com> (raw)
The UFS controller implementation is currently tied to its PCI QOM
device. This series separates the controller core from the PCI frontend
and adds a reusable SysBus frontend, following the AHCI model.
The existing "ufs" PCI device and its properties remain unchanged.
Platform-specific controllers can derive from TYPE_SYSBUS_UFS and keep
only their hardware-specific behavior.
Jeuk Kim (2):
hw/ufs: Separate the controller core from the PCI frontend
hw/ufs: Add a generic SysBus frontend
hw/ufs/Kconfig | 9 ++++
hw/ufs/lu.c | 2 +-
hw/ufs/meson.build | 4 +-
hw/ufs/trace-events | 4 +-
hw/ufs/ufs-pci.c | 112 ++++++++++++++++++++++++++++++++++++++++++++
hw/ufs/ufs-sysbus.c | 81 ++++++++++++++++++++++++++++++++
hw/ufs/ufs-sysbus.h | 22 +++++++++
hw/ufs/ufs.c | 108 +++++++++---------------------------------
hw/ufs/ufs.h | 14 ++++--
9 files changed, 262 insertions(+), 94 deletions(-)
create mode 100644 hw/ufs/ufs-pci.c
create mode 100644 hw/ufs/ufs-sysbus.c
create mode 100644 hw/ufs/ufs-sysbus.h
--
2.43.0
next reply other threads:[~2026-08-07 10:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-07 10:36 Jeuk Kim [this message]
2026-08-07 10:36 ` [PATCH 1/2] hw/ufs: Separate the controller core from the PCI frontend Jeuk Kim
2026-08-07 10:36 ` [PATCH 2/2] hw/ufs: Add a generic SysBus frontend Jeuk Kim
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.1786096976.git.jeuk20.kim@samsung.com \
--to=jeuk20.kim@gmail.com \
--cc=hyenc.jeong@samsung.com \
--cc=j-young.choi@samsung.com \
--cc=jeuk20.kim@samsung.com \
--cc=mikail.sadic@ibm.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@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 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.