Linux CXL
 help / color / mirror / Atom feed
From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: Shesha Bhushan Sreenivasamurthy <sheshas@marvell.com>
Cc: "linux-cxl@vger.kernel.org" <linux-cxl@vger.kernel.org>
Subject: Re: I2C Multi-master and Controller Slave Mode in QEMU
Date: Mon, 22 May 2023 15:41:35 +0100	[thread overview]
Message-ID: <20230522154135.00002be3@Huawei.com> (raw)
In-Reply-To: <DM6PR18MB2844C8CDBF085BE599F98EBEAF7C9@DM6PR18MB2844.namprd18.prod.outlook.com>

On Fri, 19 May 2023 19:43:25 +0000
Shesha Bhushan Sreenivasamurthy <sheshas@marvell.com> wrote:

> Hi,
>    Is there any implementation of I2C Multi-master and Controller Slave Mode in QEMU for x86 ?
> 
> What I want is to create CXL-I2C device that can exercise DCD commands via FM-API. For that I need a bus that can support both master and slave on x86. Is there one available ?

I have a side project underway to make this work.  It will be a little 'unusual'
as it'll bolt an aspeed-i2c controller with the right support onto an x86 host.
Might take me a few more days to get that working.  I have it up and running
with ACPI on an arm64 host (a few minor tweaks needed to the aspeed-i2c kernel
driver which I'll also post - mostly upstreamable but there are a couple of
hacks for now).

Currently that aspeed device is the only i2c controller that supports MCTP that has
some patches on list to do everything you want.

> 
> The second question is, can qemu-cxltype3 device be used on ARM ?

Yes, but you need the out of mainline patches from
gitlab.com/jic23/qemu Use the previous dated tag though as latest has some issues
(bad choice of base which turned out to crash :)

I'll be putting together a fixed version of that in next day or two.

https://gitlab.com/jic23/qemu/-/tree/cxl-2023-04-19?ref_type=heads
for now.

That includes support for the aspeed-i2c controller but with dt only which isn't
that helpful if you want to also use the CXL drivers.

Anyhow, it's a watch this space for now. Hopefully I'll get the PoC code in a shape
to share later this week.

Jonathan




  reply	other threads:[~2023-05-22 14:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-19 19:43 I2C Multi-master and Controller Slave Mode in QEMU Shesha Bhushan Sreenivasamurthy
2023-05-22 14:41 ` Jonathan Cameron [this message]
2023-05-23 22:08   ` [EXT] " Shesha Bhushan Sreenivasamurthy
2023-05-24 16:39     ` Jonathan Cameron
2023-05-24 17:48       ` Shesha Bhushan Sreenivasamurthy
2023-05-25 16:23         ` Jonathan Cameron
2023-06-01 23:07           ` Shesha Bhushan Sreenivasamurthy
2023-06-02 12:25             ` Jonathan Cameron
2023-06-02 23:58               ` Shesha Bhushan Sreenivasamurthy

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=20230522154135.00002be3@Huawei.com \
    --to=jonathan.cameron@huawei.com \
    --cc=linux-cxl@vger.kernel.org \
    --cc=sheshas@marvell.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