Searched full:using (Results 1 – 25 of 1671) sorted by relevance
12345678910>>...67
| /Documentation/devicetree/bindings/sound/ |
| D | rt5659.txt | 25 1: using IN2N pin as dmic1 data pin
26 2: using GPIO5 pin as dmic1 data pin
27 3: using GPIO9 pin as dmic1 data pin
28 4: using GPIO11 pin as dmic1 data pin
32 1: using IN2P pin as dmic2 data pin
33 2: using GPIO6 pin as dmic2 data pin
34 3: using GPIO10 pin as dmic2 data pin
35 4: using GPIO12 pin as dmic2 data pin
39 1: using JD3 as JD source
|
| D | rt5645.txt | 24 1: using IN2P pin as dmic1 data pin
25 2: using GPIO6 pin as dmic1 data pin
26 3: using GPIO10 pin as dmic1 data pin
27 4: using GPIO12 pin as dmic1 data pin
31 1: using IN2N pin as dmic2 data pin
32 2: using GPIO5 pin as dmic2 data pin
33 3: using GPIO11 pin as dmic2 data pin
|
| D | rt5682.txt | 17 1: using GPIO2 pin as dmic1 data pin
18 2: using GPIO5 pin as dmic1 data pin
21 0: using GPIO1 pin as dmic1 clock pin
22 1: using GPIO3 pin as dmic1 clock pin
26 1: using JD1 as JD source
|
| D | rt5668.txt | 17 1: using GPIO2 pin as dmic1 data pin
18 2: using GPIO5 pin as dmic1 data pin
21 0: using GPIO1 pin as dmic1 clock pin
22 1: using GPIO3 pin as dmic1 clock pin
26 1: using JD1 as JD source
|
| D | rt5665.txt | 23 1: using GPIO4 pin as dmic1 data pin
24 2: using IN2N pin as dmic2 data pin
28 1: using GPIO5 pin as dmic2 data pin
29 2: using IN2P pin as dmic2 data pin
33 1: using JD1 as JD source
|
| D | rt5640.txt | 27 1: using IN1P pin as dmic1 data pin
28 2: using GPIO3 pin as dmic1 data pin
32 1: using IN1N pin as dmic2 data pin
33 2: using GPIO4 pin as dmic2 data pin
|
| /Documentation/filesystems/nfs/ |
| D | nfsroot.txt | 43 This can be established using the following kernel command line parameters:
93 this means that the kernel tries to configure everything using
104 Default: Determined using autoconfiguration.
117 Default: Determined using autoconfiguration.
122 Default: Determined using autoconfiguration.
128 Default: Determined using autoconfiguration.
143 Otherwise the device is determined using
146 and using the device that received the first reply.
150 requests are sent using all protocols, and the first one
176 Default: None if not using autoconfiguration; determined
[all …]
|
| /Documentation/driver-api/dmaengine/ |
| D | dmatest.rst | 7 This small document introduces how to test DMA drivers using dmatest module.
72 Once started a message like " dmatest: Added 1 threads using dma0chan0" is
154 Channels are registered using the "channel" parameter. Channels can be requested by their
160 dmatest: Added 1 threads using dma0chan2
168 dmatest: Added 1 threads using dma0chan1
170 dmatest: Added 1 threads using dma0chan2
180 dmatest: Added 1 threads using dma0chan0
181 dmatest: Added 1 threads using dma0chan3
182 dmatest: Added 1 threads using dma0chan4
183 dmatest: Added 1 threads using dma0chan5
[all …]
|
| /Documentation/driver-api/gpio/ |
| D | drivers-on-gpio.rst | 2 Subsystem drivers using GPIO
7 drivers can quite easily interconnect with other kernel subsystems using
25 up to three buttons by simply using GPIOs and no mouse port. You can cut the
54 of wires, at least SCK and optionally MISO, MOSI and chip select lines) using
58 to this SPI by using the mmc_spi host from the MMC/SD card subsystem.
60 - w1-gpio: drivers/w1/masters/w1-gpio.c is used to drive a one-wire bus using
89 Consumer Electronics Control bus using only GPIO. It is used to communicate
94 to emulate MCTRL (modem control) signals CTS/RTS by using two GPIO lines. The
98 Use those instead of talking directly to the GPIOs using sysfs; they integrate
100 just using the appropriate kernel drivers will simplify and speed up your
|
| /Documentation/media/uapi/v4l/ |
| D | selection-api-configuration.rst | 26 control the rounding behaviour using
57 coordinates are obtained using ``V4L2_SEL_TGT_COMPOSE_BOUNDS``. All
69 control rounding behaviour using
72 For capture devices the default composing rectangle is queried using
77 ``V4L2_SEL_TGT_COMPOSE_PADDED``. It contains all pixels defined using
97 cropping coordinates are obtained using ``V4L2_SEL_TGT_CROP_BOUNDS``.
100 specified using :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl.
110 For output devices the default cropping rectangle is queried using
141 and the height of rectangles obtained using ``V4L2_SEL_TGT_CROP`` and
143 scaling is applied. The application can compute the scaling ratios using
|
| D | dev-event.rst | 23 subscribed using the
26 using the :ref:`VIDIOC_DQEVENT` ioctl. Events may be
27 unsubscribed using VIDIOC_UNSUBSCRIBE_EVENT ioctl. The special event
35 The information on dequeueable events is obtained by using select or
|
| /Documentation/core-api/ |
| D | xarray.rst | 22 clustered; hashing the object and using the hash as the index will not
39 You must first convert it into an entry using xa_mk_value().
44 Some users want to store tagged pointers instead of using the marks
72 You can then set entries using xa_store() and get entries
73 using xa_load(). xa_store will overwrite any entry with the
80 You can conditionally replace an entry at an index by using
90 You can enquire whether a mark is set on an entry by using
92 on it by using xa_set_mark() and remove the mark from an entry by
117 Using xa_insert() on a reserved entry will fail.
125 entries in the XArray using the xa_for_each() iterator.
[all …]
|
| /Documentation/networking/ |
| D | batman-adv.rst | 9 using UDP packets and sets routing tables, batman-advanced operates on ISO/OSI
30 batman-adv can operate. The batman-adv soft-interface can be created using the
40 using/broadcasting on this/these interface(s).
46 The same can also be done using the batctl interface subcommand::
57 which can be modified using batctl. Detailed information about this can be found
86 you. Basically, one "hands over" the data by using the batman interface and
90 IP address which can be either statically configured or dynamically (by using
111 a number of ways. Try using the commands: ``dmesg``, ``logread``, or looking in
123 Those additional debug messages can be accessed using the perf infrastructure::
|
| D | l2tp.txt | 49 Each L2TP tunnel is implemented using a UDP or L2TPIP socket; L2TPIP
50 provides L2TPv3 IP encapsulation (no UDP) and is implemented using a
55 indirectly by pppd using a pppol2tp socket. In the case of ethernet,
69 pseudowire. These interfaces can be managed using standard Linux tools
73 can be added to a bridge using brctl. All L2TP datapath protocol
120 Userspace may control behavior of the tunnel or session using
137 to retrieve tunnel and session statistics from the kernel using the
144 1. Open a GENL socket using L2TP_GENL_NAME for configuring the kernel
145 using netlink.
149 3. Create a new L2TP tunnel using a L2TP_CMD_TUNNEL_CREATE
[all …]
|
| /Documentation/PCI/endpoint/ |
| D | pci-endpoint.rst | 6 endpoint controller driver, endpoint function driver, and using configfs
63 devm_pci_epc_create() or pci_epc_create() using devm_pci_epc_destroy() or
97 using this API.
118 free the memory space allocated using pci_epc_mem_alloc_addr().
125 using these APIs.
134 Release the reference to the PCI endpoint controller obtained using
178 The PCI Function driver can then register the PCI EPF driver by using
183 The PCI Function driver can unregister the PCI EPF driver by using
188 The PCI Function driver can allocate space for a particular BAR using
194 (using pci_epf_alloc_space) by invoking pci_epf_free_space().
[all …]
|
| /Documentation/dev-tools/ |
| D | kgdb.rst | 2 Using kgdb, kdb and the kernel debugger internals
33 Two machines are required for using kgdb. One of these machines is a
71 If the architecture that you are using supports the kernel option
75 supports it for the architecture you are using, you can use hardware
106 ``CONFIG_KGDB_SERIAL_CONSOLE`` interface if you plan on using kdb on a
129 using kdb and kgdb as well as providing some examples of the
142 console as your primary console as well as using it to perform kernel
174 depending on if you are using kdb and/or kgdb, in one of the following
176 optional configurations together. Using kms + only gdb is generally not
179 Using loadable module or built-in
[all …]
|
| /Documentation/security/keys/ |
| D | ecryptfs.rst | 6 file using a randomly generated File Encryption Key (FEK).
11 using a key, the FEKEK, derived from a user prompted passphrase; in the latter
33 The eCryptfs filesystem may really benefit from using encrypted keys in that the
56 'ecryptfs' and save it using a previously loaded user key "test"::
69 Mount an eCryptfs filesystem using the created encrypted key "1000100010001000"
|
| /Documentation/driver-api/usb/ |
| D | typec_bus.rst | 8 Alternate modes require communication with the partner using Vendor Defined
14 modes by using the SVID and the mode number.
25 driver will happen using the same API.
49 the SVID specific commands to each other using :c:func:`typec_altmode_vdm()`.
51 If the communication with the partner using the SVID specific commands results
53 needs to notify the bus using :c:func:`typec_altmode_notify()`. The driver
55 parameter. The bus driver will then configure the mux behind the connector using
103 plug alternate modes using :c:func:`typec_altmode_get_plug()`, and take over
|
| /Documentation/hid/ |
| D | hidraw.rst | 19 communication with these non-conformant devices is impossible using hiddev.
44 devices, the reports read using read() are the reports sent from the device
47 the O_NONBLOCK flag to open(), or by setting the O_NONBLOCK flag using
60 using a SET_REPORT transfer.
78 This ioctl returns the device's report descriptor using a
114 specification, feature reports are always sent using the control endpoint.
123 This ioctl will request a feature report from the device using the control
133 purpose, and can serve as a starting point for developing applications using
|
| /Documentation/devicetree/bindings/net/ |
| D | marvell-pxa168.txt | 11 - #address-cells: must be 1 when using sub-nodes.
12 - #size-cells: must be 0 when using sub-nodes.
15 The MAC address will be determined using the optional properties
|
| /Documentation/devicetree/bindings/input/ |
| D | da9062-onkey.txt | 18 - dlg,disable-key-power : Disable power-down using a long key-press. If this
20 press when triggered using a long press of the OnKey.
40 Example: DA9061 using a fall-back compatible for the DA9062 onkey driver
|
| /Documentation/ABI/testing/ |
| D | debugfs-pfo-nx-crypto | 29 - The total number of bytes encrypted using AES in any of the driver's
36 - The total number of bytes hashed by the hardware using SHA-256.
42 - The total number of bytes hashed by the hardware using SHA-512.
|
| /Documentation/media/v4l-drivers/ |
| D | si470x.rst | 78 for frequency seeking, either by using hardware functionality as in radio-si470x
93 listing you have to redirect the sound, for example using one of the following
108 or using sox + alsa:
133 (0444) are not updated, even if space, band and de are changed using private
154 for it can be implemented using the request_firmware interface.
156 There is a RDS interrupt mode. The driver is already using the same interface
157 for polling RDS information, but is currently not using the interrupt mode.
160 programmed in the firmware. This can be made available using the LED support
|
| /Documentation/driver-api/mei/ |
| D | iamt.rst | 42 local application using the same network interface as a remote application
55 The Intel LMS opens a connection using the Intel MEI driver to the Intel LMS
56 firmware feature using a defined GUID and then communicates with the feature
57 using a protocol called Intel AMT Port Forwarding Protocol (Intel APF protocol).
67 2) Intel AMT Remote configuration using a Local Agent
77 "Using the Local Agent Sample"
|
| /Documentation/admin-guide/device-mapper/ |
| D | dm-crypt.rst | 6 using the kernel crypto API.
112 Perform encryption using the same cpu that IO was submitted on.
121 thread because it benefits CFQ to have writes submitted using the
153 encryption with dm-crypt using the 'cryptsetup' utility, see
159 # Create a crypt device using dmsetup
165 # Create a crypt device using dmsetup when encryption key is stored in keyring service
171 # Create a crypt device using cryptsetup and LUKS header with default cipher
|
12345678910>>...67