Searched full:instances (Results 1 – 25 of 194) sorted by relevance
12345678
| /Documentation/ABI/testing/ |
| D | sysfs-fs-incfs | 24 What: /sys/fs/incremental-fs/instances/[name]
31 What: /sys/fs/incremental-fs/instances/[name]/reads_delayed_min
37 What: /sys/fs/incremental-fs/instances/[name]/reads_delayed_min_us
43 What: /sys/fs/incremental-fs/instances/[name]/reads_delayed_pending
49 What: /sys/fs/incremental-fs/instances/[name]/reads_delayed_pending_us
55 What: /sys/fs/incremental-fs/instances/[name]/reads_failed_hash_verification
61 What: /sys/fs/incremental-fs/instances/[name]/reads_failed_other
67 What: /sys/fs/incremental-fs/instances/[name]/reads_failed_timed_out
|
| D | sysfs-platform-intel-ifs | 39 is loaded reports "none". Only present for device instances where a test image
51 This file is present only for device instances where a test image is applicable.
|
| /Documentation/filesystems/ |
| D | incfs.rst | 47 /sys/fs/incremental-fs/instances/[name]
51 /sys/fs/incremental-fs/instances/[name]/reads_delayed_min
55 /sys/fs/incremental-fs/instances/[name]/reads_delayed_min_us
59 /sys/fs/incremental-fs/instances/[name]/reads_delayed_pending
63 /sys/fs/incremental-fs/instances/[name]/reads_delayed_pending_us
67 /sys/fs/incremental-fs/instances/[name]/reads_failed_hash_verification
70 /sys/fs/incremental-fs/instances/[name]/reads_failed_other
74 /sys/fs/incremental-fs/instances/[name]/reads_failed_timed_out
|
| /Documentation/driver-api/media/ |
| D | v4l2-intro.rst | 21 This meant that all drivers had to do the setup of device instances and
57 device instances
59 +-sub-device instances
63 \-filehandle instances
71 sub-device instances, the video_device struct stores V4L2 device node data
72 and the v4l2_fh struct keeps track of filehandle instances.
|
| /Documentation/devicetree/bindings/iommu/ |
| D | ti,omap-iommu.txt | 5 "ti,omap2-iommu" for OMAP2/OMAP3 IOMMU instances
6 "ti,omap4-iommu" for OMAP4/OMAP5 IOMMU instances
7 "ti,dra7-dsp-iommu" for DRA7xx DSP IOMMU instances
8 "ti,dra7-iommu" for DRA7xx IOMMU instances
27 is required for DSP IOMMU instances on DRA7xx SoCs. The
|
| /Documentation/networking/devlink/ |
| D | index.rst | 25 Nested instances
29 devlink instances created underneath. In that case, drivers should make
33 lock of both nested and parent instances at the same time, devlink
40 devlink relationship (could be user for multiple nested instances.
|
| D | devlink-reload.rst | 69 The netns option allows user to be able to move devlink instances into
71 By default all devlink instances are created in init_net and stay there.
|
| /Documentation/devicetree/bindings/clock/ti/ |
| D | dra7-atl.txt | 4 audio codec. A single ATL IP provides four ATL clock instances sharing the same
16 Since the clock instances are part of a single IP this binding is used as a node
29 configuration of the IP for the ATL clock instances.
40 Configuration of ATL instances:
|
| /Documentation/networking/ |
| D | napi.rst | 40 from the system. The instances are attached to the netdevice passed
42 unregistered). Instances are added in a disabled state.
153 Modern devices have multiple NAPI instances (struct napi_struct) per
154 interface. There is no strong requirement on how the instances are
159 NAPI instances most often correspond 1:1:1 to interrupts and queue pairs
163 or Rx and Tx queues can be serviced by separate NAPI instances on a single
165 a 1:1 mapping between NAPI instances and interrupts.
240 NAPI instances of that device. Each NAPI instance will spawn a separate
245 between IRQs and NAPI instances may not be trivial (and is driver
|
| /Documentation/netlink/specs/ |
| D | devlink.yaml | 1234 doc: Get devlink instances.
1257 doc: Get devlink port instances.
1281 doc: Set devlink port instances.
1298 doc: Create devlink port instances.
1320 doc: Delete devlink port instances.
1332 doc: Split devlink port instances.
1348 doc: Unplit devlink port instances.
1360 doc: Get shared buffer instances.
1382 doc: Get shared buffer pool instances.
1405 doc: Set shared buffer pool instances.
[all …]
|
| /Documentation/driver-api/hte/ |
| D | tegra-hte.rst | 9 driver implements two GTE instances: 1) GPIO GTE and 2) LIC
10 (Legacy Interrupt Controller) IRQ GTE. Both GTE instances get the timestamp
44 The provider source code of both IRQ and GPIO GTE instances is located at
|
| /Documentation/devicetree/bindings/phy/ |
| D | phy-tegra194-p2u.yaml | 14 Speed) each interfacing with 12 and 8 P2U instances respectively.
16 each interfacing with 8, 8 and 8 P2U instances respectively.
|
| /Documentation/devicetree/bindings/soc/ti/ |
| D | keystone-navigator-dma.txt | 28 - clocks: phandle to dma instances clocks. The clock handles can be as
29 many as the dma instances. The order should be maintained as per
30 the dma instances.
|
| /Documentation/trace/rv/ |
| D | da_monitor_synthesis.rst | 15 the *RV monitor* abstraction. The RV monitor includes a set of instances
79 This initial implementation presents three different types of monitor instances:
86 the second for monitors with per-cpu instances, and the third with per-task
87 instances.
|
| /Documentation/arch/s390/ |
| D | vfio-ap-locking.rst | 8 will be used to denote instances of the structures herein described:
67 matrix_mdev instances (matrix_dev->mdev_list) that represent mediated devices
75 2. To add matrix_mdev instances to or remove them from matrix_dev->mdev_list.
|
| /Documentation/devicetree/bindings/interrupt-controller/ |
| D | ti,pruss-intc.yaml | 20 including the MPU and/or other PRUSS instances, DSPs or devices.
30 through 19) are connected to new sub-modules within the ICSSG instances.
97 instances.
|
| /Documentation/process/ |
| D | code-of-conduct.rst | 46 any instances of unacceptable behavior.
67 Instances of abusive, harassing, or otherwise unacceptable behavior may be
|
| /Documentation/gpu/rfc/ |
| D | i915_scheduler.rst | 111 Certain use cases require BBs to be placed on engine instances in logical order
112 (e.g. split-frame on gen11+). The logical mapping of engine instances can change
117 Lastly, all current platforms have at most 2 engine instances and the logical
119 engine instances.
|
| /Documentation/devicetree/bindings/timestamp/ |
| D | nvidia,tegra194-hte.yaml | 13 Tegra SoC has two instances of generic hardware timestamping engines (GTE)
50 GTE instances for both Tegra194 and Tegra234 has 3 slices. The Tegra194
|
| /Documentation/usb/ |
| D | raw-gadget.rst | 35 having multiple Raw Gadget instances bound to different UDCs.
48 for details. Multiple Raw Gadget instances (bound to different UDCs) can be
|
| /Documentation/filesystems/ext4/ |
| D | ifork.rst | 59 instances of ``struct ext4_extent_idx``; each of these index entries
62 ``eh.eh_entries`` instances of ``struct ext4_extent``; these instances
|
| /Documentation/devicetree/bindings/reset/ |
| D | brcm,bcm7216-pcie-sata-rescal.yaml | 12 instances on BCM7216.
|
| /Documentation/driver-api/thermal/ |
| D | cpu-cooling-api.rst | 30 "thermal-cpufreq-%x". This api can support multiple instances of cpufreq
44 instances of cpufreq cooling devices.
|
| /Documentation/admin-guide/ |
| D | binderfs.rst | 9 other binderfs instances. Mounting a new binderfs instance makes it possible
31 binderfs instances can be mounted with a limit on the number of binder
|
| /Documentation/admin-guide/perf/ |
| D | arm-ni.rst | 8 the clock domain ID within that particular instance. If multiple NI instances
|
12345678