Searched full:using (Results 1 – 25 of 2039) sorted by relevance
12345678910>>...82
| /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
50 the Codec, the connectivity can be described using 'ports' property.
|
| D | rt5645.txt | 33 1: using IN2P pin as dmic1 data pin
34 2: using GPIO6 pin as dmic1 data pin
35 3: using GPIO10 pin as dmic1 data pin
36 4: using GPIO12 pin as dmic1 data pin
40 1: using IN2N pin as dmic2 data pin
41 2: using GPIO5 pin as dmic2 data pin
42 3: using GPIO11 pin as dmic2 data pin
|
| 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 | rt5682.txt | 32 1: using GPIO2 pin as dmic1 data pin
33 2: using GPIO5 pin as dmic1 data pin
36 0: using GPIO1 pin as dmic1 clock pin
37 1: using GPIO3 pin as dmic1 clock pin
41 1: using JD1 as JD source
|
| /Documentation/admin-guide/nfs/ |
| D | nfsroot.rst | 50 This can be established using the following kernel command line parameters:
97 this means that the kernel tries to configure everything using
107 Default: Determined using autoconfiguration.
121 Default: Determined using autoconfiguration.
125 Default: Determined using autoconfiguration.
131 Default: Determined using autoconfiguration.
146 Otherwise the device is determined using
149 and using the device that received the first reply.
154 requests are sent using all protocols, and the first one
180 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.
9 The dmatest module tests DMA memcpy, memset, XOR and RAID6 P+Q operations using
82 Once started a message like " dmatest: Added 1 threads using dma0chan0" is
165 Channels are registered using the "channel" parameter. Channels can be requested by their
171 dmatest: Added 1 threads using dma0chan2
179 dmatest: Added 1 threads using dma0chan1
181 dmatest: Added 1 threads using dma0chan2
191 dmatest: Added 1 threads using dma0chan0
192 dmatest: Added 1 threads using dma0chan3
193 dmatest: Added 1 threads using dma0chan4
[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 AC charger or more complex tasks such as indicating charging status using
99 - gpio-mux: drivers/mux/gpio.c is used for controlling a multiplexer using
107 to emulate MCTRL (modem control) signals CTS/RTS by using two GPIO lines. The
[all …]
|
| D | using-gpio.rst | 2 Using GPIO Lines in Linux
16 using appropriate kernel drivers is paramount. Submit your code for inclusion
33 from userspace will likely be a good fit for using GPIO lines from userspace as
38 productify the prototype: rewrite it using proper kernel drivers. Do not under
39 any circumstances deploy any uniform products using GPIO from userspace.
|
| /Documentation/userspace-api/media/v4l/ |
| D | selection-api-configuration.rst | 19 control the rounding behaviour using
50 coordinates are obtained using ``V4L2_SEL_TGT_COMPOSE_BOUNDS``. All
62 control rounding behaviour using
65 For capture devices the default composing rectangle is queried using
70 ``V4L2_SEL_TGT_COMPOSE_PADDED``. It contains all pixels defined using
90 cropping coordinates are obtained using ``V4L2_SEL_TGT_CROP_BOUNDS``.
93 specified using :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl.
103 For output devices the default cropping rectangle is queried using
134 and the height of rectangles obtained using ``V4L2_SEL_TGT_CROP`` and
136 scaling is applied. The application can compute the scaling ratios using
|
| D | dev-event.rst | 16 subscribed using the
19 using the :ref:`VIDIOC_DQEVENT` ioctl. Events may be
20 unsubscribed using VIDIOC_UNSUBSCRIBE_EVENT ioctl. The special event
28 The information on dequeueable events is obtained by using select or
|
| /Documentation/hid/ |
| D | hidraw.rst | 19 communication with these non-conformant devices is impossible using hiddev.
45 devices, the reports read using read() are the reports sent from the device
48 the O_NONBLOCK flag to open(), or by setting the O_NONBLOCK flag using
61 using a SET_REPORT transfer.
79 This ioctl returns the device's report descriptor using a
115 specification, feature reports are always sent using the control endpoint.
124 This ioctl will request a feature report from the device using the control
135 This ioctl will send an input report to the device, using the control endpoint.
144 This ioctl will request an input report from the device using the control
155 This ioctl will send an output report to the device, using the control endpoint.
[all …]
|
| /Documentation/core-api/ |
| D | xarray.rst | 22 clustered; hashing the object and using the hash as the index will not
35 You must first convert it into an entry using xa_mk_value().
66 You can then set entries using xa_store() and get entries
67 using xa_load(). xa_store will overwrite any entry with the
74 You can conditionally replace an entry at an index by using
105 Using xa_insert() on a reserved entry will fail.
113 entries in the XArray using the xa_for_each() iterator.
120 iterate over marked entries by using the xa_for_each_marked() iterator.
122 You can enquire whether a mark is set on an entry by using
124 by using xa_set_mark() and remove the mark from an entry by calling
[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::
|
| /Documentation/ABI/testing/ |
| D | sysfs-class-fc_host | 6 events recorded by the F_Port, reported using fabric
14 events recorded by the F_Port/Nx_Port, reported using fabric
22 recorded by the F_Port/Nx_Port, reported using fabric
|
| D | sysfs-class-fc_remote_ports | 6 events recorded by the F_Port/Nx_Port, reported using fabric
14 events recorded by the F_Port/Nx_Port, reported using fabric
22 recorded by the F_Port/Nx_Port, reported using fabric
|
| D | sysfs-driver-intc_sar | 11 the current SAR regulatory mode on the Dynamic SAR driver using
12 this sysfs node. Such an application can also read back using
44 level using the Band/Antenna/SAR table index information.
52 using POLLPRI event on file-descriptor (fd) obtained by opening
|
| /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/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
88 plug alternate modes using :c:func:`typec_altmode_get_plug()`, and take over
|
| /Documentation/bpf/ |
| D | prog_lsm.rst | 10 policies using eBPF.
57 The eBPF programs can be declared using the``BPF_PROG``
90 the BPF verifier to update the offsets for the access at runtime using the
108 This can be simplified by using a skeleton header generated by ``bpftool``:
114 and the program can be loaded by including ``my_prog.skel.h`` and using
120 The LSM allows attachment of eBPF programs as LSM hooks using :manpage:`bpf(2)`
122 using the libbpf helper ``bpf_program__attach_lsm``.
125 link returned by ``bpf_program__attach_lsm`` using ``bpf_link__destroy``.
|
| D | s390.rst | 77 The disk image can be prepared using a loopback mount and debootstrap::
117 simplify debugging, can be done using the following commands::
146 When using this on a real IBM Z, ``-enable-kvm`` may be added for better
148 setup must be finalized using the following command::
160 After that, the test suite can be run using the following commands::
173 It is possible to debug the s390 kernel using QEMU GDB stub, which is activated
181 GDB can then be attached using the following command::
189 install additional packages, it can be configured using::
205 - `Using GDB with QEMU <https://wiki.osdev.org/Kernel_Debugging#Use_GDB_with_QEMU>`_
|
| /Documentation/driver-api/tty/ |
| D | n_gsm.rst | 25 #. Switch the serial line to using the n_gsm line discipline by using
28 #. Configure the mux using ``GSMIOC_GETCONF_EXT``/``GSMIOC_SETCONF_EXT`` ioctl if needed.
30 #. Configure the mux using ``GSMIOC_GETCONF``/``GSMIOC_SETCONF`` ioctl.
32 #. Configure DLCs using ``GSMIOC_GETCONF_DLCI``/``GSMIOC_SETCONF_DLCI`` ioctl for non-defaults.
125 #. Switch the serial line to using the *n_gsm* line discipline by using
128 #. Configure the mux using ``GSMIOC_GETCONF_EXT``/``GSMIOC_SETCONF_EXT``
131 #. Configure the mux using ``GSMIOC_GETCONF``/``GSMIOC_SETCONF`` ioctl.
133 #. Configure DLCs using ``GSMIOC_GETCONF_DLCI``/``GSMIOC_SETCONF_DLCI`` ioctl for non-defaults.
|
| /Documentation/admin-guide/gpio/ |
| D | gpio-aggregator.rst | 10 Aggregating GPIOs using Sysfs
13 GPIO controllers are exported to userspace using /dev/gpiochip* character
20 using standard UNIX file ownership and permissions. Furthermore, this
33 aggregate to the "new_device" file, using the format
83 Example: If "door" is a GPIO-operated device described in DT, using its own
97 2. Binding manually using "driver_override":
|
| /Documentation/misc-devices/ |
| D | xilinx_sdfec.rst | 128 Determine the configuration of the SD-FEC core by using the ioctl
136 Setting the order is done by using the ioctl :c:macro:`XSDFEC_SET_ORDER`
151 - Add the LPDC Code Parameters using the ioctl :c:macro:`XSDFEC_ADD_LDPC_CODE_PARAMS`
164 Configuring the Turbo decode parameters is done by using the ioctl :c:macro:`XSDFEC_SET_TURBO` usin…
174 Enabling or disabling interrupts is done by using the ioctl :c:macro:`XSDFEC_SET_IRQ`. The members …
184 Bypassing the SD-FEC is done by using the ioctl :c:macro:`XSDFEC_SET_BYPASS`
193 Start the SD-FEC core by using the ioctl :c:macro:`XSDFEC_START_DEV`
198 Get the SD-FEC status of the device by using the ioctl :c:macro:`XSDFEC_GET_STATUS`, which will fil…
207 - Get stats by using the ioctl :c:macro:`XSDFEC_GET_STATS`
210 - Get state by using the ioctl :c:macro:`XSDFEC_GET_STATUS`
[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
70 If the architecture that you are using supports the kernel option
74 supports it for the architecture you are using, you can use hardware
105 ``CONFIG_KGDB_SERIAL_CONSOLE`` interface if you plan on using kdb on a
128 using kdb and kgdb as well as providing some examples of the
141 console as your primary console as well as using it to perform kernel
173 depending on if you are using kdb and/or kgdb, in one of the following
175 optional configurations together. Using kms + only gdb is generally not
178 Using loadable module or built-in
[all …]
|
12345678910>>...82