From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Andrew Jones <ajones@ventanamicro.com>,
qemu-devel@nongnu.org, qemu-riscv@nongnu.org,
Conor Dooley <conor@kernel.org>
Cc: palmer@dabbelt.com, alistair.francis@wdc.com, bmeng.cn@gmail.com,
dbarboza@ventanamicro.com, Anup Patel <apatel@ventanamicro.com>
Subject: Re: [PATCH for-9.1 1/2] Revert "hw/riscv/virt.c: imsics DT: add '#msi-cells'"
Date: Fri, 16 Aug 2024 18:45:12 +0200 [thread overview]
Message-ID: <e190d050-7f63-4f7f-bce5-09b1cecac9aa@linaro.org> (raw)
In-Reply-To: <40c7abce-8d1d-4591-ab09-bbfebf1e1657@linaro.org>
On 16/8/24 18:27, Philippe Mathieu-Daudé wrote:
> On 16/8/24 18:07, Andrew Jones wrote:
>> This reverts commit f42cdf2ea5b3a1dc369792d7acbf9cd3e5c90815.
Ahah sorry I'm not seeing well after a long day in front of the
monitor =)
>> Linux does not properly handle '#msi-cells=<0>' when searching for
>> MSI controllers for PCI devices which results in the devices being
>> unable to use MSIs. A patch for Linux has been sent[1] but until it,
>> or something like it, is merged and in distro kernels we should stop
>> adding the property. It's harmless to stop adding it since the
>> absence of the property and a value of zero for the property mean
>> the same thing according to the DT binding definition.
>>
>
> This reverts commit f42cdf2ea5b3a1dc369792d7acbf9cd3e5c90815.
>
>> Link:
>> https://lore.kernel.org/all/20240816124957.130017-2-ajones@ventanamicro.com/ # 1
>> Signed-off-by: Andrew Jones <ajones@ventanamicro.com>
>> ---
>> hw/riscv/virt.c | 1 -
>> 1 file changed, 1 deletion(-)
>>
>> diff --git a/hw/riscv/virt.c b/hw/riscv/virt.c
>> index 9981e0f6c9b9..cef41c150aaf 100644
>> --- a/hw/riscv/virt.c
>> +++ b/hw/riscv/virt.c
>> @@ -552,7 +552,6 @@ static void create_fdt_one_imsic(RISCVVirtState
>> *s, hwaddr base_addr,
>> FDT_IMSIC_INT_CELLS);
>> qemu_fdt_setprop(ms->fdt, imsic_name, "interrupt-controller",
>> NULL, 0);
>> qemu_fdt_setprop(ms->fdt, imsic_name, "msi-controller", NULL, 0);
>> - qemu_fdt_setprop_cell(ms->fdt, imsic_name, "#msi-cells", 0);
>> qemu_fdt_setprop(ms->fdt, imsic_name, "interrupts-extended",
>> imsic_cells, ms->smp.cpus * sizeof(uint32_t) * 2);
>> qemu_fdt_setprop(ms->fdt, imsic_name, "reg", imsic_regs,
>
next prev parent reply other threads:[~2024-08-16 16:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-16 16:07 [PATCH 0/2] hw/riscv/virt: Fix PCI devices with AIA Andrew Jones
2024-08-16 16:07 ` [PATCH for-9.1 1/2] Revert "hw/riscv/virt.c: imsics DT: add '#msi-cells'" Andrew Jones
2024-08-16 16:27 ` Philippe Mathieu-Daudé
2024-08-16 16:45 ` Philippe Mathieu-Daudé [this message]
2024-08-16 16:55 ` Daniel Henrique Barboza
2024-08-19 1:19 ` Alistair Francis
2024-08-16 16:07 ` [PATCH 2/2] hw/riscv/virt: Introduce strict-dt Andrew Jones
2024-08-19 1:19 ` Alistair Francis
2024-08-19 7:50 ` Andrew Jones
2024-08-19 8:42 ` Richard Henderson
2024-09-09 2:41 ` Alistair Francis
2024-09-09 8:44 ` Andrew Jones
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=e190d050-7f63-4f7f-bce5-09b1cecac9aa@linaro.org \
--to=philmd@linaro.org \
--cc=ajones@ventanamicro.com \
--cc=alistair.francis@wdc.com \
--cc=apatel@ventanamicro.com \
--cc=bmeng.cn@gmail.com \
--cc=conor@kernel.org \
--cc=dbarboza@ventanamicro.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).