[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH 7/7] hw/misc/mps2-fpgaio: Implement push-buttons
From: |
Philippe Mathieu-Daudé |
Subject: |
Re: [PATCH 7/7] hw/misc/mps2-fpgaio: Implement push-buttons |
Date: |
Tue, 16 Jun 2020 14:33:39 +0200 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.5.0 |
On 6/16/20 2:29 PM, Peter Maydell wrote:
> 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.
On my side feedback are helpful, but I understand.
I'll see if there are still any motivated soul left,
else wait for next GSoC.
>
> thanks
> -- PMM
>
- Re: [PATCH 5/7] hw/arm/mps2: Add I2C busses on FPGA APB, (continued)
[PATCH 6/7] hw/arm/mps2: Map the FPGA I/O block, Philippe Mathieu-Daudé, 2020/06/16