[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Teensy 4.1 Implementation
From: |
Peter Maydell |
Subject: |
Re: Teensy 4.1 Implementation |
Date: |
Tue, 16 Aug 2022 11:05:40 +0100 |
On Tue, 16 Aug 2022 at 10:59, Alex Bennée <alex.bennee@linaro.org> wrote:
> Shiny Saana <shinysaana@gmail.com> writes:
> > I personally don't need any of the GPIO interfaces, but if needed
> > by someone else, that could be a good second step to
> > work on once that part of the board is implemented.
>
> Handling GPIOs in QEMU is fine (we have things like the qdev_init_gpio_*
> functions to handle them). The problem is usually what to do with the
> actual general purpose pins which aren't wired to something we emulate
> in the board. Some boards expose their values via QMP properties but I
> suspect whats really needed is a generic mechanism for exposing GPIO to
> external scripts rather than have every board define it's own thing.
Yes. However one key thing for trying to get a new board model
in is not to get tangled up in trying to improve/extend
the core QEMU facilities for something. That's much harder
than "my board model supports GPIO output lines to the same
extent as the other existing board models" :-)
thanks
-- PMM
- Teensy 4.1 Implementation, Shiny Saana, 2022/08/13
- Re: Teensy 4.1 Implementation, Peter Maydell, 2022/08/15
- Re: Teensy 4.1 Implementation, Shiny Saana, 2022/08/15
- Re: Teensy 4.1 Implementation, Alex Bennée, 2022/08/16
- Re: Teensy 4.1 Implementation,
Peter Maydell <=
- Re: Teensy 4.1 Implementation, Shiny Saana, 2022/08/20
- Re: Teensy 4.1 Implementation, Peter Maydell, 2022/08/23
- Re: Teensy 4.1 Implementation, Shiny Saana, 2022/08/23
- Re: Teensy 4.1 Implementation, Peter Maydell, 2022/08/23
- Re: Teensy 4.1 Implementation, Shiny Saana, 2022/08/23