Changes in Kconfig

795e272e - FDDI: defxx: Implement dynamic CSR I/O address space selection

Wed, 10 Mar 2021 12:03:19 +0000

FDDI: defxx: Implement dynamic CSR I/O address space selectionRecent versions of the PCI Express specification have deprecated supportfor I/O transactions and actually some PCIe host bridges, such as PowerSystems Host Bridge 4 (PHB4), do not implement them. Conversely a DEFEAadapter can have its MMIO decoding disabled with ECU (EISA ConfigurationUtility) and therefore not available for us with the resource allocationinfrastructure we implement.However either I/O address space will always be available for use withthe DEFEA (EISA) and DEFPA (PCI) adapters and both have double addressdecoding implemented in hardware for Control and Status Register access.The two kinds of adapters can be present both at once in a single mixedPCI/EISA system. For the DEFTA (TURBOchannel) variant there is no issueas there has been no port I/O address space defined for that bus.To make people's life easier and the driver more robust remove theDEFXX_MMIO configuration option so as to rather than making the choicefor the I/O address space to use at build time for all the adaptersinstalled in the system let the driver choose the most suitable addressspace dynamically on a case-by-case basis at run time. Make MMIO thedefault and resort to port I/O should the default fail for some reason.This way multiple adapters installed in one system can use different I/Oaddress spaces each, in particular in the presence of DEFEA adapters ina pure-EISA or a mixed EISA/PCI system (it is expected that DEFPA boardswill use MMIO in normal circumstances).The choice of the I/O address space to use continues being reported bythe driver on startup, e.g.:eisa 00:05: EISA: slot 5: DEC3002 detecteddefxx: v1.12 2021/03/10 Lawrence V. Stefani and others00:05: DEFEA at I/O addr = 0x5000, IRQ = 10, Hardware addr = 00-00-f8-c8-b3-b600:05: registered as fddi0and:defxx: v1.12 2021/03/10 Lawrence V. Stefani and others0031:02:04.0: DEFPA at MMIO addr = 0x620c080020000, IRQ = 57, Hardware addr = 00-60-6d-93-91-980031:02:04.0: registered as fddi0and:defxx: v1.12 2021/03/10 Lawrence V. Stefani and otherstc2: DEFTA at MMIO addr = 0x1f100000, IRQ = 21, Hardware addr = 08-00-2b-b0-8b-1etc2: registered as fddi0so there is no need to add further information.The change is supposed to cause a negligible performance hit as I/Oaccessors will now have code executed conditionally at run time.Signed-off-by: Maciej W. Rozycki Signed-off-by: David S. Miller List of files: /linux-6.15/drivers/net/fddi/Kconfig

193ced4a - FDDI: defxx: Make MMIO the configuration default except for EISA

Wed, 10 Mar 2021 12:03:14 +0000

FDDI: defxx: Make MMIO the configuration default except for EISARecent versions of the PCI Express specification have deprecated supportfor I/O transactions and actually some PCIe host bridges, such as PowerSystems Host Bridge 4 (PHB4), do not implement them.The default kernel configuration choice for the defxx driver is the useof I/O ports rather than MMIO for PCI and EISA systems. It may havemade sense as a conservative backwards compatible choice back when MMIOoperation support was added to the driver as a part of TURBOchannel bussupport. However nowadays this configuration choice makes the driverunusable with systems that do not implement I/O transactions for PCIe.Make DEFXX_MMIO the configuration default then, except where configuredfor EISA. This exception is because an EISA adapter can have its MMIOdecoding disabled with ECU (EISA Configuration Utility) and thereforenot available with the resource allocation infrastructure we implement,while port I/O is always readily available as it uses slot-specificaddressing, directly mapped to the slot an option card has been placedin and handled with our EISA bus support core. Conversely a kernel thatsupports modern systems which may not have I/O transactions implementedfor PCIe will usually not be expected to handle legacy EISA systems.The change of the default will make it easier for people, including butnot limited to distribution packagers, to make a working choice for thedriver.Update the option description accordingly and while at it replace thepotentially ambiguous PIO acronym with IOP for "port I/O" vs "I/O ports"according to our nomenclature used elsewhere.Signed-off-by: Maciej W. Rozycki Fixes: e89a2cfb7d7b ("[TC] defxx: TURBOchannel support")Cc: stable@vger.kernel.org # v2.6.21+Signed-off-by: David S. Miller List of files: /linux-6.15/drivers/net/fddi/Kconfig

55f35cf7 - docs: networking: move FDDI drivers to the hw driver section

Fri, 26 Jun 2020 17:27:31 +0000

docs: networking: move FDDI drivers to the hw driver sectionMove docs for defza and skfp under device_drivers/fddi.Signed-off-by: Jakub Kicinski Signed-off-by: David S. Miller List of files: /linux-6.15/drivers/net/fddi/Kconfig

a7f7f624 - treewide: replace '---help---' in Kconfig files with 'help'

Sat, 13 Jun 2020 16:50:22 +0000

treewide: replace '---help---' in Kconfig files with 'help'Since commit 84af7a6194e4 ("checkpatch: kconfig: prefer 'help' over'---help---'"), the number of '---help---' has been graduallydecreasing, but there are still more than 2400 instances.This commit finishes the conversion. While I touched the lines,I also fixed the indentation.There are a variety of indentation styles found. a) 4 spaces + '---help---' b) 7 spaces + '---help---' c) 8 spaces + '---help---' d) 1 space + 1 tab + '---help---' e) 1 tab + '---help---' (correct indentation) f) 1 tab + 1 space + '---help---' g) 1 tab + 2 spaces + '---help---'In order to convert all of them to 1 tab + 'help', I ran thefollowing commend: $ find . -name 'Kconfig*' | xargs sed -i 's/^[[:space:]]*---help---/\thelp/'Signed-off-by: Masahiro Yamada List of files: /linux-6.15/drivers/net/fddi/Kconfig

fe3dfe41 - docs: networking: convert skfp.txt to ReST

Thu, 30 Apr 2020 16:04:25 +0000

docs: networking: convert skfp.txt to ReST- add SPDX header;- use copyright symbol;- add a document title;- adjust titles and chapters, adding proper markups;- comment out text-only TOC from html/pdf output;- adjust identation, whitespaces and blank lines where needed;- add to networking/index.rst.Signed-off-by: Mauro Carvalho Chehab Signed-off-by: David S. Miller List of files: /linux-6.15/drivers/net/fddi/Kconfig

ec8f24b7 - treewide: Add SPDX license identifier - Makefile/Kconfig

Sun, 19 May 2019 12:07:45 +0000

treewide: Add SPDX license identifier - Makefile/KconfigAdd SPDX license identifiers to all Make/Kconfig files which: - Have no license information of any formThese files fall under the project license, GPL v2 only. The resulting SPDXlicense identifier is: GPL-2.0-onlySigned-off-by: Thomas Gleixner Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/net/fddi/Kconfig

61414f5e - FDDI: defza: Add support for DEC FDDIcontroller 700 TURBOchannel adapter

Tue, 09 Oct 2018 22:57:43 +0000

FDDI: defza: Add support for DEC FDDIcontroller 700 TURBOchannel adapterAdd support for the DEC FDDIcontroller 700 (DEFZA), Digital EquipmentCorporation's first-generation FDDI network interface adapter, made forTURBOchannel and based on a discrete version of what eventually becameMotorola's widely used CAMEL chipset.The CAMEL chipset is present for example in the DEC FDDIcontrollerTURBOchannel, EISA and PCI adapters (DEFTA/DEFEA/DEFPA) that we supportwith the `defxx' driver, however the host bus interface logic and thefirmware API are different in the DEFZA and hence a separate driver isrequired.There isn't much to say about the driver except that it works, but thereis one peculiarity to mention. The adapter implements two Tx/Rx queuepairs.Of these one pair is the usual network Tx/Rx queue pair, in this caseused by the adapter to exchange frames with the ring, via the RMC (RingMemory Controller) chip. The Tx queue is handled directly by the RMCchip and resides in onboard packet memory. The Rx queue is maintainedvia DMA in host memory by adapter's firmware copying received datastored by the RMC in onboard packet memory.The other pair is used to communicate SMT frames with adapter'sfirmware. Any SMT frame received from the RMC via the Rx queue must bequeued back by the driver to the SMT Rx queue for the firmware toprocess. Similarly the firmware uses the SMT Tx queue to supply thedriver with SMT frames that must be queued back to the Tx queue for theRMC to send to the ring.This solution was chosen because the designers ran out of PCB space andcould not squeeze in more logic onto the board that would be required tohandle this SMT frame traffic without the need to involve the driver, aswith the later DEFTA/DEFEA/DEFPA adapters.Finally the driver does some Frame Control byte decoding, so to avoidmagic numbers some macros are added to .Signed-off-by: Maciej W. Rozycki Signed-off-by: David S. Miller List of files: /linux-6.15/drivers/net/fddi/Kconfig

33f810b2 - fddi: Move the FDDI drivers

Sun, 31 Jul 2011 07:06:29 +0000

fddi: Move the FDDI driversMove the FDDI drivers into drivers/net/fddi/ and make thenecessary Kconfig and Makefile changes.CC: "Maciej W. Rozycki" CC: Christoph Goos CC: Signed-off-by: Jeff Kirsher List of files: /linux-6.15/drivers/net/fddi/Kconfig