qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@redhat.com>
To: Ernest Esene <eroken1@gmail.com>
Cc: "Stefan Hajnoczi" <stefanha@gmail.com>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	qemu-devel@nongnu.org,
	"Marc-André Lureau" <marcandre.lureau@redhat.com>,
	"Markus Armbruster" <armbru@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v3] chardev/char-i2c: Implement Linux I2C character device
Date: Fri, 17 May 2019 10:15:08 +0100	[thread overview]
Message-ID: <20190517091507.GF3679@stefanha-x1.localdomain> (raw)
In-Reply-To: <20190516134945.GA2293@erokenlabserver>

[-- Attachment #1: Type: text/plain, Size: 1347 bytes --]

On Thu, May 16, 2019 at 02:49:45PM +0100, Ernest Esene wrote:
> On Wed, May 15, 2019 at 03:17:12PM +0100, Stefan Hajnoczi wrote:
> > On Fri, May 10, 2019 at 07:04:10PM +0100, Ernest Esene wrote:
> > > Add support for Linux I2C character device for I2C device passthrough
> > > For example:
> > > -chardev i2c,address=0x46,path=/dev/i2c-N,id=i2c-chardev
> > > 
> > > QEMU supports emulation of I2C devices in software but currently can't
> > > passthrough to real I2C devices. This feature is needed by developers
> > > using QEMU for writing and testing software for I2C devices.
> > > 
> > > Signed-off-by: Ernest Esene <eroken1@gmail.com>
> > 
> > How is -chardev i2c meant to be used?  Do you have code to connect this
> > new chardev type to an emulated I2C bus?
> It is meant to be connected to emulated I2C bus as you've stated, but I
> don't have the code yet.

I'd like to see that code first, especially if it uses the chardev ioctl
to perform operations other than just read/write.  That could influence
the design of chardev-i2c.

Please keep this patch out-of-tree unless someone has an immediate use
for it.  If it gets merged too early (especially if a QEMU release is
made), then it's difficult to change the command-line interface if
changes are required to make it work with the I2C emulation.

Stefan

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

      reply	other threads:[~2019-05-17  9:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-10 18:04 [Qemu-devel] [PATCH v3] chardev/char-i2c: Implement Linux I2C character device Ernest Esene
2019-05-13 15:15 ` Markus Armbruster
2019-05-15 14:17 ` Stefan Hajnoczi
2019-05-16 13:49   ` Ernest Esene
2019-05-17  9:15     ` Stefan Hajnoczi [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=20190517091507.GF3679@stefanha-x1.localdomain \
    --to=stefanha@redhat.com \
    --cc=armbru@redhat.com \
    --cc=eroken1@gmail.com \
    --cc=marcandre.lureau@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.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).