From: Peter Maydell <peter.maydell@linaro.org>
To: Harshit Aghera <haghera@nvidia.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Shakeeb Pasha <spasha@nvidia.com>,
Arun D Patil <arundp@nvidia.com>,
Raghul Rajakumar <rrajakumar@nvidia.com>
Subject: Re: Requesting suggestions on how to access I2C Bus of the Guest OS
Date: Mon, 12 Feb 2024 16:29:13 +0000 [thread overview]
Message-ID: <CAFEAcA-VLEm5BYptxQ+hsQKz7ARC+xAbRqdqZViAmi_g7=btfA@mail.gmail.com> (raw)
In-Reply-To: <LV2PR12MB598943FA3FC5605955DCF2A0D8482@LV2PR12MB5989.namprd12.prod.outlook.com>
On Mon, 12 Feb 2024 at 16:01, Harshit Aghera <haghera@nvidia.com> wrote:
>
> We have a Linux image targeted for architecture Cortex A7, that we are running inside QEMU on x86 machine.
>
>
>
> Our Linux image has I2C slave with EEPROM backend, instantiated from user-space. Reference - Linux I2C slave EEPROM backend — The Linux Kernel documentation.
>
> Commands used from user-space to instantiate these I2C slaves –
>
> echo slave-24c512ro 0x1054 > /sys/bus/i2c/devices/i2c-0/new_device
>
> echo slave-24c02 0x1054 > /sys/bus/i2c/devices/i2c-1/new_device
>
>
>
> Is there a way to send I2C messages to these I2C buses (bus 0 and bus 1) on the Guest OS, as a I2C Master from the Host OS?
>
> Is there a way to send I2C messages to these I2C buses from a separate QEMU Instance’s Guest OS acting as a I2C Master?
No; our i2c bus framework does not currently support either of those
things.
thanks
-- PMM
prev parent reply other threads:[~2024-02-12 16:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-12 15:09 Requesting suggestions on how to access I2C Bus of the Guest OS Harshit Aghera
2024-02-12 16:29 ` Peter Maydell [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='CAFEAcA-VLEm5BYptxQ+hsQKz7ARC+xAbRqdqZViAmi_g7=btfA@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=arundp@nvidia.com \
--cc=haghera@nvidia.com \
--cc=qemu-devel@nongnu.org \
--cc=rrajakumar@nvidia.com \
--cc=spasha@nvidia.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).