/openbmc/linux/Documentation/ABI/testing/ |
H A D | sysfs-bus-pci-drivers-xhci_hcd | 32 presented in the USB device descriptor by this xhci debug 45 presented in the USB device descriptor by this xhci debug 57 presented in the USB device descriptor by this xhci debug 70 presented in the USB Interface descriptor by the xhci debug
|
H A D | sysfs-class-scsi_tape | 44 This value is presented in bytes because tape drives support 75 This value is presented in bytes because tape drives support
|
H A D | sysfs-firmware-dmi-tables | 16 presented as binary attributes and are accessible via:
|
/openbmc/linux/include/linux/clk/ |
H A D | analogbits-wrpll-cln28hpc.h | 38 * @divr: reference divider value (6 bits), as presented to the PLL signals 39 * @divf: feedback divider value (9 bits), as presented to the PLL signals 40 * @divq: output divider value (3 bits), as presented to the PLL signals
|
/openbmc/u-boot/drivers/clk/sifive/ |
H A D | analogbits-wrpll-cln28hpc.h | 53 * @divr: reference divider value (6 bits), as presented to the PLL signals. 54 * @divf: feedback divider value (9 bits), as presented to the PLL signals. 55 * @divq: output divider value (3 bits), as presented to the PLL signals.
|
/openbmc/linux/Documentation/admin-guide/acpi/ |
H A D | fan_performance_states.rst | 76 The support of fine grain control is presented via sysfs attribute 80 This sysfs attribute is presented in the same directory as performance states. 89 This speed is presented in the sysfs using the attribute "fan_speed_rpm",
|
/openbmc/qemu/docs/system/s390x/ |
H A D | pcidevices.rst | 26 Instead, ``uid`` and ``fid`` determine how the device is presented to the guest 36 will be presented in the guest as::
|
/openbmc/linux/Documentation/trace/rv/ |
H A D | deterministic_automata.rst | 31 One of the benefits of this formal definition is that it can be presented 55 For example, the 'wip' automata can be presented as (augmented with comments):: 144 presented in [3].
|
H A D | da_monitor_instrumentation.rst | 165 [1] The wip model is presented in:: 169 The wip monitor is presented in::
|
/openbmc/linux/Documentation/arch/s390/ |
H A D | cds.rst | 77 routine whenever an I/O interrupt is presented to the system. The do_IRQ() 234 user_intparm user specific interrupt information; will be presented 306 interrupt will be presented to indicate I/O completion as the I/O request was 383 and Device-End status to be presented together, with a single interrupt. 387 result will be presented by a single interrupt anyway. 392 case all I/O interruptions are presented to the device driver until final 395 If a device is able to recover from asynchronously presented I/O errors, it can 407 presented to the device driver while overlapping I/O is performed. When a 408 secondary status without error (alert status) is presented, this indicates
|
/openbmc/linux/drivers/staging/media/atomisp/pci/hive_isp_css_include/host/ |
H A D | input_formatter_public.h | 39 there are only a fixed number of frames, presented only once. By 40 enabling blocking the inputformatter will wait on the first presented
|
/openbmc/linux/Documentation/driver-api/usb/ |
H A D | typec.rst | 30 Every port will be presented as its own device under /sys/class/typec/. The 33 When connected, the partner will be presented also as its own device under 39 The cable and the two plugs on it may also be optionally presented as their own 50 mode of port0-partner will be presented under /sys/class/typec/port0-partner/.
|
/openbmc/qemu/docs/system/ |
H A D | device-emulation.rst | 18 A device front end is how a device is presented to the guest. The type 19 of device presented should match the hardware that the guest operating
|
/openbmc/linux/Documentation/admin-guide/pm/ |
H A D | intel_uncore_frequency_scaling.rst | 82 support), sysfs is enhanced. This granular interface is presented in the 100 The other attributes are same as presented at package_*_die_* level.
|
/openbmc/qemu/include/hw/mem/ |
H A D | nvdimm.h | 54 * the size of label data in NVDIMM device which is presented to 67 * it's the PMEM region in NVDIMM device, which is presented to
|
/openbmc/linux/drivers/iio/orientation/ |
H A D | Kconfig | 28 is presented using quaternion format.
|
/openbmc/openbmc/poky/meta/files/common-licenses/ |
H A D | HaskellReport | 6 …tributed for any purpose, provided that the modified version is clearly presented as such, and tha…
|
H A D | DL-DE-ZERO-2.0 | 19 be copied, printed, presented, altered, processed and transmitted to third parties;
|
/openbmc/linux/Documentation/networking/ |
H A D | ppp_generic.rst | 123 presented to the start_xmit() function contain only the 2-byte 124 protocol number and the data, and the skbuffs presented to ppp_input() 135 If the channel needs some headroom in the skbuffs presented to it for 144 headroom in the skbuffs presented to ppp_input(). The generic PPP 319 to. Once two channels are bridged, frames presented to one channel by
|
/openbmc/linux/drivers/iio/common/cros_ec_sensors/ |
H A D | Kconfig | 22 presented by the ChromeOS EC Sensor hub.
|
/openbmc/linux/drivers/rtc/ |
H A D | rtc-wilco-ec.c | 46 * All values are presented in binary (not BCD). 73 * All values are presented in BCD.
|
/openbmc/linux/arch/arm/mach-omap2/ |
H A D | clockdomain.c | 188 * Returns -EINVAL if presented with invalid clockdomain pointers, 231 * wakes up. Returns -EINVAL if presented with invalid clockdomain 275 * presented with invalid clockdomain pointers or called on a machine 320 * if presented with invalid clockdomain pointers or called on a machine 589 * Returns -EINVAL if presented with invalid clockdomain pointers, 618 * wakes up. Returns -EINVAL if presented with invalid clockdomain 708 * presented with invalid clockdomain pointers or called on a machine 739 * if presented with invalid clockdomain pointers or called on a machine
|
/openbmc/linux/drivers/iio/accel/ |
H A D | cros_ec_accel_legacy.c | 9 * Accelerometer access is presented through iio sysfs. 232 /* The lid sensor needs to be presented inverted. */ in cros_ec_accel_legacy_probe()
|
/openbmc/linux/Documentation/userspace-api/media/mediactl/ |
H A D | media-controller-intro.rst | 15 presented to userspace applications as V4L2 and ALSA capture devices.
|
/openbmc/linux/arch/powerpc/include/asm/ |
H A D | hvcserver.h | 27 * This structure outlines the format that partner info is presented to a caller
|