qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Dmitriy Sharikhin <d.sharikhin@yadro.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Cc: Igor Kononenko <i.kononenko@yadro.com>,
	"Alexander A. Filippov" <a.filippov@yadro.com>,
	Alexander Amelkin <a.amelkin@yadro.com>
Subject: Re: [PATCH v3] hw: gpio: introduce pcf8574 driver
Date: Mon, 11 Mar 2024 13:03:19 +0100	[thread overview]
Message-ID: <e7dc81df-1a51-4e0d-b865-5741803fb8cf@linaro.org> (raw)
In-Reply-To: <f1552d822276e878d84c01eba2cf2c7c9ebdde00.camel@yadro.com>

On 11/3/24 10:58, Dmitriy Sharikhin wrote:
> NXP PCF8574 and compatible ICs are simple I2C GPIO expanders.
> PCF8574 incorporates quasi-bidirectional IO, and simple
> communication protocol, when IO read is I2C byte read, and
> IO write is I2C byte write. User can think of it as
> open-drain port, when line high state is input and line low
> state is output.
> 
> Signed-off-by: Dmitrii Sharikhin <d.sharikhin@yadro.com>

If a patch is reviewed, please carry reviewers' tag:
https://www.qemu.org/docs/master/devel/submitting-a-patch.html#proper-use-of-reviewed-by-tags-can-aid-review

Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>

> ---
>   MAINTAINERS               |   6 ++
>   hw/gpio/Kconfig           |   4 +
>   hw/gpio/meson.build       |   1 +
>   hw/gpio/pcf8574.c         | 162 ++++++++++++++++++++++++++++++++++++++
>   include/hw/gpio/pcf8574.h |  15 ++++
>   5 files changed, 188 insertions(+)
>   create mode 100644 hw/gpio/pcf8574.c
>   create mode 100644 include/hw/gpio/pcf8574.h



  reply	other threads:[~2024-03-11 12:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-11  9:58 [PATCH v3] hw: gpio: introduce pcf8574 driver Dmitriy Sharikhin
2024-03-11 12:03 ` Philippe Mathieu-Daudé [this message]
2024-03-12  8:16 ` Philippe Mathieu-Daudé

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=e7dc81df-1a51-4e0d-b865-5741803fb8cf@linaro.org \
    --to=philmd@linaro.org \
    --cc=a.amelkin@yadro.com \
    --cc=a.filippov@yadro.com \
    --cc=d.sharikhin@yadro.com \
    --cc=i.kononenko@yadro.com \
    --cc=qemu-devel@nongnu.org \
    /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).