From: "BillXiang" <xiangwencheng@lanxincomputing.com>
To: <sunilvl@oss.qualcomm.com>
Cc: <sunilvl@ventanamicro.com>, <rafael@kernel.org>,
<lenb@kernel.org>, <pjw@kernel.org>, <palmer@dabbelt.com>,
<aou@eecs.berkeley.edu>, <alex@ghiti.fr>,
<linux-acpi@vger.kernel.org>, <linux-riscv@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <iommu@lists.linux.dev>,
<tjeznach@rivosinc.com>, <luxu.kernel@bytedance.com>,
<guoren@linux.alibaba.com>, <jgg@nvidia.com>
Subject: Re: [PATCH] riscv: iommu: ask for ACS to be enabled
Date: Thu, 17 Sep 2026 10:04:34 +0800 [thread overview]
Message-ID: <9d469f95-73b4-4a0a-9c35-80a655a53225@lanxincomputing.com> (raw)
In-Reply-To: <CAB19ukHfFXmuPEaWdNPvFRkvMGpDQfVEpCHfqsHL20tpBytQRA@mail.gmail.com>
On 9/16/2026 8:18 PM, Sunil V L wrote:
> On Wed, Sep 16, 2026 at 5:15 PM BillXiang
> <xiangwencheng@lanxincomputing.com> wrote:
>>
>> Make sure ACS will be enabled during PCI probe
>>
>> Signed-off-by: BillXiang <xiangwencheng@lanxincomputing.com>
>> ---
>> drivers/acpi/riscv/rimt.c | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/drivers/acpi/riscv/rimt.c b/drivers/acpi/riscv/rimt.c
>> index e4538fa6c2c8..30d2d0211d5e 100644
>> --- a/drivers/acpi/riscv/rimt.c
>> +++ b/drivers/acpi/riscv/rimt.c
>> @@ -525,4 +525,5 @@ void __init riscv_acpi_rimt_init(void)
>>
>> return;
>> }
>> + pci_request_acs();
>> }
>>
> There is already a patch in the mailing list for this.
>
> https://lkml.org/lkml/2026/9/3/1930
>
> Thanks,
> Sunil
Thank you for pointing that out. Please just ignore my commit.
--
BillXiang
prev parent reply other threads:[~2026-09-17 2:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-16 11:25 BillXiang
2026-09-16 12:18 ` Sunil V L
2026-09-17 2:04 ` BillXiang [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=9d469f95-73b4-4a0a-9c35-80a655a53225@lanxincomputing.com \
--to=xiangwencheng@lanxincomputing.com \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=guoren@linux.alibaba.com \
--cc=iommu@lists.linux.dev \
--cc=jgg@nvidia.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=luxu.kernel@bytedance.com \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=rafael@kernel.org \
--cc=sunilvl@oss.qualcomm.com \
--cc=sunilvl@ventanamicro.com \
--cc=tjeznach@rivosinc.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
all inboxes | Powered by JetHome®