From: Daniel Henrique Barboza <danielhb413@gmail.com>
To: Glenn Miles <milesg@linux.vnet.ibm.com>, qemu-ppc@nongnu.org
Cc: qemu-devel@nongnu.org, clg@kaod.org, npiggin@gmail.com,
fbarrat@linux.ibm.com, philmd@linaro.org
Subject: Re: [PATCH v3 0/2] Add PowerNV I2C Controller Model
Date: Tue, 7 Nov 2023 15:54:13 -0300 [thread overview]
Message-ID: <651c05ab-dfa6-4511-a088-3e3b303fe6fc@gmail.com> (raw)
In-Reply-To: <20231016222013.3739530-1-milesg@linux.vnet.ibm.com>
Queued in gitlab.com/danielhb/qemu/tree/ppc-next. Thanks,
Daniel
On 10/16/23 19:20, Glenn Miles wrote:
> Upstreams the PowerNV I2C controller model originally
> authored by Cédric Le Goater with minor changes by
> myself to split the actual addition of the model from
> wiring it up to a power processor model.
>
> This series only attaches the controller to the powernv9
> chip model, but is expected to eventually also be attached
> to the powernv10 chip model.
>
> Cédric Le Goater (2):
> ppc/pnv: Add an I2C controller model
> ppc/pnv: Connect I2C controller model to powernv9 chip
>
> hw/ppc/meson.build | 1 +
> hw/ppc/pnv.c | 28 ++
> hw/ppc/pnv_i2c.c | 697 +++++++++++++++++++++++++++++++++++++
> include/hw/ppc/pnv_chip.h | 8 +
> include/hw/ppc/pnv_i2c.h | 38 ++
> include/hw/ppc/pnv_xscom.h | 3 +
> 6 files changed, 775 insertions(+)
> create mode 100644 hw/ppc/pnv_i2c.c
> create mode 100644 include/hw/ppc/pnv_i2c.h
>
prev parent reply other threads:[~2023-11-07 18:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-16 22:20 [PATCH v3 0/2] Add PowerNV I2C Controller Model Glenn Miles
2023-10-16 22:20 ` [PATCH v3 1/2] ppc/pnv: Add an I2C controller model Glenn Miles
2023-10-16 22:20 ` [PATCH v3 2/2] ppc/pnv: Connect I2C controller model to powernv9 chip Glenn Miles
2023-10-17 7:01 ` [PATCH v3 0/2] Add PowerNV I2C Controller Model Cédric Le Goater
2023-10-17 20:52 ` Miles Glenn
2023-11-07 18:54 ` Daniel Henrique Barboza [this message]
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=651c05ab-dfa6-4511-a088-3e3b303fe6fc@gmail.com \
--to=danielhb413@gmail.com \
--cc=clg@kaod.org \
--cc=fbarrat@linux.ibm.com \
--cc=milesg@linux.vnet.ibm.com \
--cc=npiggin@gmail.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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).