From: Geert Uytterhoeven <geert@linux-m68k.org>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
Cc: Peter Maydell <peter.maydell@linaro.org>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Linus Walleij <linus.walleij@linaro.org>,
Magnus Damm <magnus.damm@gmail.com>,
QEMU Developers <qemu-devel@nongnu.org>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
qemu-arm <qemu-arm@nongnu.org>, Alexander Graf <graf@amazon.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Bartosz Golaszewski <bartekgola@gmail.com>
Subject: Re: [PATCH QEMU v2 3/5] Add a GPIO backend using libgpiod
Date: Thu, 23 Apr 2020 11:41:29 +0200 [thread overview]
Message-ID: <CAMuHMdWf2RfGvSizXKonmAB84kPyAPwZ3mF1PayK_mdn=wwRkw@mail.gmail.com> (raw)
In-Reply-To: <5dbfd026-3807-b122-ce60-1339a5252fca@amsat.org>
Hi Philippe,
Thanks for your comments!
On Thu, Apr 23, 2020 at 11:28 AM Philippe Mathieu-Daudé <f4bug@amsat.org> wrote:
> On 4/23/20 11:01 AM, Geert Uytterhoeven wrote:
> > Add a GPIO controller backend, to connect virtual GPIOs on the guest to
> > physical GPIOs on the host. This allows the guest to control any
> > external device connected to the physical GPIOs.
> >
> > Features and limitations:
> > - The backend uses libgpiod on Linux,
> > - For now only GPIO outputs are supported,
> > - The number of GPIO lines mapped is limited to the number of GPIO
> > lines available on the virtual GPIO controller.
> >
> > Future work:
> > - GPIO inputs,
> > - GPIO line configuration,
> > - Optimizations for controlling multiple GPIO lines at once,
> > - ...
> >
> > Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> > --- /dev/null
> > +++ b/backends/gpiodev.c
> > @@ -0,0 +1,94 @@
> > +/*
> > + * QEMU GPIO Backend
> > + *
> > + * Copyright (C) 2018-2020 Glider bv
> > + *
> > + * SPDX-License-Identifier: GPL-2.0-or-later
> > + */
> > +
> > +#include <errno.h>
>
> <errno.h> probably not needed.
It is indeed included by one of the other header files.
What is the QEMU policy w.r.t. that?
>
> > +#include <gpiod.h>
>
> Please move this one...
>
> > +
> > +#include "qemu/osdep.h"
> > +#include "qemu/config-file.h"
> > +#include "qemu/cutils.h"
I forgot to remove the two above...
> > +#include "qemu/error-report.h"
> > +#include "qemu/module.h"
> > +#include "qemu/option.h"
... and the two above.
> > +#include "qapi/error.h"
> > +
> > +#include "sysemu/gpiodev.h"
> > +
> > +#include "hw/irq.h"
> > +#include "hw/qdev-core.h"
>
> ... here:
>
> #include <gpiod.h>
OK.
> > --- a/configure
> > +++ b/configure
> > @@ -509,6 +509,7 @@ libpmem=""
> > default_devices="yes"
> > plugins="no"
> > fuzzing="no"
> > +gpio=""
>
> Maybe name this feature 'libgpiod'?
Makes sense.
> >
> > supported_cpu="no"
> > supported_os="no"
> > @@ -1601,6 +1602,10 @@ for opt do
> > ;;
> > --gdb=*) gdb_bin="$optarg"
> > ;;
> > + --disable-gpio) gpio="no"
> > + ;;
> > + --enable-gpio) gpio="yes"
>
> Ditto: --enable-libgpiod, because else it seems rather confusing.
OK.
> > --- /dev/null
> > +++ b/include/sysemu/gpiodev.h
> > @@ -0,0 +1,12 @@
> > +/*
> > + * QEMU GPIO Backend
> > + *
> > + * Copyright (C) 2018-2020 Glider bv
> > + *
> > + * SPDX-License-Identifier: GPL-2.0-or-later
> > + */
> > +
> > +#include "qemu/typedefs.h"
>
> "qemu/typedefs.h" not needed in includes.
While removing that works, it does mean the header file is no longer
self-contained:
include/sysemu/gpiodev.h:10:23: error: unknown type name ‘DeviceState’
> > +
> > +void qemu_gpiodev_add(DeviceState *dev, const char *name, unsigned int maxgpio,
> > + Error **errp);
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2020-04-23 9:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-23 9:01 [PATCH QEMU v2 0/5] Add a GPIO backend Geert Uytterhoeven
2020-04-23 9:01 ` [PATCH QEMU v2 1/5] ARM: PL061: Move TYPE_PL061 to hw/gpio/pl061.h Geert Uytterhoeven
2020-04-23 9:22 ` Philippe Mathieu-Daudé
2020-04-23 9:01 ` [PATCH QEMU v2 2/5] ARM: PL061: Extract pl061_create_fdt() Geert Uytterhoeven
2020-04-23 9:23 ` Philippe Mathieu-Daudé
2020-04-23 9:01 ` [PATCH QEMU v2 3/5] Add a GPIO backend using libgpiod Geert Uytterhoeven
2020-04-23 9:28 ` Philippe Mathieu-Daudé
2020-04-23 9:41 ` Geert Uytterhoeven [this message]
2020-04-23 10:06 ` Philippe Mathieu-Daudé
2020-04-23 9:01 ` [PATCH QEMU v2 4/5] ARM: PL061: Add gpiodev support Geert Uytterhoeven
2020-04-23 9:33 ` Philippe Mathieu-Daudé
2020-04-23 10:08 ` Philippe Mathieu-Daudé
2020-07-16 14:10 ` Geert Uytterhoeven
2020-04-23 9:01 ` [PATCH QEMU v2 5/5] hw/arm/virt: Add dynamic PL061 GPIO support Geert Uytterhoeven
2020-04-23 9:13 ` [PATCH QEMU v2 0/5] Add a GPIO backend no-reply
2020-04-23 9:34 ` no-reply
2020-04-23 9:40 ` no-reply
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='CAMuHMdWf2RfGvSizXKonmAB84kPyAPwZ3mF1PayK_mdn=wwRkw@mail.gmail.com' \
--to=geert@linux-m68k.org \
--cc=bartekgola@gmail.com \
--cc=f4bug@amsat.org \
--cc=geert+renesas@glider.be \
--cc=graf@amazon.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--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).