51 lines · plain
1===========================================2Firewire (IEEE 1394) driver Interface Guide3===========================================4 5Introduction and Overview6=========================7 8The Linux FireWire subsystem adds some interfaces into the Linux system to9 use/maintain+any resource on IEEE 1394 bus.10 11The main purpose of these interfaces is to access address space on each node12on IEEE 1394 bus by ISO/IEC 13213 (IEEE 1212) procedure, and to control13isochronous resources on the bus by IEEE 1394 procedure.14 15Two types of interfaces are added, according to consumers of the interface. A16set of userspace interfaces is available via `firewire character devices`. A set17of kernel interfaces is available via exported symbols in `firewire-core` module.18 19Firewire char device data structures20====================================21 22.. include:: ../ABI/stable/firewire-cdev23 :literal:24 25.. kernel-doc:: include/uapi/linux/firewire-cdev.h26 :internal:27 28Firewire device probing and sysfs interfaces29============================================30 31.. include:: ../ABI/stable/sysfs-bus-firewire32 :literal:33 34.. kernel-doc:: drivers/firewire/core-device.c35 :export:36 37Firewire core transaction interfaces38====================================39 40.. kernel-doc:: drivers/firewire/core-transaction.c41 :export:42 43Firewire Isochronous I/O interfaces44===================================45 46.. kernel-doc:: include/linux/firewire.h47 :functions: fw_iso_context_schedule_flush_completions48.. kernel-doc:: drivers/firewire/core-iso.c49 :export:50 51