Searched full:handle (Results 1 – 25 of 581) sorted by relevance
12345678910>>...24
| /Documentation/media/kapi/ |
| D | v4l2-fh.rst | 6 struct :c:type:`v4l2_fh` provides a way to easily keep file handle specific
19 struct :c:type:`v4l2_fh` is allocated as a part of the driver's own file handle
29 Drivers can extract their own file handle structure by using the container_of
82 - Initialise the file handle. This **MUST** be performed in the driver's
89 - Add a :c:type:`v4l2_fh` to :c:type:`video_device` file handle list.
90 Must be called once the file handle is completely initialized.
95 - Unassociate the file handle from :c:type:`video_device`. The file handle
101 - Uninitialise the file handle. After uninitialisation the :c:type:`v4l2_fh`
122 Several drivers need to do something when the first file handle is opened and
123 when the last file handle closes. Two helper functions were added to check
[all …]
|
| /Documentation/crypto/ |
| D | intro.rst | 19 Therefore, a cipher handle variable usually has the name "tfm". Besides
56 to as a "cipher handle". Such a cipher handle is always subject to the
58 a cipher handle:
60 1. Initialization of a cipher handle.
62 2. Execution of all intended cipher operations applicable for the handle
63 where the cipher handle must be furnished to every API call.
65 3. Destruction of a cipher handle.
67 When using the initialization API calls, a cipher handle is created and
|
| D | api-skcipher.rst | 19 Symmetric Key Cipher Request Handle
23 :doc: Symmetric Key Cipher Request Handle
46 Asynchronous Cipher Request Handle - Deprecated
50 :doc: Asynchronous Cipher Request Handle
|
| D | architecture.rst | 76 must ensure it can handle such asynchronous events by applying
108 initialization of a cipher handle, the kernel crypto API looks up all
178 When allocating a cipher handle, the caller only specifies the cipher
188 The different cipher handle allocation functions allow the specification
333 cipher handle for GCM is provided to SEQIV. This means that SEQIV
334 invokes AEAD cipher operations with the GCM cipher handle.
336 During instantiation of the GCM handle, the CTR(AES) and GHASH
345 with the instantiated CTR(AES) cipher handle.
348 implementation of AES is instantiated. The cipher handle for AES is
356 cipher handle to encrypt one block.
[all …]
|
| /Documentation/devicetree/bindings/net/ |
| D | hisilicon-hip04-net.txt | 9 - port-handle: <phandle port channel>
17 - phy-handle: see ethernet.txt [1].
70 port-handle = <&ppe 31 0 31>;
78 port-handle = <&ppe 0 1 0>;
79 phy-handle = <&phy0>;
87 port-handle = <&ppe 8 2 8>;
88 phy-handle = <&phy1>;
|
| D | hisilicon-hns-dsaf.txt | 26 - phy-handle: phy handle of physical port, 0 if not any phy device. It is optional
27 attribute. If port node exists, phy-handle in each port node will be used.
29 - subctrl-syscon: is syscon handle for external interface control register.
38 - phy-handle: phy handle of physical port. It is not required if there isn't
40 - serdes-syscon: is syscon handle for SerDes register.
41 - cpld-syscon: is syscon handle + register offset pair for cpld register. It is
80 phy-handle = <&phy0>;
|
| D | qualcomm-bluetooth.txt | 24 - vddio-supply: VDD_IO supply regulator handle.
25 - vddxo-supply: VDD_XO supply regulator handle.
26 - vddrf-supply: VDD_RF supply regulator handle.
27 - vddch0-supply: VDD_CH0 supply regulator handle.
|
| D | cavium-pip.txt | 38 - phy-handle: Optional, see ethernet.txt file in the same directory.
64 phy-handle = <&phy2>;
70 phy-handle = <&phy3>;
76 phy-handle = <&phy4>;
82 phy-handle = <&phy5>;
96 phy-handle = <&phy6>;
|
| D | nixge.txt | 21 Use instead of phy-handle.
22 - phy-handle: See ethernet.txt file in the same directory.
39 phy-handle = <ðernet_phy1>;
62 phy-handle = <ðernet_phy1>;
|
| D | cortina,gemini-ethernet.txt | 34 - clocks: this should contain a handle to the PCLK clock for
40 - phy-handle: see ethernet.txt
77 phy-handle = <&phy0>;
90 phy-handle = <&phy1>;
|
| /Documentation/admin-guide/cgroup-v1/ |
| D | net_cls.rst | 17 values is 0xAAAABBBB; AAAA is the major handle number and BBBB
18 is the minor handle number.
28 - setting a 10:1 handle::
35 tc qdisc add dev eth0 root handle 10: htb
40 tc filter add dev eth0 parent 10: protocol ip prio 10 handle 1: cgroup
|
| /Documentation/devicetree/bindings/soc/fsl/ |
| D | qman-portals.txt | 78 - dev-handle
103 dev-handle = <&fman0>;
107 dev-handle = <&fman1>;
111 dev-handle = <&crypto>;
123 dev-handle = <&fman0>;
127 dev-handle = <&fman1>;
131 dev-handle = <&crypto>;
|
| /Documentation/filesystems/ |
| D | overlayfs.txt | 182 handle it in two different ways:
230 indexed by the file handle of the lower inode and a file handle of the
233 directory does not match the file handle stores in the index, that is an
339 handle of the lower layer root directory, along with the UUID of the lower
342 the lower root directory file handle and lower filesystem UUID are compared
356 the copied layers will fail the verification of the lower root file handle.
365 This is the list of cases that overlayfs doesn't currently handle:
425 On every copy_up, an NFS file handle of the lower inode, along with the
432 that the found lower directory file handle and lower filesystem UUID
433 match the origin file handle that was stored at copy_up time. If a
[all …]
|
| /Documentation/power/ |
| D | pm_qos_interface.rst | 42 void pm_qos_add_request(handle, param_class, target_value):
46 Clients of pm_qos need to save the returned handle for future use in other
49 void pm_qos_update_request(handle, new_target_value):
50 Will update the list element pointed to by the handle with the new target value
54 void pm_qos_remove_request(handle):
62 int pm_qos_request_active(handle):
114 int dev_pm_qos_add_request(device, handle, type, value):
118 Clients of dev_pm_qos need to save the handle for future use in other
121 int dev_pm_qos_update_request(handle, new_value):
122 Will update the list element pointed to by the handle with the new target
[all …]
|
| /Documentation/devicetree/bindings/net/dsa/ |
| D | realtek-smi.txt | 36 a GPIO) that will demultiplex and handle the interrupt from the single
88 phy-handle = <&phy0>;
93 phy-handle = <&phy1>;
98 phy-handle = <&phy2>;
103 phy-handle = <&phy3>;
108 phy-handle = <&phy4>;
|
| D | lantiq-gswip.txt | 62 phy-handle = <&phy0>;
69 phy-handle = <&phy1>;
76 phy-handle = <&phy11>;
83 phy-handle = <&phy13>;
90 phy-handle = <&phy5>;
|
| D | qca8k.txt | 93 phy-handle = <&phy_port1>;
99 phy-handle = <&phy_port2>;
105 phy-handle = <&phy_port3>;
111 phy-handle = <&phy_port4>;
117 phy-handle = <&phy_port5>;
|
| /Documentation/devicetree/bindings/input/ |
| D | gpio-mouse.txt | 15 - button-left-gpios: GPIO line handle to the left mouse button
16 - button-middle-gpios: GPIO line handle to the middle mouse button
17 - button-right-gpios: GPIO line handle to the right mouse button
|
| /Documentation/ABI/testing/ |
| D | sysfs-firmware-dmi-entries | 18 'handle' that is supposed to be unique amongst all
28 to handle these duplicate entry types, each entry is
53 handle : The 16bit 'handle' that is assigned to this
54 entry by the firmware. This handle may be
|
| D | sysfs-driver-hid-multitouch | 5 quirks actually in place to handle the device's protocol.
9 the protocol to handle the device.
|
| /Documentation/ |
| D | remoteproc.txt | 46 handle. There are several ways to achieve that cleanly (devres, pdata,
65 which means that the @rproc handle stays valid even after
73 Find an rproc handle using a device tree phandle. Returns the rproc
74 handle on success, and NULL on failure. This function increments
85 /* in case we were given a valid 'rproc' handle */
94 * something went wrong. handle it and leave.
115 Allocate a new remote processor handle, but don't register
124 After creating an rproc handle using this function, and when ready,
139 Free an rproc handle that was allocated by rproc_alloc.
214 The ->start() handler takes an rproc handle and should then power on the
[all …]
|
| /Documentation/devicetree/bindings/powerpc/fsl/ |
| D | cache_sram.txt | 11 - fsl,cache-sram-ctlr-handle : points to the L2 controller
17 fsl,cache-sram-ctlr-handle = <&L2>;
|
| /Documentation/devicetree/bindings/soc/fsl/cpm_qe/qe/ |
| D | ucc.txt | 14 - pio-handle : The phandle for the Parallel I/O port configuration.
46 - phy-handle : The phandle for the PHY connected to this controller.
65 phy-handle = <212000>;
67 pio-handle = <140001>;
|
| /Documentation/devicetree/bindings/display/ti/ |
| D | ti,dra7-dss.txt | 14 - clocks: handle to fclk
25 - clocks: handle to video1 pll clock and video2 pll clock
47 - clocks: handle to fclk
|
| /Documentation/devicetree/bindings/media/ |
| D | tegra-cec.txt | 4 handle communication between HDMI connected devices over the CEC bus.
14 - clocks : from common clock binding: handle to HDMI CEC clock.
|
12345678910>>...24