From: ido berenbaum <ido.ber3@gmail.com>
To: qemu-devel@nongnu.org
Subject: Gpio in vexpress
Date: Mon, 15 May 2023 18:17:14 +0300 [thread overview]
Message-ID: <CANamGFG1Lq+QSMshgYChj663K=Sj19YEh8WP=HWYM6HBnpRpWw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 413 bytes --]
Hi, I was trying to understand the architecture of the vexpress virtual
machine in regards to adding new gpios that are going to be external.
First, is it right to act as if I am developing on a physical board and add
the gpios to the VexpressMachineState struct?
Secondly, which gpio type fits here? I see that for fsl_imx7 it is the
imx_gpio, but what is for vexpress? Should I create one?
Or, can I use pl061?
[-- Attachment #2: Type: text/html, Size: 499 bytes --]
next reply other threads:[~2023-05-16 6:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-15 15:17 ido berenbaum [this message]
2023-05-16 9:17 ` Gpio in vexpress Peter Maydell
2023-05-18 14:35 ` ido berenbaum
2023-05-18 15:01 ` Peter Maydell
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='CANamGFG1Lq+QSMshgYChj663K=Sj19YEh8WP=HWYM6HBnpRpWw@mail.gmail.com' \
--to=ido.ber3@gmail.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).