Re: [RFC 01/32] Kconfig: introduce and depend on LEGACY_PCI

From
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Date
2021-12-28 12:01:48
Also in
alsa-devel, dri-devel, intel-wired-lan, linux-arch, linux-fbdev, linux-gpio, linux-hwmon, linux-i2c, linux-ide, linux-input, linux-media, linux-pci, linux-riscv, linux-scsi, linux-spi, linux-staging, linux-watchdog, linux-wireless, lkml, netdev
Reply to
Niklas Schnelle, 2021-12-28
On Tue, Dec 28, 2021 at 11:58:55AM +0100, Niklas Schnelle wrote:
We add both LEGACY_PCI and HAS_IOPORT to differentiate between two
cases. HAS_IOPORT is for PC-style devices that are not on a PCI card
while LEGACY_PCI is for PCI drivers that require port I/O. This
includes pre-PCIe devices as well as PCIe devices which require
features like I/O spaces. The "legacy" naming is comes from the PCIe
spec which in section 2.1.1.2 says "PCI Express supports I/O Space for
compatibility with legacy devices which require their use. Future
revisions of this specification may deprecate the use of I/O Space."
Ah, then mention the reason why this is called LEGACY_PCI is that it is
because that is what the PCI spec calls it.  It was not obvious here at
all that this is where the name came from.

thanks,

greg k-h
Thread (20 messages) 20 messages, 6 authors, last reply 2022-01-10
Keyboard shortcuts
hback out one level
jnext message in thread / next series-diff position
kprevious message in thread / previous series-diff position
ldrill in
Escclose help / fold thread tree
?toggle this help