Linux PCI subsystem development
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Ali Alaei" <ali.alaei.tabatabaei@gmail.com>
Cc: linux-pci@vger.kernel.org
Subject: Re: [PATCH v3] PCI: vmd: Handle BUS_RESTRICT_CFG value 3 for Arrow Lake-HX
Date: Sun, 28 Jun 2026 14:46:52 +0000	[thread overview]
Message-ID: <20260628144658.A6AE81F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260628143450.92492-1-ali.alaei.tabatabaei@gmail.com>

> On Intel Arrow Lake-HX systems (e.g. Core Ultra 9 275HX on Acer Predator
> PH16-73), the VMD controller reports BUS_RESTRICT_CFG = 3 in the VMCONFIG
> register. The existing switch statement only handled values 0, 1, and 2,
> causing vmd_get_bus_number_start() to return -ENODEV and aborting the
> entire VMD probe. This leaves NVMe drives behind the VMD controller
> invisible to the kernel.
> 
> Hardware registers (VMCAP/VMCONFIG at offsets 0x40/0x44):
>   VMD 0000:00:0e.0 (8086:ad0b): VMCAP=0x000f, VMCONFIG=0x03b8
>   BUS_RESTRICT_CFG(0x03b8) = (0x03b8 >> 8) & 0x3 = 3
> 
> Add cfg=3 as a fallthrough to cfg=2, setting busn_start=224, which is
> the correct bus number base for this hardware.
> 
> Also add a PCI_POSSIBLE_ERROR() guard after reading VMCONFIG: a failed
> config space read returns 0xFFFF, and BUS_RESTRICT_CFG(0xFFFF) = 3,
> so without this guard a removed or errored device would falsely match
> the new case 3 instead of being caught as an error.
> 
> Signed-off-by: Ali Alaei <ali.alaei.tabatabaei@gmail.com>

Sashiko has reviewed this patch and found no issues. It looks great!

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260628143450.92492-1-ali.alaei.tabatabaei@gmail.com?part=1


  reply	other threads:[~2026-06-28 14:46 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-04 18:59 [PATCH] PCI: vmd: Handle BUS_RESTRICT_CFG value 3 for Arrow Lake-HX Ali Alaei
2026-06-04 19:12 ` sashiko-bot
2026-06-04 21:40 ` [PATCH v2] " Ali Alaei
2026-06-22 14:46   ` Manivannan Sadhasivam
2026-06-28 14:34   ` [PATCH v3] " Ali Alaei
2026-06-28 14:46     ` sashiko-bot [this message]
2026-07-13 17:16     ` Ali Alaei
2026-07-15  5:56     ` Manivannan Sadhasivam
2026-07-20 22:47     ` Bjorn Helgaas
2026-07-21 12:47       ` Lin Mohan
2026-07-21 12:50       ` Lin Mohan
  -- strict thread matches above, loose matches on Subject: below --
2026-07-21 12:47 Lin Mohan
2026-07-21 16:42 ` Bjorn Helgaas
2026-08-05  3:27   ` Krzysztof Wilczyński

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=20260628144658.A6AE81F000E9@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=ali.alaei.tabatabaei@gmail.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    /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