Searched full:instance (Results 1 – 25 of 445) sorted by relevance
12345678910>>...18
| /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/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/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
|
| /Documentation/process/ |
| D | deprecated.rst | 278 `CONFIG_FORTIFY_SOURCE`, and `CONFIG_UBSAN_BOUNDS`). For instance,
287 struct something *instance;
289 instance = kmalloc(struct_size(instance, items, count), GFP_KERNEL);
290 instance->count = count;
292 size = sizeof(instance->items) * instance->count;
293 memcpy(instance->items, source, size);
318 struct something *instance;
320 instance = kmalloc(struct_size(instance, items, count - 1), GFP_KERNEL);
321 instance->count = count;
323 size = sizeof(instance->items) * instance->count;
[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/devicetree/bindings/phy/ |
| D | phy-tegra194-p2u.txt | 5 A P2U instance is a glue logic between Synopsys DesignWare Core PCIe IP's PIPE
6 interface and PHY of HSIO/NVHS bricks. Each P2U instance represents one PCIe
12 instance.
|
| /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/devicetree/bindings/clock/ |
| D | qcom,mmcc.yaml | 33 - description: DSI phy instance 0 dsi clock
34 - description: DSI phy instance 0 byte clock
35 - description: DSI phy instance 1 dsi clock
36 - description: DSI phy instance 1 byte clock
|
| /Documentation/devicetree/bindings/mailbox/ |
| D | sti-mailbox.txt | 14 <&phandle instance channel direction>
16 instance : Instance number
|
| /Documentation/devicetree/bindings/spi/ |
| D | brcm,spi-bcm-qspi.txt | 11 Supported Broadcom SoCs have one instance of MSPI+BSPI controller IP.
12 MSPI master can be used wihout BSPI. BRCMSTB SoCs have an additional instance
27 "brcm,spi-brcmstb-mspi", "brcm,spi-bcm-qspi" : Second Instance of MSPI
29 "brcm,spi-bcm7425-qspi", "brcm,spi-bcm-qspi", "brcm,spi-brcmstb-mspi" : Second Instance of MSPI
31 "brcm,spi-bcm7429-qspi", "brcm,spi-bcm-qspi", "brcm,spi-brcmstb-mspi" : Second Instance of MSPI
33 "brcm,spi-bcm7435-qspi", "brcm,spi-bcm-qspi", "brcm,spi-brcmstb-mspi" : Second Instance of MSPI
35 "brcm,spi-bcm7445-qspi", "brcm,spi-bcm-qspi", "brcm,spi-brcmstb-mspi" : Second Instance of MSPI
37 "brcm,spi-bcm7216-qspi", "brcm,spi-bcm-qspi", "brcm,spi-brcmstb-mspi" : Second Instance of MSPI
39 "brcm,spi-bcm7278-qspi", "brcm,spi-bcm-qspi", "brcm,spi-brcmstb-mspi" : Second Instance of MSPI
|
| /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/filesystems/ |
| D | devpts.rst | 15 created with ``mknod name c 5 2``) when opened will look for an instance
31 Per-instance limit could be set by adding mount option ``max=<count>``.
36 In kernels older than 3.4 sysctl ``kernel.pty.max`` works as per-instance limit.
|
| D | tmpfs.rst | 11 created on your hard drive. If you unmount a tmpfs instance,
66 size The limit of allocated bytes for this tmpfs instance. The
71 nr_inodes The maximum number of inodes for this instance. The default
79 to limit this tmpfs instance to that percentage of your physical RAM:
82 If nr_blocks=0 (or size=0), blocks will not be limited in that instance;
86 that instance in a system with many cpus making intensive use of it.
90 all files in that instance (if CONFIG_NUMA is enabled) - which can be
170 will give you tmpfs instance on /mytmpfs which can allocate 10GB
|
| /Documentation/driver-api/soundwire/ |
| D | locking.rst | 17 (sdw_bus) which is used for every Bus instance. This lock is used to
18 serialize each of the following operations(s) within SoundWire Bus instance.
31 transfers (read/write) within a SoundWire Bus instance.
72 1. Acquire lock for Bus instance associated with Master 1.
83 3. Release lock for Bus instance associated with Master 1 ::
|
| /Documentation/devicetree/bindings/memory-controllers/ti/ |
| D | emif.txt | 5 DDR2/DDR3/LPDDR2 protocols. This binding describes a given instance
12 is the IP revision of the specific EMIF instance. For newer controllers,
28 instance with base 1.
40 instance has a memory part attached to it. If there is a memory
|
| /Documentation/networking/ |
| D | ppp_generic.rst | 63 system call on an instance of /dev/ppp which is bound to the
91 will need it to attach an instance of /dev/ppp to this channel.
127 The channel must provide an instance of a ppp_channel struct to
255 channels. Although there is only one /dev/ppp, each open instance of
258 to point to a separate object for each open instance of /dev/ppp. In
263 When /dev/ppp is opened, a new instance is created which is initially
266 existing channel. An instance attached to a unit can be used to send
268 calls, along with poll() if necessary. Similarly, an instance
274 write to the unit (i.e., to an instance of /dev/ppp attached to the
285 The ioctl calls which are available on an instance of /dev/ppp depend
[all …]
|
| /Documentation/devicetree/bindings/slimbus/ |
| D | bus.txt | 13 Manufacturer ID, Product code, Device index, and Instance value for
24 - reg - Should be ('Device index', 'Instance ID') from SLIMbus
28 Instance ID Is for the cases where multiple Devices of the
|
| D | slim-ngd-qcom-ctrl.txt | 41 Definition: Should be 1, reflecting the instance id of ngd.
49 Each subnode represents an instance of NGD, must contain the following
55 Definition: Should be instance id of ngd.
|
| /Documentation/usb/ |
| D | raw-gadget.rst | 38 To create a Raw Gadget instance open /dev/raw-gadget. Multiple raw-gadget
45 1. Open Raw Gadget instance via /dev/raw-gadget.
46 2. Initialize the instance via USB_RAW_IOCTL_INIT.
47 3. Launch the instance with USB_RAW_IOCTL_RUN.
|
| /Documentation/devicetree/bindings/soc/fsl/ |
| D | bman.txt | 42 Definition: Phandle to this BMan instance's portals
56 Devices connected to a BMan instance via Direct Connect Portals (DCP) must link
57 to the respective BMan instance
62 Description: List of phandle and DCP index pairs, to the BMan instance
|
| /Documentation/devicetree/bindings/thermal/ |
| D | exynos-thermal.txt | 19 belongs to register set of TMU instance and second set belongs to
20 registers shared with the TMU instance.
97 Note: For multi-instance tmu each instance should have an alias correctly
|
| /Documentation/devicetree/bindings/power/ |
| D | ti-smartreflex.txt | 15 reg: Shall contain the device instance IO range
17 interrupts: Shall contain the device instance interrupt
|
12345678910>>...18