Searched full:setup (Results 1 – 25 of 334) sorted by relevance
12345678910>>...14
| /Documentation/sound/hd-audio/ |
| D | models.rst | 102 Lenovo Thinkpad T440s setup
104 Lenovo Thinkpad T460/560 setup
106 Lenovo Thinkpad T470 dock setup
114 COEF setup for Dell M101z
118 Inversed EAPD setup for Lenovo laptops
120 H/W EQ COEF setup for Sony laptops
170 ALC283 COEF setup for Lenovo machines
365 Setup ALC889 COEF
375 GPIO setup for Mac Pro
379 Vref setup for Macbook Pro
[all …]
|
| /Documentation/driver-api/iio/ |
| D | triggered-buffers.rst | 7 IIO triggered buffer setup
10 * :c:func:`iio_triggered_buffer_setup` — Setup triggered buffer and pollfunc
13 * struct :c:type:`iio_buffer_setup_ops` — buffer setup related callbacks
15 A typical triggered buffer setup looks like this::
45 /* setup triggered buffer, usually in probe function */
52 * :c:type:`iio_buffer_setup_ops`, the buffer setup functions to be called at
|
| D | hw-consumer.rst | 18 HW consumer setup
22 A typical IIO HW consumer setup looks like this::
|
| D | triggers.rst | 44 IIO trigger setup
47 Let's see a simple example of how to setup a trigger to be used by a driver::
59 /* setup trigger operations field */
|
| /Documentation/devicetree/bindings/pinctrl/ |
| D | pinctrl-mt8183.txt | 65 For I2C pins, there are existing generic driving setup and the specific
66 driving setup. I2C pins can only support 2/4/6/8/10/12/14/16mA driving
67 adjustment in generic driving setup. But in specific driving setup,
69 driving setup for I2C pins, the existing generic driving setup will be
71 driving setup. The specific driving setup is controlled by E1E0EN.
75 driving setup property. "XXX" means the value of E1E0EN. EN is 0 or 1.
76 It is used to enable or disable the specific driving setup.
|
| /Documentation/devicetree/bindings/memory-controllers/ |
| D | atmel,ebi.txt | 70 (next device setup time is subtracted to the
83 - atmel,smc-ncs-rd-setup-ns
84 - atmel,smc-nrd-setup-ns
85 - atmel,smc-ncs-wr-setup-ns
86 - atmel,smc-nwe-setup-ns
124 atmel,smc-ncs-rd-setup-ns = <0>;
125 atmel,smc-ncs-wr-setup-ns = <0>;
126 atmel,smc-nwe-setup-ns = <8>;
127 atmel,smc-nrd-setup-ns = <16>;
|
| D | ti-aemif.txt | 102 - ti,cs-read-setup-ns: read setup width, ns
119 - ti,cs-write-setup-ns: write setup width, ns
168 ti,cs-read-setup-ns = <14>;
171 ti,cs-write-setup-ns = <14>;
197 ti,cs-read-setup-ns = <14>;
200 ti,cs-write-setup-ns = <14>;
|
| D | mvebu-devbus.txt | 62 - devbus,rd-setup-ps: Defines the time delay between DEV_CSn assertion to
66 (no affect on first data sample). Set <rd-setup-ps>
91 is active. This parameter defines the setup time of
145 devbus,rd-setup-ps = <0>;
|
| /Documentation/power/ |
| D | swsusp-dmcrypt.rst | 18 system for crypto setup and/or rescue purposes. You may even have
19 an initrd that does your current crypto setup already.
44 modify. For lilo the simplest setup looks like the following
53 you create an initrd that reads the required dm-crypt setup
56 card contains at least the encrypted swap setup in a file
65 of your crypto devices, again by reading the setup from the
125 Then we need to set up dmcrypt with the setup data from the
|
| /Documentation/networking/caif/ |
| D | caif.rst | 27 Preparing the setup with a STE modem
100 - Channel Setup::
107 Command:Channel Setup(1)
116 bit 0x20 set in the command bit, and Channel Setup has added one byte
126 - last_tx_msg contains channel setup message and last_rx_msg is empty ->
|
| /Documentation/driver-api/firmware/ |
| D | firmware_cache.rst | 24 Some implementation details about the firmware cache setup:
26 * The firmware cache is setup by adding a devres entry for each device that
36 criteria the firmware cache is setup by adding a devres entry for the
|
| /Documentation/networking/device_drivers/cirrus/ |
| D | cs89x0.txt | 117 * CS8900/20 Setup Utility (DOS-based)
146 stored in an on-board EEPROM. You must use the DOS-based CS8900/20 Setup
154 Since the CS8900/20 Setup Utility is a DOS-based application, you must install
155 and configure the adapter in a DOS-based system using the CS8900/20 Setup
177 CS8900/20 Setup Utility.
185 run the CS8900/20 Setup Utility to disable PnP and configure the
196 * RUN THE CS8900/20 SETUP UTILITY TO DISABLE PnP SUPPORT AND *
379 the CS8900/20 Setup Utility can be used to test the functionality of the
384 CS8900/20-based adapter card (it must also be running the CS8900/20 Setup
387 NOTE: The Setup Utility's diagnostics are designed to run in a
[all …]
|
| /Documentation/arm/samsung-s3c24xx/ |
| D | suspend.rst | 50 A board can do its own setup before calling s3c_pm_init, if it
51 needs to setup anything else for power management support.
96 relevant clocks and peripherals setup before use (ie, bootloader).
99 rate and uart controls must be setup beforehand.
|
| /Documentation/arm/ |
| D | cluster-pm-race-avoidance.rst | 6 cluster setup and teardown operations and to manage hardware coherency
118 cluster setup and
119 CPU setup complete policy decision
323 setup to enable other CPUs in the cluster to enter coherency
329 cluster-level setup and hardware coherency complete
336 Cluster-level setup is complete and hardware coherency is
354 Cluster-level setup is complete and hardware coherency is
421 unnecessary teardown and setup operations in situations where
429 cluster-level setup and hardware
449 The CPU which performs cluster setup on the inbound side is commonly
[all …]
|
| D | booting.rst | 19 1. Setup and initialise the RAM.
22 4. Setup the kernel tagged list.
27 1. Setup and initialise RAM
82 4. Setup boot data
94 4a. Setup the kernel tagged list
126 4b. Setup the device tree
|
| /Documentation/x86/ |
| D | zero-page.rst | 8 real-mode setup code of the kernel. References/settings to it mainly
30 140/080 ALL edid_info Video mode setup (struct edid_info)
33 1E4/004 ALL scratch Scratch field for the kernel setup code
|
| /Documentation/fb/ |
| D | deferred_io.rst | 7 IO. The following example may be a useful explanation of how one such setup
51 1. Setup your structure. Eg::
62 2. Setup your deferred IO callback. Eg::
|
| D | ep93xx-fb.rst | 87 callbacks: setup, teardown and blank. The setup and teardown functions
92 The setup and teardown devices pass the platform_device structure as
101 /* Board specific framebuffer setup */
|
| /Documentation/devicetree/bindings/mtd/ |
| D | lpc32xx-slc.txt | 17 - nxp,wsetup: Write setup time (W_SETUP)
20 - nxp,rsetup: Read setup time (R_SETUP)
|
| /Documentation/sh/ |
| D | new-machine.txt | 99 After you have setup your new arch/sh/boards/ directory, remember that you
111 setup code, we're required at the very least to provide definitions for
116 * arch/sh/boards/vapor/setup.c - Setup code for imaginary board
129 * setup here. Though it's also sane to leave this empty
183 - Add machine vector definitions to the board's setup.c. At a bare minimum,
197 Now that we have the corresponding directories setup, and all of the
|
| /Documentation/filesystems/nfs/ |
| D | nfs-rdma.txt | 15 - Check RDMA and NFS Setup
16 - NFS/RDMA Setup
21 This document describes how to install and setup the Linux NFS/RDMA client
157 Check RDMA and NFS Setup
166 - Check RDMA Setup
199 - Check NFS Setup
204 NFS/RDMA Setup
|
| /Documentation/devicetree/bindings/display/exynos/ |
| D | samsung-fimd.txt | 46 - cs-setup: clock cycles for the active period of address signal is enabled
49 - wr-setup: clock cycles for the active period of CS signal is enabled until
63 | cs-setup+1 | : : :
66 | wr-setup+1 | | wr-hold+1 |
|
| /Documentation/ |
| D | dontdiff | 220 setup
221 setup.bin
222 setup.elf
|
| /Documentation/devicetree/bindings/phy/ |
| D | nvidia,tegra20-usb-phy.txt | 46 - nvidia,xcvr-setup : integer, uses the provided value.
47 - nvidia,xcvr-setup-use-fuses : boolean, indicates that the value is read
49 If both are provided, nvidia,xcvr-setup-use-fuses takes precedence.
|
| /Documentation/devicetree/bindings/power/reset/ |
| D | keystone-reset.txt | 37 Setup keystone reset so that in case software reset or
58 Setup keystone reset so that in case of software reset or
|
12345678910>>...14