Man page or keyword search:   man All Sections 1 - General Commands 2 - System Calls 3 - Subroutines, Functions 4 - Special Files 5 - File Formats 6 - Games and Screensavers 7 - Macros and Conventions 8 - Maintenence Commands 9 - Kernel Interface New Commands Server 4.4BSD AIX Alpinelinux Archlinux Aros BSDOS BSDi Bifrost CentOS Cygwin Darwin Debian DigitalUNIX DragonFly ElementaryOS Fedora FreeBSD Gentoo GhostBSD HP-UX Haiku Hurd IRIX Inferno JazzOS Kali Knoppix LinuxMint MacOSX Mageia Mandriva Manjaro Minix MirBSD NeXTSTEP NetBSD OPENSTEP OSF1 OpenBSD OpenDarwin OpenIndiana OpenMandriva OpenServer OpenSuSE OpenVMS Oracle PC-BSD Peanut Pidora Plan9 QNX Raspbian RedHat Scientific Slackware SmartOS Solaris SuSE SunOS Syllable Tru64 UNIXv7 Ubuntu Ultrix UnixWare Xenix YellowDog aLinux   26626 pages apropos Keyword Search (all sections) Output format html ascii pdf view pdf save postscript

PCI_ENABLE_OBFF(9)	      Hardware Interfaces	    PCI_ENABLE_OBFF(9)

NAME
       pci_enable_obff - enable optimized buffer flush/fill

SYNOPSIS
       int pci_enable_obff(struct pci_dev * dev,
			   enum pci_obff_signal_type type);

ARGUMENTS
       dev
	   PCI device

       type
	   type of signaling to use

DESCRIPTION
       Try to enable type OBFF signaling on dev. It will try using WAKE#
       signaling if possible, falling back to message signaling only if WAKE#
       isn´t supported.	 type should indicate whether the PCIe link be brought
       out of L0s or L1 to send the message. It should be either
       PCI_EXP_OBFF_SIGNAL_ALWAYS or PCI_OBFF_SIGNAL_L0.

       If your device can benefit from receiving all messages, even at the
       power cost of bringing the link back up from a low power state, use
       PCI_EXP_OBFF_SIGNAL_ALWAYS. Otherwise, use PCI_OBFF_SIGNAL_L0 (the
       preferred type).

RETURNS
       Zero on success, appropriate error number on failure.

COPYRIGHT
Kernel Hackers Manual 2.6.	 November 2013		    PCI_ENABLE_OBFF(9)

Vote for polarhome