Searched full:spec (Results  1 – 25 of 153) sorted by relevance
1234567
| /Documentation/devicetree/bindings/net/ieee802154/ | 
| D | cc2520.txt | 10 	- fifo-gpio:		GPIO spec for the FIFO pin 11 	- fifop-gpio:		GPIO spec for the FIFOP pin 12 	- sfd-gpio:		GPIO spec for the SFD pin 13 	- cca-gpio:		GPIO spec for the CCA pin 14 	- vreg-gpio:		GPIO spec for the VREG pin 15 	- reset-gpio:		GPIO spec for the RESET pin
  | 
| D | at86rf230.txt | 13   - reset-gpio:		GPIO spec for the rstn pin 14   - sleep-gpio:		GPIO spec for the slp_tr pin
  | 
| D | mcr20a.txt | 12   - rst_b-gpio:		GPIO spec for the RST_B pin
  | 
| /Documentation/sound/hd-audio/ | 
| D | dp-mst.rst | 15 per_pin. Driver uses spec->dyn_pcm_assign flag to indicate whether to use 58 For !dyn_pcm_assign, per_pin->pcm will assigned to spec->pcm[n] statically. 60 For dyn_pcm_assign, per_pin->pcm will assigned to spec->pcm[n] 69   Will not use hda_jack but use snd_jack in spec->pcm_rec[pcm_idx].jack directly. 73   Use hda_jack and assign spec->pcm_rec[pcm_idx].jack = jack->jack statically. 88   Use directly snd_jack_report() on spec->pcm_rec[pcm_idx].jack for 96   Use directly snd_jack_report() on spec->pcm_rec[pcm_idx].jack for dyn_pcm_assign.
  | 
| /Documentation/devicetree/bindings/sound/ | 
| D | ak5386.txt | 11   - reset-gpio : a GPIO spec for the reset/power down pin. 13   - va-supply : a regulator spec, providing 5.0V 14   - vd-supply : a regulator spec, providing 3.3V
  | 
| D | uda1334.txt | 8   - nxp,mute-gpios: a GPIO spec for the MUTE pin. 9   - nxp,deemph-gpios: a GPIO spec for the De-emphasis pin
  | 
| D | st,sta32x.txt | 9   - reset-gpios: a GPIO spec for the reset pin. If specified, it will be 12   - power-down-gpios: a GPIO spec for the power down pin. If specified, 16   - Vdda-supply: regulator spec, providing 3.3V 17   - Vdd3-supply: regulator spec, providing 3.3V 18   - Vcc-supply: regulator spec, providing 5V - 26V
  | 
| D | tda7419.txt | 9 - vdd-supply : a regulator spec for the common power supply (8-10V) 13 - st,mute-gpios : a GPIO spec for the MUTE pin.
  | 
| D | st,sta350.txt | 9   - reset-gpios: a GPIO spec for the reset pin. If specified, it will be 12   - power-down-gpios: a GPIO spec for the power down pin. If specified, 16   - vdd-dig-supply: regulator spec, providing 3.3V 17   - vdd-pll-supply: regulator spec, providing 3.3V 18   - vcc-supply: regulator spec, providing 5V - 26V
  | 
| D | cs53l30.txt | 14   - reset-gpios : a GPIO spec for the reset pin. 16   - mute-gpios : a GPIO spec for the MUTE pin. The active state can be either
  | 
| D | cs4349.txt | 11   - reset-gpios : a GPIO spec for the reset pin.
  | 
| D | cs42l73.txt | 11   - reset_gpio : a GPIO spec for the reset pin.
  | 
| /Documentation/devicetree/bindings/riscv/ | 
| D | extensions.yaml | 116             encoding") of the riscv-v-spec. 432             riscv-crypto-spec-vector.adoc") of riscv-crypto. 438             riscv-crypto-spec-vector.adoc") of riscv-crypto. 444             riscv-v-spec. 450             riscv-v-spec. 456             riscv-v-spec. 462             riscv-v-spec. 468             riscv-v-spec. 474             ("Remove draft warnings from Zvfh[min]") of riscv-v-spec. 480             ("Remove draft warnings from Zvfh[min]") of riscv-v-spec. [all …] 
 | 
| /Documentation/hid/ | 
| D | hidreport-parsing.rst | 27           ---- Length of data (see HID spec 6.2.2.2) 29         ------ Type of the item (see HID spec 6.2.2.2, then jump to 6.2.2.7) 31     --------- Function of the item (see HID spec 6.2.2.7, then HUT Sec 3) 45 (``0000``) is given in the HID spec Sec. 6.2.2.8 "Local Items", so that
  | 
| /Documentation/devicetree/bindings/spi/ | 
| D | spi-gpio.yaml | 24     description: GPIO spec for the SCK line to use 28     description: GPIO spec for the MISO line to use 32     description: GPIO spec for the MOSI line to use
  | 
| /Documentation/arch/arm/ | 
| D | marvell.rst | 51 …- Hardware Spec  : https://web.archive.org/web/20121021182835/http://www.marvell.com/embedded-proc… 52 …- Functional Spec: https://web.archive.org/web/20130730091033/http://www.marvell.com/embedded-proc… 56 …- Hardware Spec  : https://web.archive.org/web/20121021182835/http://www.marvell.com/embedded-proc… 57 …- Functional Spec: https://web.archive.org/web/20130730091033/http://www.marvell.com/embedded-proc… 62 …- Hardware Spec  : https://web.archive.org/web/20130730091654/http://www.marvell.com/embedded-proc… 63 …- Functional Spec: https://web.archive.org/web/20130730091033/http://www.marvell.com/embedded-proc… 70 …- Hardware Spec  : https://web.archive.org/web/20120620073511/http://www.marvell.com/embedded-proc… 71 …- Functional Spec: https://web.archive.org/web/20130730091033/http://www.marvell.com/embedded-proc… 93 …- Hardware Spec  : https://web.archive.org/web/20141005120451/http://www.marvell.com/embedded-proc… 94 …- Functional Spec: https://web.archive.org/web/20111110081125/http://www.marvell.com/embedded-proc… [all …] 
 | 
| /Documentation/userspace-api/netlink/ | 
| D | intro-specs.rst | 21  - ``--spec`` - point to the spec file 30   $ ./tools/net/ynl/cli.py --spec Documentation/netlink/specs/ethtool.yaml \ 49 The spec and Netlink internals are factored out as a standalone 60 By default code is re-generated only if spec is newer than the source, 73 The simplest way to generate a new file based on a spec is to add
  | 
| D | specs.rst | 11 Netlink specs should be complete and not depend on any other spec 81 Attributes listed directly at the root level of the spec file. 150 Note that the spec is "flattened" and is not meant to visually resemble 152 formats seen in kernel comments). In the spec subordinate attribute sets 156 Spec may also contain fractional sets - sets which contain a ``subset-of`` 209 entry ``0`` is almost always reserved as undefined. Spec can explicitly 253 rather than depend on what is specified in the spec file.
  | 
| /Documentation/driver-api/virtio/ | 
| D | virtio.rst | 14 Types") of the virtio spec (`[1]`_). Originally developed as a standard 30 orthogonal to the device itself. The virtio spec defines these transport 46 Refer to Chapter 2.5 ("Virtqueues") of the virtio spec (`[1]`_) for the 82 and device id 0x1003 (virtio console), as defined in the spec, so the 135 _`[1]` Virtio Spec v1.2: 138 .. Check for later versions of the spec as well.
  | 
| D | writing_virtio_drivers.rst | 22 and configure the virtqueues for the device according to its spec, the 111 should be added only for devices that are defined in the spec, see 113 in the virtio spec before being added to that file. 193 _`[1]` Virtio Spec v1.2: 196 Check for later versions of the spec as well.
  | 
| /Documentation/devicetree/bindings/power/supply/ | 
| D | bq24735.yaml | 41       See spec for more information about the ChargeCurrent (0x14h) register. 49       See spec for more information about the ChargeVoltage (0x15h) register. 57       See the spec for more information about the InputCurrent (0x3fh) register.
  | 
| /Documentation/arch/x86/x86_64/ | 
| D | index.rst | 15    cpu-hotplug-spec
  | 
| /Documentation/devicetree/bindings/media/i2c/ | 
| D | isil,isl79987.yaml | 29       A GPIO spec for the RSTB pin (active high) 34       A GPIO spec for the Power Down pin (active high)
  | 
| D | ad5820.txt | 16    - enable-gpios : GPIO spec for the XSHUTDOWN pin. The XSHUTDOWN signal is
  | 
| /Documentation/virt/kvm/x86/ | 
| D | amd-memory-encryption.rst | 157 For more details, see SEV spec Section 6.2. 178 For more details, see SEV spec Section 6.3. 204 For more details on the measurement verification flow, see SEV spec Section 6.4. 435 For more details, see SEV spec Section 6.12. 544 See the SEV-SNP spec [snp-fw-abi]_ for further details on how each page type is 594 information, see the SEV Key Management spec [api-spec]_ 606 See [white-paper]_, [api-spec]_, [amd-apm]_, [kvm-forum]_, and [snp-fw-abi]_ 610 .. [api-spec] https://support.amd.com/TechDocs/55766_SEV-KM_API_Specification.pdf
  | 
        1234567