qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Graeme Gregory <quic_ggregory@quicinc.com>
To: Troy Lee <troy_lee@aspeedtech.com>
Cc: leetroy@gmail.com, qemu-devel@nongnu.org, hailin.wu@aspeedtech.com
Subject: Re: [PATCH v3 0/2] Aspeed I3C device model
Date: Wed, 12 Jan 2022 10:57:04 +0000	[thread overview]
Message-ID: <20220112105704.ovkq5yxl6phzeqi3@ggregory-linuxws> (raw)
In-Reply-To: <20220111084546.4145785-1-troy_lee@aspeedtech.com>

On Tue, Jan 11, 2022 at 04:45:44PM +0800, Troy Lee wrote:
> This series of patch introduce a dummy implemenation of aspeed i3c
> model, and it provide just enough information for guest machine.
> However, the driver probing is still failed, but it will not cause
> kernel panic.
> 

These patches arrived just in time for our i3c testing. This stops
our CI halting due to kernel panic on i3c probing.

Reviewed-by: Graeme Gregory <quic_ggregory@quicinc.com>
Tested-by: Graeme Gregory <quic_ggregory@quicinc.com>

> v3:
> - Remove unused AspeedI3CClass
> - Refine memory region
> - Refine register reset
> - Remove unrelated changes to SPI2 address
> - Remove i3c controller irq line
> 
> v2:
> - Split i3c model into i3c and i3c_device
> - Create 6x i3c devices
> - Using register fields macro
> - Rebase to mainline QEMU
> 
> Troy Lee (2):
>   Introduce a dummy AST2600 I3C model.
>   This patch includes i3c instance in ast2600 soc.
> 
>  hw/arm/aspeed_ast2600.c      |  16 ++
>  hw/misc/aspeed_i3c.c         | 381 +++++++++++++++++++++++++++++++++++
>  hw/misc/meson.build          |   1 +
>  hw/misc/trace-events         |   6 +
>  include/hw/arm/aspeed_soc.h  |   3 +
>  include/hw/misc/aspeed_i3c.h |  48 +++++
>  6 files changed, 455 insertions(+)
>  create mode 100644 hw/misc/aspeed_i3c.c
>  create mode 100644 include/hw/misc/aspeed_i3c.h
> 
> -- 
> 2.25.1
> 
> 


  parent reply	other threads:[~2022-01-12 10:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-11  8:45 [PATCH v3 0/2] Aspeed I3C device model Troy Lee
2022-01-11  8:45 ` [PATCH v3 1/2] Introduce a dummy AST2600 I3C model Troy Lee
2022-01-11  9:05   ` Cédric Le Goater
2022-01-11  8:45 ` [PATCH v3 2/2] This patch includes i3c instance in ast2600 soc Troy Lee
2022-01-11  9:12   ` Cédric Le Goater
2022-01-20 16:01   ` Peter Maydell
2022-01-11  9:21 ` [PATCH v3 0/2] Aspeed I3C device model Cédric Le Goater
2022-01-12 10:57 ` Graeme Gregory [this message]
2022-01-12 12:45   ` Cédric Le Goater
2022-01-12 15:54     ` Graeme Gregory
2022-01-12 13:50   ` Troy Lee
2022-01-18 17:40 ` Peter Maydell

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=20220112105704.ovkq5yxl6phzeqi3@ggregory-linuxws \
    --to=quic_ggregory@quicinc.com \
    --cc=hailin.wu@aspeedtech.com \
    --cc=leetroy@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=troy_lee@aspeedtech.com \
    /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).