All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
Cc: Esteban Bosse <estebanbosse@gmail.com>,
	Joaquin de Andres <me@xcancerberox.com.ar>,
	qemu-arm <qemu-arm@nongnu.org>,
	QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [PATCH 7/7] hw/misc/mps2-fpgaio: Implement push-buttons
Date: Tue, 16 Jun 2020 13:29:45 +0100	[thread overview]
Message-ID: <CAFEAcA_GuCQRuwAgbQfHRKh732Kfzwj-zxX48tjBBnWCBjKLnQ@mail.gmail.com> (raw)
In-Reply-To: <84c3ce87-fefd-5741-7588-7a8ca12fde4c@amsat.org>

On Tue, 16 Jun 2020 at 11:40, Philippe Mathieu-Daudé <f4bug@amsat.org> wrote:
> On 6/16/20 12:27 PM, Peter Maydell wrote:
> > This change seems kind of pointless unless these GPIO lines are
> > actually wired up to something.
>
> Yes, I should have kept it out of this series, or documented
> better the goal in the cover.
>
> I'm setting the roots to motivate a team of developers to
> work on a visualization of the MPS2 board. The push-button is
> supported by Zephyr, so the the idea is the visualizer generates
> QMP GPIO event to be processed such in pca9552_set_led(), and
> interact with the guest firmware.

I think that having a framework so we can better model this kind
of push button / LED / similar thing is definitely good. I just
think we need to review it at the framework level first -- it
might turn out that actually the right way to wire up the push
button to the UI framework isn't with a GPIO wire at all.
Similarly with the other patchset that sends QMP events for
LEDs -- that also seems like it's half of a design and a bit
awkward to review without the context for what it connects to.

thanks
-- PMM


  reply	other threads:[~2020-06-16 12:31 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-16  6:31 [PATCH 0/7] mps2: Add few more peripherals Philippe Mathieu-Daudé
2020-06-16  6:31 ` [PATCH 1/7] hw/arm/mps2: Rename CMSDK AHB peripheral region Philippe Mathieu-Daudé
2020-06-16 10:13   ` Peter Maydell
2020-06-16  6:31 ` [PATCH 2/7] hw/arm/mps2: Rename dualtimer as apb-dualtimer Philippe Mathieu-Daudé
2020-06-16 10:16   ` Peter Maydell
2020-06-16  6:31 ` [PATCH 3/7] hw/arm/mps2: Add CMSDK APB watchdog as unimplemented device Philippe Mathieu-Daudé
2020-06-16 10:17   ` Peter Maydell
2020-06-16 10:35     ` Philippe Mathieu-Daudé
2020-06-16  6:31 ` [PATCH 4/7] hw/arm/mps2: Add CMSDK AHB GPIO peripherals as unimplemented devices Philippe Mathieu-Daudé
2020-06-16 10:20   ` Peter Maydell
2020-06-16  6:31 ` [PATCH 5/7] hw/arm/mps2: Add I2C busses on FPGA APB Philippe Mathieu-Daudé
2020-06-16 10:21   ` Peter Maydell
2020-06-17  3:28     ` Philippe Mathieu-Daudé
2020-06-16  6:31 ` [PATCH 6/7] hw/arm/mps2: Map the FPGA I/O block Philippe Mathieu-Daudé
2020-06-16 10:26   ` Peter Maydell
2020-06-16 10:36     ` Philippe Mathieu-Daudé
2020-06-16  6:31 ` [PATCH 7/7] hw/misc/mps2-fpgaio: Implement push-buttons Philippe Mathieu-Daudé
2020-06-16 10:27   ` Peter Maydell
2020-06-16 10:40     ` Philippe Mathieu-Daudé
2020-06-16 12:29       ` Peter Maydell [this message]
2020-06-16 12:33         ` 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=CAFEAcA_GuCQRuwAgbQfHRKh732Kfzwj-zxX48tjBBnWCBjKLnQ@mail.gmail.com \
    --to=peter.maydell@linaro.org \
    --cc=estebanbosse@gmail.com \
    --cc=f4bug@amsat.org \
    --cc=me@xcancerberox.com.ar \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.