Home
last modified time | relevance | path

Searched +full:out +full:- +full:of +full:- +full:band (Results 1 – 25 of 49) sorted by relevance

12

/Documentation/devicetree/bindings/net/
Dbtusb.txt2 ---------------------------------------------------
6 - compatible : should comply with the format "usbVID,PID" specified in
7 Documentation/devicetree/bindings/usb/usb-device.yaml
8 At the time of writing, the only OF supported devices
13 "usb4ca,301a" (Qualcomm QCA6174A (Lite-On))
17 Documentation/devicetree/bindings/net/marvell-bt-8xxx.txt
21 - interrupt-names: (see below)
22 - interrupts : The interrupt specified by the name "wakeup" is the interrupt
23 that shall be used for out-of-band wake-on-bt. Driver will
26 platform out of band. During system resume, the irq will be
[all …]
/Documentation/userspace-api/media/v4l/
Dvidioc-enum-freq-bands.rst1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
13 VIDIOC_ENUM_FREQ_BANDS - Enumerate supported frequency bands
36 fields, and zero out the ``reserved`` array of a struct
41 of the corresponding tuner/modulator is set.
47 .. flat-table:: struct v4l2_frequency_band
48 :header-rows: 0
49 :stub-columns: 0
52 * - __u32
53 - ``tuner``
54 - The tuner or modulator index number. This is the same value as in
[all …]
Dvidioc-s-hw-freq-seek.rst1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
13 VIDIOC_S_HW_FREQ_SEEK - Perform a hardware frequency seek
37 zero out the ``reserved`` array of a struct
41 The ``rangelow`` and ``rangehigh`` fields can be set to a non-zero value
42 to tell the driver to search a specific band. If the struct
45 within one of the bands returned by
48 must exactly match those of one of the bands returned by
50 current frequency of the tuner does not fall within the selected band it
51 will be clamped to fit in the band before the seek is started.
58 If this ioctl is called from a non-blocking filehandle, then ``EAGAIN``
[all …]
/Documentation/devicetree/bindings/mailbox/
Darm,mhuv3.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Sudeep Holla <sudeep.holla@arm.com>
11 - Cristian Marussi <cristian.marussi@arm.com>
17 The controller can optionally support a varying number of extensions that, in
18 turn, enable different kinds of transport to be used for communication.
19 Number, type and characteristics of each supported extension can be discovered
22 Given the unidirectional nature of the controller, an MHUv3 mailbox controller
23 is composed of a MHU Sender (MHUS) containing a PostBox (PBX) block and a MHU
[all …]
/Documentation/ABI/stable/
Dsysfs-class-bluetooth2 Date: 14-Jan-2025
4 Contact: linux-bluetooth@vger.kernel.org
5 Description: This write-only attribute allows users to trigger the vendor reset
8 (e.g., UART/USB), and can also be done through an out-of-band
/Documentation/filesystems/
Dinotify.rst1 .. SPDX-License-Identifier: GPL-2.0
4 Inotify - A Powerful yet Simple File Change Notification System
13 - Deleted obsoleted interface, just refer to manpages for user interface.
18 What is the design decision behind not tying the watch to the open fd of
29 What is the design decision behind using an-fd-per-instance as opposed to
30 an fd-per-watch?
33 An fd-per-watch quickly consumes more file descriptors than are allowed,
35 select()-able. Yes, root can bump the per-process fd limit and yes, users
38 spaces is thus sensible. The current design is what user-space developers
41 thousand times is silly. If we can implement user-space's preferences
[all …]
Dorangefs.rst1 .. SPDX-License-Identifier: GPL-2.0
7 OrangeFS is an LGPL userspace scale-out parallel storage system. It is ideal
13 Virtual Machine (PVM) as part of a NASA grant to study the I/O patterns
14 of parallel programs.
51 On Fedora, install orangefs and orangefs-server::
53 dnf -y install orangefs orangefs-server
64 pvfs2-client-core.
68 pvfs2-server -f /etc/orangefs/orangefs.conf
72 systemctl start orangefs-server
76 pvfs2-ping -m /pvfsmnt
[all …]
/Documentation/devicetree/bindings/mtd/
Draw-nand-chip.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/mtd/raw-nand-chip.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Miquel Raynal <miquel.raynal@bootlin.com>
13 - $ref: nand-chip.yaml#
17 desires in terms of correction capability of a controller. Together,
21 The interpretation of these parameters is implementation-defined, so
28 pattern: "^nand@[a-f0-9]$"
32 Contains the chip-select IDs.
[all …]
/Documentation/devicetree/bindings/hwmon/
Dadi,ltc2947.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Nuno Sá <nuno.sa@analog.com>
15 https://www.analog.com/media/en/technical-documentation/data-sheets/LTC2947.pdf
20 - adi,ltc2947
33 adi,accumulator-ctl-pol:
35 This property controls the polarity of current that is accumulated to
37 positive current for example. Since there are two sets of registers for
39 energy1/charge1 and energy2/charger2 respectively. Check table 12 of the
[all …]
/Documentation/driver-api/usb/
Dbulk-streams.rst11 Streams are defined in sections 4.4.6.4 and 8.12.1.4 of the Universal Serial Bus
17 Device-side implications
21 an out-of-band mechanism on another endpoint) that data is ready for that stream
39 pass an array of usb_host_endpoints that need to be setup with similar stream
41 ID for the bulk IN and OUT endpoints used in a Bi-directional command sequence.
43 The return value is an error condition (if one of the endpoints doesn't support
44 streams, or the xHCI driver ran out of memory), or the number of streams the
51 Do NOT call this function if you have URBs enqueued for any of the endpoints
64 usb_alloc_streams() returns with a value of N, you may use streams 1 though N.
65 To queue an URB for a specific stream, set the urb->stream_id value. If the
/Documentation/admin-guide/media/
Dsi470x.rst1 .. SPDX-License-Identifier: GPL-2.0
12 -----------------------------
14 Silicon Laboratories is the manufacturer of the radio ICs, that nowadays are the
18 Part of this reference design is also a radio application in binary and source
25 -------------
30 - Si4700: FM radio receiver
31 - Si4701: FM radio receiver, RDS Support
32 - Si4702: FM radio receiver
33 - Si4703: FM radio receiver, RDS Support
34 - Si4704: FM radio receiver, no external antenna required
[all …]
Dvivid.rst1 .. SPDX-License-Identifier: GPL-2.0
6 This driver emulates video4linux hardware of various types: video capture, video
13 Each input can be a webcam, TV capture device, S-Video capture device or an HDMI
14 capture device. Each output can be an S-Video output device or an HDMI output
23 - Support for read()/write(), MMAP, USERPTR and DMABUF streaming I/O.
24 - A large list of test patterns and variations thereof
25 - Working brightness, contrast, saturation and hue controls
26 - Support for the alpha color component
27 - Full colorspace support, including limited/full RGB range
28 - All possible control types are present
[all …]
/Documentation/arch/x86/
Dorc-unwinder.rst1 .. SPDX-License-Identifier: GPL-2.0
12 format of the ORC data is much simpler than DWARF, which in turn allows
15 The ORC data consists of unwind tables which are generated by objtool.
16 They contain out-of-band data which is used by the in-kernel ORC
17 unwinder. Objtool generates the ORC data by first doing compile-time
19 all the code paths of a .o file, it determines information about the
23 The per-object ORC sections are combined at link time and are sorted and
24 post-processed at boot time. The unwinder uses the resulting data to
33 3.2%, resulting in a broad kernel-wide slowdown. Measurements by Mel
34 Gorman [1]_ have shown a slowdown of 5-10% for some workloads.
[all …]
/Documentation/networking/dsa/
Dsja1105.rst8 The NXP SJA1105 is a family of 10 SPI-managed automotive switches:
10 - SJA1105E: First generation, no TTEthernet
11 - SJA1105T: First generation, TTEthernet
12 - SJA1105P: Second generation, no TTEthernet, no SGMII
13 - SJA1105Q: Second generation, TTEthernet, no SGMII
14 - SJA1105R: Second generation, no TTEthernet, SGMII
15 - SJA1105S: Second generation, TTEthernet, SGMII
16 - SJA1110A: Third generation, TTEthernet, SGMII, integrated 100base-T1 and
17 100base-TX PHYs
18 - SJA1110B: Third generation, TTEthernet, SGMII, 100base-T1, 100base-TX
[all …]
Dbcm_sf2.rst8 - xDSL gateways such as BCM63138
9 - streaming/multimedia Set Top Box such as BCM7445
10 - Cable Modem/residential gateways such as BCM7145/BCM3390
13 ports, offering a range of built-in and customizable interfaces:
15 - single integrated Gigabit PHY
16 - quad integrated Gigabit PHY
17 - quad external Gigabit PHY w/ MDIO multiplexer
18 - integrated MoCA PHY
19 - several external MII/RevMII/GMII/RGMII interfaces
22 fail-over not to lose packets during a MoCA role re-election, as well as out of
[all …]
/Documentation/networking/
Dxdp-rx-metadata.rst1 .. SPDX-License-Identifier: GPL-2.0
8 hardware metadata related to a packet using a set of helper functions,
14 XDP has access to a set of kfuncs to manipulate the metadata in an XDP frame.
16 implement these kfuncs. The set of kfuncs is declared in ``include/net/xdp.h``
22 .. kernel-doc:: net/core/xdp.c
25 .. kernel-doc:: net/core/xdp.c
28 .. kernel-doc:: net/core/xdp.c
34 ahead of the packet. Not all packets will necessary have the requested
35 metadata available in which case the driver returns ``-ENODATA``.
38 implemented, the default ones that return ``-EOPNOTSUPP`` will be used
[all …]
/Documentation/driver-api/mei/
Diamt.rst1 .. SPDX-License-Identifier: GPL-2.0
6 Prominent usage of the Intel ME Interface is to communicate with Intel(R)
10 Intel AMT provides the ability to manage a host remotely out-of-band (OOB)
14 Some examples of Intel AMT usage are:
15 - Monitoring hardware state and platform components
16 - Remote power off/on (useful for green computing or overnight IT
18 - OS updates
19 - Storage of useful platform information such as software assets
20 - Built-in hardware KVM
21 - Selective network isolation of Ethernet and IP protocol flows based
[all …]
/Documentation/ABI/testing/
Dsysfs-firmware-qemu_fw_cfg11 useful as an out-of-band, asynchronous mechanism for providing
14 The authoritative guest-side hardware interface documentation
17 https://qemu-project.gitlab.io/qemu/specs/fw_cfg.html
24 presence or size of "legacy" blobs (with selector keys between
50 name The 56-byte nul-terminated ASCII string used as the
52 size The length of the blob, as given in the fw_cfg
54 key The value of the blob's selector key as given in the
57 raw The raw bytes of the blob, obtained by selecting the
59 of bytes equal to the blob size from the data
73 "etc/boot-fail-wait"
[all …]
Dsysfs-platform-mellanox-bootctl6 The Life-cycle state of the SoC, which could be one of the
12 GA Non-Secured Non-Secure chip and not able to change state
30 The source of the boot stream for the next reset. It could be
31 one of the following values:
44 Update the source of the boot stream after next reset. It could
45 be one of the following values and will be applied after next
61 The state of eFuse versions with the following values.
94 the out-of-band 1Gbps Ethernet port. This MAC address is
95 provided on a board-level label.
103 This value is provided on a board-level label.
[all …]
/Documentation/admin-guide/pm/
Dsuspend-flows.rst1 .. SPDX-License-Identifier: GPL-2.0
12 At least one global system-wide transition needs to be carried out for the
13 system to get from the working state into one of the supported
14 :doc:`sleep states <sleep-states>`. Hibernation requires more than one
16 referred to as *system-wide suspend* (or simply *system suspend*) states, need
19 For those sleep states, the transition from the working state of the system into
21 of cases, whether this means a transition or a sleep state of the system should
26 different sleep states of the system are quite similar, but there are some
27 significant differences between the :ref:`suspend-to-idle <s2idle>` code flows
28 and the code flows related to the :ref:`suspend-to-RAM <s2ram>` and
[all …]
Dsleep-states.rst1 .. SPDX-License-Identifier: GPL-2.0
13 Sleep states are global low-power states of the entire system in which user
21 Depending on its configuration and the capabilities of the platform it runs on,
23 hibernation and up to three variants of system suspend. The sleep states that
28 Suspend-to-Idle
29 ---------------
31 This is a generic, pure software, light-weight variant of system suspend (also
34 I/O devices into low-power states (possibly lower-power than available in the
38 The system is woken up from this state by in-band interrupts, so theoretically
43 or :ref:`suspend-to-RAM <s2ram>`, or it can be used in addition to any of the
[all …]
/Documentation/gpu/rfc/
Di915_scheduler.rst14 * Lots of rework will need to be done to integrate with DRM scheduler so
38 * Lots of complexity of the GuC backend can be pulled out once
48 * Fully integrating would add lots of complexity to DRM
54 * Remove in-order completion assumptions from DRM scheduler
57 finish out of order
58 * Pull out i915 priority levels and use DRM priority levels
75 * -1k to -1 Low priority
80 band is reserved with the kernel. This aligns with the DRM scheduler priority
84 ----------------
86 * https://www.khronos.org/registry/vulkan/specs/1.2-extensions/html/chap5.html#devsandqueues-priori…
[all …]
/Documentation/devicetree/bindings/net/wireless/
Dbrcm,bcm4329-fmac.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/net/wireless/brcm,bcm4329-fmac.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Arend van Spriel <arend@broadcom.com>
19 - $ref: ieee80211.yaml#
24 - items:
25 - enum:
26 - brcm,bcm43143-fmac
27 - brcm,bcm4341b0-fmac
[all …]
/Documentation/power/
Dsuspend-and-cpuhotplug.rst2 Interaction of Suspend code (S3) with the CPU hotplug infrastructure
5 (C) 2011 - 2014 Srivatsa S. Bhat <srivatsa.bhat@linux.vnet.ibm.com>
8 I. Differences between CPU hotplug and Suspend-to-RAM
11 How does the regular CPU hotplug code differ from how the Suspend-to-RAM
14 Well, a picture is worth a thousand words... So ASCII art follows :-)
20 of describing where they take different paths and where they share code.
21 What happens when regular CPU hotplug and Suspend-to-RAM race with each other
24 On a high level, the suspend-resume cycle goes like this::
26 |Freeze| -> |Disable nonboot| -> |Do suspend| -> |Enable nonboot| -> |Thaw |
33 -----------------
[all …]
/Documentation/arch/powerpc/
Dpapr_hcalls.rst1 .. SPDX-License-Identifier: GPL-2.0
4 Hypercall Op-codes (hcalls)
10 Virtualization on 64-bit Power Book3S Platforms is based on the PAPR
11 specification [1]_ which describes the run-time environment for a guest
15 - **IBM PowerVM (PHYP)**: IBM's proprietary hypervisor that supports AIX,
16 IBM-i and Linux as supported guests (termed as Logical Partitions
19 - **Qemu/KVM**: Supports PPC64 linux guests running on a PPC64 linux host.
20 Though it only implements a subset of PAPR specification called LoPAPR [2]_.
22 On PPC64 arch a guest kernel running on top of a PAPR hypervisor is called
29 asking hypervisor to perform a privileged operation on behalf of the guest. The
[all …]

12