From: Eric Blake <eblake@redhat.com>
To: Ernest Esene <eroken1@gmail.com>, qemu-devel@nongnu.org
Cc: "Stefan Hajnoczi" <stefanha@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Markus Armbruster" <armbru@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] chardev/char-i2c: Implement Linux I2C character device
Date: Fri, 3 May 2019 15:24:06 -0500 [thread overview]
Message-ID: <7f3b0a70-cec4-f267-c1fa-0bed6851b8cf@redhat.com> (raw)
In-Reply-To: <20190503193141.GA17700@erokenlabserver>
[-- Attachment #1: Type: text/plain, Size: 1530 bytes --]
On 5/3/19 2:31 PM, Ernest Esene wrote:
> Add support for Linux I2C character device for I2C device passthrough
> For example:
> -chardev linux-i2c,address=0x46,path=/dev/i2c-N,id=i2c-chardev
>
> Signed-off-by: Ernest Esene <eroken1@gmail.com>
> ---
Just an interface review:
> +++ b/qapi/char.json
> @@ -240,6 +240,21 @@
> 'data': { 'device': 'str' },
> 'base': 'ChardevCommon' }
>
> +##
> +# @ChardevI2c:
> +#
> +# Configuration info for i2c chardev (only on linux).
Rather than a parenthetical comment, you could use:
> +#
> +# @device: The name of the special file for the device,
> +# i.e. /dev/i2c-0 on linux
> +# @address: The address of the i2c device on the host.
> +#
> +##
Missing a 'Since: 4.1' line.
> +{ 'struct': 'ChardevI2c',
> + 'data': { 'device': 'str',
> + 'address': 'int16'},
> + 'base': 'ChardevCommon'}
'if': 'defined(CONFIG_LINUX)'
as part of the usage of this struct, so that introspection will only see
the struct where it can be used.
> +
> ##
> # @ChardevSocket:
> #
> @@ -398,6 +413,7 @@
> 'data': { 'file': 'ChardevFile',
> 'serial': 'ChardevHostdev',
> 'parallel': 'ChardevHostdev',
> + 'i2c': 'ChardevI2c',
> 'pipe': 'ChardevHostdev',
> 'socket': 'ChardevSocket',
> 'udp': 'ChardevUdp',
>
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Eric Blake <eblake@redhat.com>
To: Ernest Esene <eroken1@gmail.com>, qemu-devel@nongnu.org
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
"Markus Armbruster" <armbru@redhat.com>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] chardev/char-i2c: Implement Linux I2C character device
Date: Fri, 3 May 2019 15:24:06 -0500 [thread overview]
Message-ID: <7f3b0a70-cec4-f267-c1fa-0bed6851b8cf@redhat.com> (raw)
Message-ID: <20190503202406.3Jl0NPAg5JtgaE6Fa8A2gqoK1jJ_dVcGojQhKNMWFmw@z> (raw)
In-Reply-To: <20190503193141.GA17700@erokenlabserver>
[-- Attachment #1: Type: text/plain, Size: 1530 bytes --]
On 5/3/19 2:31 PM, Ernest Esene wrote:
> Add support for Linux I2C character device for I2C device passthrough
> For example:
> -chardev linux-i2c,address=0x46,path=/dev/i2c-N,id=i2c-chardev
>
> Signed-off-by: Ernest Esene <eroken1@gmail.com>
> ---
Just an interface review:
> +++ b/qapi/char.json
> @@ -240,6 +240,21 @@
> 'data': { 'device': 'str' },
> 'base': 'ChardevCommon' }
>
> +##
> +# @ChardevI2c:
> +#
> +# Configuration info for i2c chardev (only on linux).
Rather than a parenthetical comment, you could use:
> +#
> +# @device: The name of the special file for the device,
> +# i.e. /dev/i2c-0 on linux
> +# @address: The address of the i2c device on the host.
> +#
> +##
Missing a 'Since: 4.1' line.
> +{ 'struct': 'ChardevI2c',
> + 'data': { 'device': 'str',
> + 'address': 'int16'},
> + 'base': 'ChardevCommon'}
'if': 'defined(CONFIG_LINUX)'
as part of the usage of this struct, so that introspection will only see
the struct where it can be used.
> +
> ##
> # @ChardevSocket:
> #
> @@ -398,6 +413,7 @@
> 'data': { 'file': 'ChardevFile',
> 'serial': 'ChardevHostdev',
> 'parallel': 'ChardevHostdev',
> + 'i2c': 'ChardevI2c',
> 'pipe': 'ChardevHostdev',
> 'socket': 'ChardevSocket',
> 'udp': 'ChardevUdp',
>
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-05-03 20:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-03 19:31 [Qemu-devel] [PATCH] chardev/char-i2c: Implement Linux I2C character device Ernest Esene
2019-05-03 19:31 ` Ernest Esene
2019-05-03 20:24 ` Eric Blake [this message]
2019-05-03 20:24 ` Eric Blake
2019-05-03 21:46 ` Ernest Esene
2019-05-03 21:46 ` Ernest Esene
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=7f3b0a70-cec4-f267-c1fa-0bed6851b8cf@redhat.com \
--to=eblake@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@redhat.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).