From: Keith Busch <kbusch@kernel.org>
To: Jon Derrick <jonathan.derrick@intel.com>
Cc: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
linux-pci@vger.kernel.org, Bjorn Helgaas <helgaas@kernel.org>,
Keith Busch <kbusch@kernel.com>
Subject: Re: [PATCH 1/2] PCI: vmd: Add bus 224-255 restriction decode
Date: Tue, 12 Nov 2019 02:04:22 +0900 [thread overview]
Message-ID: <20191111170422.GB10851@redsun51.ssa.fujisawa.hgst.com> (raw)
In-Reply-To: <20191111165302.29636-2-jonathan.derrick@intel.com>
On Mon, Nov 11, 2019 at 09:53:01AM -0700, Jon Derrick wrote:
> VMD bus restrictions are required when IO fabric is multiplexed such
> that VMD cannot use the entire bus range. This patch adds another bus
> restriction decode bit that can be set by firmware to restrict the VMD
> bus range from 224-255.
The code suggests that such a device is restricted *to* that range,
not from it.
> + switch (BUS_RESTRICT_CFG(reg16)) {
> + case(1):
> + vmd->busn_start = 128;
> + break;
> + case(2):
> + vmd->busn_start = 224;
> + break;
> + case(3):
> + pci_err(vmd->dev, "Unknown Bus Offset Setting\n");
> + return -ENODEV;
> + default:
> + break;
> + }
Just a nit for consistent sytle, every other switch case looks like:
case 1:
...
case 2:
...
case 3:
...
next prev parent reply other threads:[~2019-11-11 17:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-11 16:53 [PATCH 0/2] VMD support for 8086:9A0B Jon Derrick
2019-11-11 16:53 ` [PATCH 1/2] PCI: vmd: Add bus 224-255 restriction decode Jon Derrick
2019-11-11 17:04 ` Keith Busch [this message]
2019-11-11 16:53 ` [PATCH 2/2] PCI: vmd: Add device id for VMD device 8086:9A0B Jon Derrick
2019-11-11 16:55 ` [PATCH 0/2] VMD support for 8086:9A0B Derrick, Jonathan
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=20191111170422.GB10851@redsun51.ssa.fujisawa.hgst.com \
--to=kbusch@kernel.org \
--cc=helgaas@kernel.org \
--cc=jonathan.derrick@intel.com \
--cc=kbusch@kernel.com \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.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).