From: Peter Maydell <peter.maydell@linaro.org>
To: Maxim Uvarov <maxim.uvarov@linaro.org>
Cc: qemu-arm <qemu-arm@nongnu.org>, QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [PATCH 1/2] arm/virt: fix irq mapping for gpio_pwr
Date: Fri, 25 Jun 2021 12:58:14 +0100 [thread overview]
Message-ID: <CAFEAcA9Q9kc2-8h5xprg1FsKf3F7Uo7DaxMftecWgZFFoWYWXw@mail.gmail.com> (raw)
In-Reply-To: <20210625111842.3790-2-maxim.uvarov@linaro.org>
On Fri, 25 Jun 2021 at 12:18, Maxim Uvarov <maxim.uvarov@linaro.org> wrote:
>
> Fix irq mapping for virt machine reboot and shutdown
> interrupts triggered from ATF code.
>
> Signed-off-by: Maxim Uvarov <maxim.uvarov@linaro.org>
> ---
> hw/arm/virt.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/hw/arm/virt.c b/hw/arm/virt.c
> index 4b96f06014..d83f4ebdd3 100644
> --- a/hw/arm/virt.c
> +++ b/hw/arm/virt.c
> @@ -846,8 +846,8 @@ static void create_gpio_keys(char *fdt, DeviceState *pl061_dev,
> "gpios", phandle, 3, 0);
> }
>
> -#define SECURE_GPIO_POWEROFF 0
> -#define SECURE_GPIO_RESET 1
> +#define SECURE_GPIO_POWEROFF 1
> +#define SECURE_GPIO_RESET 2
I don't understand why this is needed. QEMU counts its GPIO
lines from 0 for the PL061, so wiring up lines 1 and 2
should be no different from using lines 0 and 1 (either way,
we tell the guest what lines to use in the device tree).
-- PMM
next prev parent reply other threads:[~2021-06-25 12:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-25 11:18 [PATCH 0/2] arm/virt: fix machine poweroff Maxim Uvarov
2021-06-25 11:18 ` [PATCH 1/2] arm/virt: fix irq mapping for gpio_pwr Maxim Uvarov
2021-06-25 11:58 ` Peter Maydell [this message]
2021-06-25 14:03 ` Maxim Uvarov
2021-06-25 11:18 ` [PATCH 2/2] gpio_pwr: use shutdown function for reboot Maxim Uvarov
2021-06-25 11:56 ` Peter Maydell
2021-06-29 15:29 ` 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=CAFEAcA9Q9kc2-8h5xprg1FsKf3F7Uo7DaxMftecWgZFFoWYWXw@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=maxim.uvarov@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).