Searched full:instance (Results 1 – 25 of 581) sorted by relevance
12345678910>>...24
| /Documentation/trace/ |
| D | boottime-trace.rst | 56 Ftrace Per-instance Options
59 These options can be used for each instance including global ftrace node.
61 ftrace.[instance.INSTANCE.]options = OPT1[, OPT2[...]]
64 ftrace.[instance.INSTANCE.]tracing_on = 0|1
65 Enable/Disable tracing on this instance when starting boot-time tracing.
68 ftrace.[instance.INSTANCE.]trace_clock = CLOCK
71 ftrace.[instance.INSTANCE.]buffer_size = SIZE
75 ftrace.[instance.INSTANCE.]alloc_snapshot
78 ftrace.[instance.INSTANCE.]cpumask = CPUMASK
81 ftrace.[instance.INSTANCE.]events = EVENT[, EVENT2[...]]
[all …]
|
| /Documentation/devicetree/bindings/clock/ |
| D | qcom,mmcc.yaml | 85 - description: DSI phy instance 1 dsi clock
86 - description: DSI phy instance 1 byte clock
87 - description: DSI phy instance 2 dsi clock
88 - description: DSI phy instance 2 byte clock
117 - description: DSI phy instance 0 dsi clock
118 - description: DSI phy instance 0 byte clock
145 - description: DSI phy instance 0 dsi clock
146 - description: DSI phy instance 0 byte clock
147 - description: DSI phy instance 1 dsi clock
148 - description: DSI phy instance 1 byte clock
[all …]
|
| /Documentation/admin-guide/ |
| D | binderfs.rst | 8 located in a new binderfs instance are independent of binder devices located in
9 other binderfs instances. Mounting a new binderfs instance makes it possible
20 at which point a new instance of binderfs will show up at ``/dev/binderfs``.
21 In a fresh instance of binderfs no binder devices will be present. There will
23 binderfs. Mounting another binderfs instance at a different location will
24 create a new and separate instance from all other binderfs mounts. This is
33 a per-instance limit. If ``max=<count>`` is set then only ``<count>`` number
34 of binder devices can be allocated in this binderfs instance.
38 ``stats=global`` is only available for a binderfs instance mounted in the
40 instance in another user namespace will return a permission error.
[all …]
|
| /Documentation/networking/devlink/ |
| D | index.rst | 15 the devlink instance lock is already held. Drivers can take the instance
19 Drivers are encouraged to use the devlink instance lock for their own needs.
21 Drivers need to be cautious when taking devlink instance lock and
22 taking RTNL lock at the same time. Devlink instance lock needs to be taken
32 - Lock ordering should be maintained. If driver needs to take instance
34 instance lock of the parent instance should be taken first, only then
35 instance lock of the nested instance could be taken.
|
| /Documentation/devicetree/bindings/net/ |
| D | intel,ixp4xx-hss.yaml | 24 description: The HSS instance
30 - description: phandle to the NPE this HSS instance is using
31 - description: the NPE instance number
32 description: phandle to the NPE this HSS instance is using
33 and the instance to use in the second cell
40 - description: the queue instance number
48 - description: the queue instance number
56 - description: the queue instance number
65 - description: the queue instance number
74 - description: the queue instance number
[all …]
|
| D | intel,ixp4xx-ethernet.yaml | 35 - description: RX queue instance to use
43 - description: TX READY queue instance to use
54 - description: phandle to the NPE this ethernet instance is using
55 - description: the NPE instance to use
56 description: phandle to the NPE this ethernet instance is using
57 and the instance to use in the second cell
|
| /Documentation/ABI/testing/ |
| D | debugfs-scmi | 5 Description: The name of the underlying SCMI instance <n> described by
8 this SCMI instance is rooted.
16 on this SCMI instance <n>, the threshold above which any SCMI
27 SCMI instance <n>.
35 SCMI instance <n> is capable of atomic mode of operation.
43 for the currently configured SCMI transport for instance <n>.
51 configured SCMI transport for instance <n>.
59 the currently configured SCMI transport for instance <n> on the
68 the currently configured SCMI transport for instance <n> on the
|
| D | debugfs-scmi-raw | 8 backend SCMI server for instance <n>.
23 backend SCMI server for instance <n>.
39 generally unexpectedly received SCMI message, for instance <n>,
50 emitted by the backend SCMI server, for instance <n>, can be
62 still pending to be read out for instance <n>, to be immediately
75 backend SCMI server for instance <n> through the <m> transport
86 channel for this instance.
99 backend SCMI server for instance <n> through the <m> transport
113 channel for this instance.
|
| /Documentation/devicetree/bindings/crypto/ |
| D | intel,ixp4xx-crypto.yaml | 28 - description: the NPE instance number
30 describing the NPE instance to be used.
37 - description: the queue instance number
39 the queue instance to be used.
46 - description: the queue instance number
48 the queue instance to be used.
|
| /Documentation/networking/ |
| D | napi.rst | 14 The host then schedules a NAPI instance to process the events.
30 of the NAPI instance while the method is the driver-specific event
39 netif_napi_add() and netif_napi_del() add/remove a NAPI instance
47 instance to be released.
60 will take ownership of the NAPI instance.
82 the NAPI instance will be serviced/polled again (without the
88 of the instance.
105 the instance (unless the instance is disabled). Similarly,
107 if napi_schedule() succeeded (e.g. if the instance gets disabled).
110 calls to the poll method only wait for the ownership of the instance
[all …]
|
| /Documentation/driver-api/media/ |
| D | v4l2-device.rst | 3 V4L2 device instance
6 Each device instance is represented by a struct v4l2_device.
10 You must register the device instance by calling:
21 that embed the struct v4l2_device instance. This is achieved by a
22 ``dev_set_drvdata()`` call before registering the V4L2 device instance.
24 properly initialized and registered :c:type:`media_device` instance.
34 name and a driver-global atomic_t instance. This will generate names like
36 a dash: ``cx18-0``, ``cx18-1``, etc. This function returns the instance number.
104 Sometimes you need to keep a running counter of the device instance. This is
105 commonly used to map a device instance to an index of a module option array.
[all …]
|
| /Documentation/devicetree/bindings/arm/omap/ |
| D | prm-inst.txt | 1 OMAP PRM instance bindings
17 - reg: Contains PRM instance register address range
21 - #power-domain-cells: Should be 0 if the instance is a power domain provider.
22 - #reset-cells: Should be 1 if the PRM instance in question supports resets.
|
| /Documentation/devicetree/bindings/iommu/ |
| D | ti,omap-iommu.txt | 9 - ti,hwmods : Name of the hwmod associated with the IOMMU instance
11 - interrupts : Interrupt specifier for the IOMMU instance
21 - ti,iommu-bus-err-back : Indicates the IOMMU instance supports throwing
25 register for enabling the MMU, and the MMU instance
28 instance number should be 0 for DSP MDMA MMUs and 1 for
|
| D | rockchip,iommu.yaml | 33 - description: configuration registers for MMU instance 0
34 - description: configuration registers for MMU instance 1
39 - description: interruption for MMU instance 0
40 - description: interruption for MMU instance 1
|
| /Documentation/driver-api/surface_aggregator/clients/ |
| D | cdev.rst | 37 interface, associated with a specific target category and device-file-instance.
39 instance, from which it can then be read.
43 notifiers work per-client (i.e. per-device-file-instance), events are enabled
50 instance is closed. Therefore any client process (or group of processes) should
54 client instance ``A``, enable those events on instance ``B`` (note that these
57 instance ``C``.
154 the device file instance. Note that events may have to be enabled, e.g. via the
157 Only one notifier can be registered per target category and client instance. If
160 Notifiers will automatically be removed when the device file instance is
170 registered for this client instance and the given category, this IOCTL will
[all …]
|
| /Documentation/core-api/ |
| D | padata.rst | 32 'name' simply identifies the instance.
53 submitted to this instance in parallel and a serial cpumask defines which
57 There may be sysfs files for an instance's cpumasks. For example, pcrypt's
58 live in /sys/kernel/pcrypt/<instance-name>. Within an instance's directory
69 cpumask.) The user-supplied cpumasks default to all possible CPUs on instance
83 Actually submitting work to the padata instance requires the creation of a
106 done; it must be in the current instance's CPU mask (if not the cb_cpu pointer
110 instance's CPU mask, while -EINVAL is a complaint about cb_cpu not being in the
112 instance.
147 Cleaning up a padata instance predictably involves calling the two free
|
| /Documentation/process/ |
| D | deprecated.rst | 284 `CONFIG_FORTIFY_SOURCE`, and `CONFIG_UBSAN_BOUNDS`). For instance,
293 struct something *instance;
295 instance = kmalloc(struct_size(instance, items, count), GFP_KERNEL);
296 instance->count = count;
298 size = sizeof(instance->items) * instance->count;
299 memcpy(instance->items, source, size);
324 struct something *instance;
326 instance = kmalloc(struct_size(instance, items, count - 1), GFP_KERNEL);
327 instance->count = count;
329 size = sizeof(instance->items) * instance->count;
[all …]
|
| /Documentation/devicetree/bindings/soc/ti/ |
| D | keystone-navigator-dma.txt | 8 CRYPTO Engines etc has its own instance of dma hardware. QMSS has also
17 |-> DMA instance #0
19 |-> DMA instance #1
23 |-> DMA instance #n
40 DMA instance properties:
97 - A phandle pointing to DMA instance node
|
| /Documentation/admin-guide/perf/ |
| D | arm-ni.rst | 7 arm_ni_<x>_cd_<y>, where <x> is an (arbitrary) instance identifier and <y> is
8 the clock domain ID within that particular instance. If multiple NI instances
10 hardware instance via sysfs parentage.
|
| /Documentation/translations/it_IT/process/ |
| D | deprecated.rst | 325 struct something *instance;
327 instance = kmalloc(struct_size(instance, items, count), GFP_KERNEL);
328 instance->count = count;
330 size = sizeof(instance->items) * instance->count;
331 memcpy(instance->items, source, size);
360 struct something *instance;
362 instance = kmalloc(struct_size(instance, items, count - 1), GFP_KERNEL);
363 instance->count = count;
365 size = sizeof(instance->items) * instance->count;
366 memcpy(instance->items, source, size);
[all …]
|
| /Documentation/translations/sp_SP/process/ |
| D | deprecated.rst | 323 struct something *instance;
325 instance = kmalloc(struct_size(instance, items, count), GFP_KERNEL);
326 instance->count = count;
328 size = sizeof(instance->items) * instance->count;
329 memcpy(instance->items, source, size);
356 struct something *instance;
358 instance = kmalloc(struct_size(instance, items, count - 1), GFP_KERNEL);
359 instance->count = count;
361 size = sizeof(instance->items) * instance->count;
362 memcpy(instance->items, source, size);
[all …]
|
| /Documentation/driver-api/hte/ |
| D | tegra-hte.rst | 17 This GTE instance timestamps GPIO in real time. For that to happen GPIO
19 instance supports timestamping GPIOs in real time as it is tightly coupled with
37 This GTE instance timestamps LIC IRQ lines in real time. The hte devicetree
42 this GTE instance in the HTE framework.
|
| /Documentation/scsi/ |
| D | scsi_mid_low_api.rst | 103 "struct scsi_host_template", an instance of which is passed to
106 struct scsi_host_template. Defining an instance of struct
242 returns a pointer to new instance of struct
246 adds 1 to the reference count of the given instance
250 instance. If the reference count reaches 0 then the given instance
258 a copy of a pointer to a scsi_device instance it should use scsi_device_get()
297 - scsi_add_device - creates new scsi device (lu) instance
302 - scsi_host_alloc - return a new scsi_host instance whose refcount==1
303 - scsi_host_get - increments Scsi_Host instance's refcount
304 - scsi_host_put - decrements Scsi_Host instance's refcount (free if 0)
[all …]
|
| /Documentation/driver-api/driver-model/ |
| D | design-patterns.rst | 40 This will create an instance of struct foo in memory every time probe() is
41 called. This is our state container for this instance of the device driver.
42 Of course it is then necessary to always pass this instance of the
62 This way you always get a pointer back to the correct instance of foo in
115 instance this way, while still keeping the number of parameters passed to the
|
| /Documentation/devicetree/bindings/phy/ |
| D | phy-tegra194-p2u.yaml | 17 A P2U instance is a glue logic between Synopsys DesignWare Core PCIe IP's PIPE
18 interface and PHY of HSIO/NVHS/GBE bricks. Each P2U instance represents one
29 description: Should be the physical address space and length of respective each P2U instance.
|
12345678910>>...24