From: Alistair Francis <alistair23@gmail.com>
To: Wilfred Mallawa <wilfred.mallawa@opensource.wdc.com>
Cc: Alistair.Francis@wdc.com, palmer@dabbelt.com,
bin.meng@windriver.com, qemu-riscv@nongnu.org,
qemu-devel@nongnu.org, Wilfred Mallawa <wilfred.mallawa@wdc.com>
Subject: Re: [PATCH] include/hw/riscv/opentitan: update opentitan IRQs
Date: Mon, 23 Jan 2023 12:53:11 +1000 [thread overview]
Message-ID: <CAKmqyKOnXPPcHMXe81KTxt9mLz0VjE+QxGybGmKZNzSFhP7KmQ@mail.gmail.com> (raw)
In-Reply-To: <20230123000540.58351-1-wilfred.mallawa@opensource.wdc.com>
On Mon, Jan 23, 2023 at 10:06 AM Wilfred Mallawa
<wilfred.mallawa@opensource.wdc.com> wrote:
>
> From: Wilfred Mallawa <wilfred.mallawa@wdc.com>
>
> Updates the opentitan IRQs to match the latest supported commit of
> Opentitan from TockOS.
>
> OPENTITAN_SUPPORTED_SHA := 565e4af39760a123c59a184aa2f5812a961fde47
>
> Signed-off-by: Wilfred Mallawa <wilfred.mallawa@wdc.com>
Reviewed-by: Alistair Francis <alistair.francis@wdc.com>
Alistair
> ---
> include/hw/riscv/opentitan.h | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/include/hw/riscv/opentitan.h b/include/hw/riscv/opentitan.h
> index 7659d1bc5b..235728b9cc 100644
> --- a/include/hw/riscv/opentitan.h
> +++ b/include/hw/riscv/opentitan.h
> @@ -108,11 +108,11 @@ enum {
> IBEX_UART0_RX_BREAK_ERR_IRQ = 6,
> IBEX_UART0_RX_TIMEOUT_IRQ = 7,
> IBEX_UART0_RX_PARITY_ERR_IRQ = 8,
> - IBEX_TIMER_TIMEREXPIRED0_0 = 127,
> - IBEX_SPI_HOST0_ERR_IRQ = 134,
> - IBEX_SPI_HOST0_SPI_EVENT_IRQ = 135,
> - IBEX_SPI_HOST1_ERR_IRQ = 136,
> - IBEX_SPI_HOST1_SPI_EVENT_IRQ = 137,
> + IBEX_TIMER_TIMEREXPIRED0_0 = 124,
> + IBEX_SPI_HOST0_ERR_IRQ = 131,
> + IBEX_SPI_HOST0_SPI_EVENT_IRQ = 132,
> + IBEX_SPI_HOST1_ERR_IRQ = 133,
> + IBEX_SPI_HOST1_SPI_EVENT_IRQ = 134,
> };
>
> #endif
> --
> 2.39.0
>
>
prev parent reply other threads:[~2023-01-23 2:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-23 0:05 [PATCH] include/hw/riscv/opentitan: update opentitan IRQs Wilfred Mallawa
2023-01-23 2:53 ` Alistair Francis [this message]
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=CAKmqyKOnXPPcHMXe81KTxt9mLz0VjE+QxGybGmKZNzSFhP7KmQ@mail.gmail.com \
--to=alistair23@gmail.com \
--cc=Alistair.Francis@wdc.com \
--cc=bin.meng@windriver.com \
--cc=palmer@dabbelt.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-riscv@nongnu.org \
--cc=wilfred.mallawa@opensource.wdc.com \
--cc=wilfred.mallawa@wdc.com \
/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).