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: [EXT] Re: I2C Multi-master and Controller Slave Mode in QEMU
Date: Thu, 25 May 2023 17:23:07 +0100 [thread overview]
Message-ID: <20230525172307.00005a8b@Huawei.com> (raw)
In-Reply-To: <DM6PR18MB2844EBEBA8D10343B6DB763EAF419@DM6PR18MB2844.namprd18.prod.outlook.com>
> ss: Thats great ! Can you please share the code, both QEMU and kernel driver ?
QEMU: http://gitlab.com/jic23/qemu cxl-2023-05-25
https://lore.kernel.org/linux-cxl/20230525160859.32517-1-Jonathan.Cameron@huawei.com/T/#t
Kernel: To enable ACPI support in the aspeed-i2c driver used.
https://lore.kernel.org/linux-cxl/20230525152203.32190-1-Jonathan.Cameron@huawei.com/T/#t
Other than enabling MCTP + the aspeed-i2c driver, not much special needed kernel side
(all access is from the MCTP socket interface in userspace).
Have fun. It's pretty minimal at the moment.
For switches it pokes at the number of ports (the port status is all lies for now)
For Type 3 devices it just provide Identify.
I need to do a little more spec diving to check I've enabled them for the correct
MCTP bindings.
Jonathan
next prev parent reply other threads:[~2023-05-25 16:23 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
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 [this message]
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=20230525172307.00005a8b@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