Changes in Kconfig

7a14f78d - firewire: ohci: add static inline functions to deserialize for Self-ID DMA operation

Tue, 02 Jul 2024 22:20:32 +0000

firewire: ohci: add static inline functions to deserialize for Self-ID DMA operationThe SelfI-ID is one type of DMAs defined in 1394 OHCI specification. It isoperated by two registers, one interrupt, and has one format of buffer.This commit adds some static inline functions to deserialize the data inthe buffer and registers. Some KUnit tests are also added to check theirreliability.Link: https://lore.kernel.org/r/20240702222034.1378764-4-o-takashi@sakamocchi.jpSigned-off-by: Takashi Sakamoto List of files: /linux-6.15/drivers/firewire/Kconfig

7bd10e0e - firewire: core: add enumerator of self ID sequences and its KUnit test

Wed, 05 Jun 2024 23:51:45 +0000

firewire: core: add enumerator of self ID sequences and its KUnit testWhen the state of bus reset finishes, 1394 OHCI driver constructs self IDsequences, then it calls fw_core_handle_bus_reset() in core function. Thecore function enumerates the self ID sequences to build bus topology.This commit adds a structure and some helper functions for the enumeration,and adds a KUnit test suite to ensure its expected behaviour.Link: https://lore.kernel.org/r/20240605235155.116468-2-o-takashi@sakamocchi.jpSigned-off-by: Takashi Sakamoto List of files: /linux-6.15/drivers/firewire/Kconfig

e789523f - firewire: fix website URL in Kconfig

Thu, 13 Jun 2024 09:03:43 +0000

firewire: fix website URL in KconfigThe wiki in kernel.org is no longer updated. This commit replaces thewebsite URL with the latest one.Link: https://lore.kernel.org/r/20240613090343.416198-1-o-takashi@sakamocchi.jpSigned-off-by: Takashi Sakamoto List of files: /linux-6.15/drivers/firewire/Kconfig

75527d8d - firewire: core: add common inline functions to serialize/deserialize asynchronous packet header

Sun, 28 Apr 2024 07:13:39 +0000

firewire: core: add common inline functions to serialize/deserialize asynchronous packet headerIn both core and 1394 OHCI driver, some hard-coded values and macros areused to serialize/deserialize the header of asynchronous packets. It isinconvenient to reuse them.This commit adds some helper inline functions with their tests for thepurpose.Link: https://lore.kernel.org/r/20240428071347.409202-2-o-takashi@sakamocchi.jpSigned-off-by: Takashi Sakamoto List of files: /linux-6.15/drivers/firewire/Kconfig

1770d39d - firewire: test: add KUnit test for device attributes

Sun, 24 Dec 2023 22:23:00 +0000

firewire: test: add KUnit test for device attributesThe traverse over CSR space results in attributes of node and unitdevices. Any test of the traverse is useful.This commit adds a skeleton of KUnit test for the purpose.Link: https://lore.kernel.org/r/20231221134849.603857-4-o-takashi@sakamocchi.jpSigned-off-by: Takashi Sakamoto List of files: /linux-6.15/drivers/firewire/Kconfig

dc7c5163 - firewire: add KUnit test to check layout of UAPI structures

Mon, 29 May 2023 23:12:39 +0000

firewire: add KUnit test to check layout of UAPI structuresIn future commits, some new structure will be added to express new typeof event. They are exposed to user space as the part of UAPI. It is likelyto get trouble in ioctl compatibility layer for 32 bit binaries in 64 bithost machine since the layout of structure could differ depending onSystem V ABI for these architectures. Actually the subsystem already gotsuch trouble at v2.6.27. It is preferable to decide the layout ofstructure carefully so that the layer is free from such trouble.This commit utilizes KUnit framework to check the layout of structure forthe purpose. A test is added for the existent issue.Cc: kunit-dev@googlegroups.comLink: https://lore.kernel.org/r/20230529113406.986289-2-o-takashi@sakamocchi.jpSigned-off-by: Takashi Sakamoto List of files: /linux-6.15/drivers/firewire/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/firewire/Kconfig

c820518f - firewire: Remove depends on HAS_DMA in case of platform dependency

Fri, 22 Jun 2018 11:04:19 +0000

firewire: Remove depends on HAS_DMA in case of platform dependencyRemove dependencies on HAS_DMA where a Kconfig symbol depends on anothersymbol that implies HAS_DMA, and, optionally, on "|| COMPILE_TEST".In most cases this other symbol is an architecture or platform specificsymbol, or PCI.Generic symbols and drivers without platform dependencies keep theirdependencies on HAS_DMA, to prevent compiling subsystems or drivers thatcannot work anyway.This simplifies the dependencies, and allows to improve compile-testing.Signed-off-by: Geert Uytterhoeven Reviewed-by: Mark Brown Acked-by: Robin Murphy Signed-off-by: Stefan Richter List of files: /linux-6.15/drivers/firewire/Kconfig

655fc39b - firewire: IEEE 1394 (FireWire) support should depend on HAS_DMA

Wed, 09 Jul 2014 19:04:00 +0000

firewire: IEEE 1394 (FireWire) support should depend on HAS_DMACommit b3d681a4fc108f9653bbb44e4f4e72db2b8a5734 ("firewire: UseCOMPILE_TEST for build testing") added COMPILE_TEST as an alternativedependency for the purpose of build testing the firewire core.However, this bypasses all other implicit dependencies assumed by PCI,like HAS_DMA.If NO_DMA=y: drivers/built-in.o: In function `fw_iso_buffer_destroy': (.text+0x36a096): undefined reference to `dma_unmap_page' drivers/built-in.o: In function `fw_iso_buffer_map_dma': (.text+0x36a164): undefined reference to `dma_map_page' drivers/built-in.o: In function `fw_iso_buffer_map_dma': (.text+0x36a172): undefined reference to `dma_mapping_error' drivers/built-in.o: In function `sbp2_send_management_orb': sbp2.c:(.text+0x36c6b4): undefined reference to `dma_map_single' sbp2.c:(.text+0x36c6c8): undefined reference to `dma_mapping_error' sbp2.c:(.text+0x36c772): undefined reference to `dma_map_single' sbp2.c:(.text+0x36c786): undefined reference to `dma_mapping_error' sbp2.c:(.text+0x36c854): undefined reference to `dma_unmap_single' sbp2.c:(.text+0x36c872): undefined reference to `dma_unmap_single' drivers/built-in.o: In function `sbp2_map_scatterlist': sbp2.c:(.text+0x36ccbc): undefined reference to `scsi_dma_map' sbp2.c:(.text+0x36cd36): undefined reference to `dma_map_single' sbp2.c:(.text+0x36cd4e): undefined reference to `dma_mapping_error' sbp2.c:(.text+0x36cd84): undefined reference to `scsi_dma_unmap' drivers/built-in.o: In function `sbp2_unmap_scatterlist': sbp2.c:(.text+0x36cda6): undefined reference to `scsi_dma_unmap' sbp2.c:(.text+0x36cdc6): undefined reference to `dma_unmap_single' drivers/built-in.o: In function `complete_command_orb': sbp2.c:(.text+0x36d6ac): undefined reference to `dma_unmap_single' drivers/built-in.o: In function `sbp2_scsi_queuecommand': sbp2.c:(.text+0x36d8e0): undefined reference to `dma_map_single' sbp2.c:(.text+0x36d8f6): undefined reference to `dma_mapping_error'Add an explicit dependency on HAS_DMA to fix this.Signed-off-by: Geert Uytterhoeven Reviewed-by: Jean Delvare Signed-off-by: Stefan Richter List of files: /linux-6.15/drivers/firewire/Kconfig

b3d681a4 - firewire: Use COMPILE_TEST for build testing

Thu, 15 May 2014 13:29:23 +0000

firewire: Use COMPILE_TEST for build testingStop using BROKEN as an alternative dependency for the purpose ofbuild testing the firewire core. The newly introduced COMPILE_TEST isbetter suited for that purpose.Signed-off-by: Jean Delvare Signed-off-by: Stefan Richter List of files: /linux-6.15/drivers/firewire/Kconfig

cb6bf355 - firewire net, ipv6: IPv6 over Firewire (RFC3146) support.

Mon, 25 Mar 2013 08:26:24 +0000

firewire net, ipv6: IPv6 over Firewire (RFC3146) support.Signed-off-by: YOSHIFUJI Hideaki Signed-off-by: David S. Miller List of files: /linux-6.15/drivers/firewire/Kconfig

cfda62ba - firewire: ohci: move runtime debug facility out of #ifdef

Sun, 04 Mar 2012 20:34:21 +0000

firewire: ohci: move runtime debug facility out of #ifdefCONFIG_FIREWIRE_OHCI_DEBUG could have been exposed to kernel tweakersif CONFIG_EXPERT was set. But in hindsight, this stuff is far toouseful to omit it. So get rid of two #else branches that are onlygoing to bitrot otherwise.Signed-off-by: Stefan Richter List of files: /linux-6.15/drivers/firewire/Kconfig

8fd2af11 - firewire: nosy: should work on Power Mac G4 PCI too

Sun, 23 Jan 2011 11:26:51 +0000

firewire: nosy: should work on Power Mac G4 PCI tooThe first board generation of Power Mac G4 ("Yikes!", those with PCIgraphics) still had a PCILynx controller like their G3 predecessors,but not the later AGP models. (Jonathan Woithe recalls to have heardof it, and some web sources reinforce it.)Signed-off-by: Stefan Richter List of files: /linux-6.15/drivers/firewire/Kconfig

32471997 - firewire: net: is not experimental anymore

Wed, 19 Jan 2011 23:07:46 +0000

firewire: net: is not experimental anymorethanks to Clemens' and Maxim's fixes to firewire-ohci and -net in thelast two kernel releases.Signed-off-by: Stefan Richter List of files: /linux-6.15/drivers/firewire/Kconfig

7a39d8b8 - firewire: ohci: Asynchronous Reception rewrite

Fri, 26 Nov 2010 07:57:31 +0000

firewire: ohci: Asynchronous Reception rewriteMove the AR DMA descriptors out of the buffer pages, and map the bufferpages linearly into the kernel's address space. This allows the driverto ignore any page boundaries in the DMA data and thus to avoid anycopying around of packet payloads.This fixes the bug where S800 packets that are so big (> 4080 bytes)that they can be split over three pages were not handled correctly.Due to the changed algorithm, we can now use arbitrarily many bufferpages, which improves performance because the controller can more easilyunload its DMA FIFO.Furthermore, using streaming DMA mappings should improve perfomance onarchitectures where coherent DMA mappings are not cacheable. Even onother architectures, the caching behaviour should be improved slightlybecause the CPU no longer writes to the buffer pages.v2: Detect the last filled buffer page by searching the descriptor's residual count value fields in order (like in the old code), instead of going backwards through the transfer status fields; it looks as if some controllers do not set the latter correctly.v3: Fix an old resume bug that would now make the handler run into a BUG_ON, and replace that check with more useful error handling. Increase the buffer size for better performance with non-TI chips.Signed-off-by: Clemens Ladisch Maxim Levitsky writes: Works almost perfectly. I can still see RCODE_BUSY errors sometimes, not very often though. 64K here eliminates these errors completely. This is most likely due to nouveau drivers and lowest perf level I use to lower card temperature. That increases latencies too much I think. Besides that the IO is just perfect.Tested-by: Maxim Levitsky Signed-off-by: Stefan Richter List of files: /linux-6.15/drivers/firewire/Kconfig

66fa12c5 - ieee1394: remove the old IEEE 1394 driver stack

Sat, 09 Oct 2010 22:12:20 +0000

ieee1394: remove the old IEEE 1394 driver stackThe drivers - ohci1394 (controller driver) - ieee1394 (core) - dv1394, raw1394, video1394 (userspace ABI) - eth1394, sbp2 (protocol drivers)are replaced by - firewire-ohci (controller driver) - firewire-core (core and userspace ABI) - firewire-net, firewire-sbp2 (protocol drivers)which are more featureful, better performing, and more secure than the olderdrivers; all with a smaller and more modern code base.The driver firedtv in drivers/media/dvb/firewire/ contains backends to bothieee1394 and firewire-core. Its ieee1394 backend code can be removed in anindependent commit; firedtv as-is builds and works fine without ieee1394.The driver pcilynx (an incomplete controller driver) is deleted withoutreplacement since PCILynx cards are extremely rare. Owners of these cardsuse them with the stand-alone bus sniffer driver nosy instead.The drivers nosy and init_ohci1394_dma which do not interact with either ofthe two IEEE 1394 stacks are not affected by the ieee1394 subsystem removal.There are still some issues with the newer firewire subsystem compared tothe older one: - The rare and quirky controllers ALi M52xx, Apple UniNorth v1, NVIDIA NForce2 are even less well supported by firewire-ohci than by ohci1394. I am looking into the M52xx issue. - The experimental firewire-net is reportedly less stable than its experimental cousin eth1394. - Audio playback of a certain group of audio devices (ones based on DICE chipset with EAP; supported by prerelease FFADO code) does not work yet. This issue is still under investigation. - There were some ieee1394 based out-of-the-mainline drivers. Of them, only lisight, an audio driver for iSight webcams, seems still useful. Work is underway to reimplement it on top of firewire-core.All these remainig issues are minor; they should not stand in the way ofoverall better user experience of IEEE 1394 on Linux, together with areduction in support efforts and maintenance burden. The coexistence of twoIEEE 1394 kernel driver stacks in the mainline since 2.6.22 shall end now,as announced earlier this year.Signed-off-by: Stefan Richter List of files: /linux-6.15/drivers/firewire/Kconfig

9f6d3c4b - tools/firewire: add userspace front-end of nosy

Thu, 22 Jul 2010 09:58:05 +0000

tools/firewire: add userspace front-end of nosyThis adds nosy-dump, the userspace part of nosy, the IEEE 1394 trafficsniffer for Texas Instruments PCILynx/ PCILynx2 based cards. Author isKristian Høgsberg.The files added here are taken fromgit://anongit.freedesktop.org/~krh/nosy commit ee29be97 (2009-11-10)with the following changes by Stefan Richter: - Parts pertaining to the kernel module removed from Makefile. - dist target removed from the Makefile. - Mentioned nosy-dump in the Kconfig help to nosy's kernel component. - Add copyright notice to nosy-dump.c. This is a duplicate of the respective notice in the kernel component nosy.c except for a time span of 2002 - 2006, according to Kristian's git log."git shortlog decode-fcp.c list.h nosy-dump.[ch]" from nosy's gitrepository:Jonathan Woithe (1): Save logs on Ctrl-CKristian Høgsberg (11): Pull over nosy from mercurial repo. Remove some fields from default view, add logging feature. Use infinite time out for poll(), mark more detail fields. Fix byte ordering macro. Add decoding of iso data and lock packets. Add flag to indicate data length field. Add cycle start packet decoding, add --iso and --cycle-start flags. Distinguish between phy-packets and 0-length iso data. Fix transaction and stats view. Add simple AV/C decoder. Don't break down on big payloads.Signed-off-by: Stefan Richter Acked-by: Kristian Høgsberg List of files: /linux-6.15/drivers/firewire/Kconfig

28646821 - firewire: new driver: nosy - IEEE 1394 traffic sniffer

Tue, 27 Jul 2010 08:26:33 +0000

firewire: new driver: nosy - IEEE 1394 traffic snifferThis adds the traffic sniffer driver for Texas Instruments PCILynx/PCILynx2 based cards. The use cases for nosy are analysis ofnonstandard protocols and as an aid in development of drivers,applications, or firmwares.Author of the driver is Kristian Høgsberg. Known contributers areJody McIntyre and Jonathan Woithe.Nosy programs PCILynx chips to operate in promiscuous mode, which is afeature that is not found in OHCI-1394 controllers. Hence, only specialhardware as mentioned in the Kconfig help text is suitable for nosy.This is only the kernelspace part of nosy. There is a userspaceinterface to it, called nosy-dump, proposed to be added into the tools/subdirectory of the kernel sources in a subsequent change. Kernelspaceand userspave component of nosy communicate via a 'misc' characterdevice file called /dev/nosy with a simple ioctl() and read() basedprotocol, as described by nosy-user.h.The files added here are taken fromgit://anongit.freedesktop.org/~krh/nosy commit ee29be97 (2009-11-10)with the following changes by Stefan Richter: - Kconfig and Makefile hunks are written from scratch. - Commented out version printk in nosy.c. - Included missing , reported by Stephen Rothwell."git shortlog nosy{-user.h,.c,.h}" from nosy's git repository:Jonathan Woithe (2): Nosy updates for recent kernels Fix uninitialised memory (needed for 2.6.31 kernel)Kristian Høgsberg (5): Pull over nosy from mercurial repo. Use a misc device instead. Add simple AV/C decoder. Don't break down on big payloads. Set parent device for misc device.As a low-level IEEE 1394 driver, its files are placed intodrivers/firewire/ although nosy is not part of the firewire driverstack.I am aware of the following literature from Texas Instruments aboutPCILynx programming: SCPA020A - PCILynx 1394 to PCI Bus Interface TSB12LV21BPGF Functional Specification SLLA023 - Initialization and Asynchronous Programming of the TSB12LV21A 1394 DeviceSigned-off-by: Stefan Richter Acked-by: Kristian Høgsberg List of files: /linux-6.15/drivers/firewire/Kconfig

5d7db049 - firewire, ieee1394: update Kconfig help

Sat, 26 Dec 2009 00:36:53 +0000

firewire, ieee1394: update Kconfig helpUpdate the Kconfig help texts of both stacks to encourage a general movefrom the older to the newer drivers. However, do not label ieee1394 as"Obsolete" yet, as the newer drivers have not been deployed as defaultstack in the majority of Linux distributions yet, and those who startdoing so now may still want to install the old drivers as fallback forunforeseen issues.Since Linux 2.6.32, FireWire audio devices can be driven by the newerfirewire driver stack too, hence remove an outdated comment about audiodevices. Also remove comments about library versions since the 2ndgeneration of libraw1394 and libdc1394 is now in common use; details onlibrary versions can be read at the wiki link from the help texts.Signed-off-by: Stefan Richter List of files: /linux-6.15/drivers/firewire/Kconfig

0c53decd - firewire: new stack is no longer experimental

Tue, 16 Jun 2009 20:36:34 +0000

firewire: new stack is no longer experimentalThe new stack is now recommended over the old one if used for industrialvideo (IIDC/DCAM) or for storage devices (SBP-2) due to betterperformance, improved compatibility, added features, and security. Itshould also be functionally on par with and is more secure than the oldieee1394 stack in the use case of consumer video devices.IP-over-1394 support for the new stack is currently emerging, and abackend of the firedtv DVB driver to the new stack should be availablesoon.The one remaining area where the old stack is still required are audiodevices, as the new stack is not yet able to support the FFADO FireWireaudio framework.Signed-off-by: Stefan Richter List of files: /linux-6.15/drivers/firewire/Kconfig