From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Jim Shu <jim.shu@sifive.com>,
Alistair.Francis@wdc.com, bin.meng@windriver.com,
palmer@dabbelt.com, frank.chang@sifive.com,
qemu-riscv@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [PATCH 2/2] hw/dma: sifive_pdma: permit 4/8-byte access size of PDMA registers
Date: Tue, 28 Dec 2021 11:35:31 +0100 [thread overview]
Message-ID: <df3d3a3a-500b-8dd2-045c-7074682af27e@redhat.com> (raw)
In-Reply-To: <20211228005236.415583-3-jim.shu@sifive.com>
On 12/28/21 01:52, Jim Shu wrote:
> It's obvious that PDMA support 64-bit access of 64-bit registers, and
> in previous commit, we confirm that PDMA support 32-bit access of both
> 32/64-bit registers. Thus, we configure 32/64-bit memory access of
> PDMA registers as valid in general.
>
> Signed-off-by: Jim Shu <jim.shu@sifive.com>
> Reviewed-by: Frank Chang <frank.chang@sifive.com>
> ---
> hw/dma/sifive_pdma.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/hw/dma/sifive_pdma.c b/hw/dma/sifive_pdma.c
> index b8b198ab4e..731fcdcf89 100644
> --- a/hw/dma/sifive_pdma.c
> +++ b/hw/dma/sifive_pdma.c
> @@ -441,6 +441,10 @@ static const MemoryRegionOps sifive_pdma_ops = {
> .impl = {
> .min_access_size = 4,
> .max_access_size = 8,
> + },
> + .valid = {
> + .min_access_size = 4,
> + .max_access_size = 8,
> }
> };
>
Eh now I see this patch. It is correct, so:
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
But I think the previous patch could be simpler.
next prev parent reply other threads:[~2021-12-28 10:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-28 0:52 [PATCH 0/2] Align SiFive PDMA behavior to real hardware Jim Shu
2021-12-28 0:52 ` [PATCH 1/2] hw/dma: sifive_pdma: support high 32-bit access of 64-bit register Jim Shu
2021-12-28 10:33 ` Philippe Mathieu-Daudé
2022-01-03 22:45 ` Alistair Francis
2022-01-04 2:55 ` Bin Meng
2022-01-04 5:53 ` Jim Shu
2021-12-28 0:52 ` [PATCH 2/2] hw/dma: sifive_pdma: permit 4/8-byte access size of PDMA registers Jim Shu
2021-12-28 10:35 ` Philippe Mathieu-Daudé [this message]
2022-01-03 22:46 ` Alistair Francis
2022-01-04 2:56 ` Bin Meng
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=df3d3a3a-500b-8dd2-045c-7074682af27e@redhat.com \
--to=philmd@redhat.com \
--cc=Alistair.Francis@wdc.com \
--cc=bin.meng@windriver.com \
--cc=frank.chang@sifive.com \
--cc=jim.shu@sifive.com \
--cc=palmer@dabbelt.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-riscv@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).