From: Alexander Hansen <alexander.hansen@9elements.com>
To: qemu-devel@nongnu.org
Cc: Alexander Hansen <alexander.hansen@9elements.com>
Subject: [PATCH v4 0/5] initial support for yosemite v4
Date: Fri, 15 May 2026 16:57:57 +0200 [thread overview]
Message-ID: <20260515150610.381066-1-alexander.hansen@9elements.com> (raw)
Add initial and incomplete support for yosemite v4 BMC-side emulation.
As part of this effort 3 new sensor ICs are added.
Thanks to Cedric and Titus for review of patchset 3.
Summary of changes from patchset 3:
- changed commit message for functional test to be more clear
- amended my .gitconfig to present changes matching qemu orderfil
- max31790: fix indent to 4 spaces
- max31790: removed extra header file from patch
- max11615: rename variable to channel_select to match qemu coding style
- max11615: fix typo
- all sensors in this series: fix reset handling. Set dc->legacy_reset
instead of manually calling reset function in realize.
I was mildly confused because both tmp105 and tmp421 call a reset
function in their realize functions. Anyways, hopefully i did it right
this time :)
Alexander Hansen (5):
ast2600: yosemite4 initial support
ast2600: yosemite4 functional test
hw/sensor: MAX31790 support
hw/sensor: support MAX11615
hw/sensor: support Texas Instruments ADC128D818
MAINTAINERS | 3 +
include/hw/sensor/adc128d818.h | 20 +
include/hw/sensor/max11615.h | 21 +
hw/arm/aspeed_ast2600_fby4.c | 280 +++++++++++++
hw/sensor/adc128d818.c | 410 +++++++++++++++++++
hw/sensor/max11615.c | 206 ++++++++++
hw/sensor/max31790.c | 501 +++++++++++++++++++++++
hw/arm/Kconfig | 3 +
hw/arm/meson.build | 1 +
hw/sensor/Kconfig | 12 +
hw/sensor/meson.build | 3 +
hw/sensor/trace-events | 24 ++
tests/functional/arm/meson.build | 2 +
tests/functional/arm/test_aspeed_fby4.py | 80 ++++
14 files changed, 1566 insertions(+)
create mode 100644 include/hw/sensor/adc128d818.h
create mode 100644 include/hw/sensor/max11615.h
create mode 100644 hw/arm/aspeed_ast2600_fby4.c
create mode 100644 hw/sensor/adc128d818.c
create mode 100644 hw/sensor/max11615.c
create mode 100644 hw/sensor/max31790.c
create mode 100755 tests/functional/arm/test_aspeed_fby4.py
--
2.54.0
next reply other threads:[~2026-05-15 15:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-15 14:57 Alexander Hansen [this message]
2026-05-15 14:57 ` [PATCH v4 1/5] ast2600: yosemite4 initial support Alexander Hansen
2026-05-15 16:30 ` Cédric Le Goater
2026-05-15 14:57 ` [PATCH v4 2/5] ast2600: yosemite4 functional test Alexander Hansen
2026-05-15 16:31 ` Cédric Le Goater
2026-05-15 14:58 ` [PATCH v4 3/5] hw/sensor: MAX31790 support Alexander Hansen
2026-05-15 14:58 ` [PATCH v4 4/5] hw/sensor: support MAX11615 Alexander Hansen
2026-05-15 14:58 ` [PATCH v4 5/5] hw/sensor: support Texas Instruments ADC128D818 Alexander Hansen
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=20260515150610.381066-1-alexander.hansen@9elements.com \
--to=alexander.hansen@9elements.com \
--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.