Home
last modified time | relevance | path

Searched full:second (Results 1 – 25 of 1018) sorted by relevance

12345678910>>...41

/Documentation/admin-guide/
Ddevices.txt22 1 = /dev/ram1 Second RAM disk
33 1 = /dev/ptyp1 Second PTY master
108 1 = /dev/ttyp1 Second PTY slave
122 2 = /dev/hd?2 Second partition
193 1 = /dev/loop1 Second loop device
202 16 = /dev/sdb Second SCSI disk whole disk
213 1 = /dev/st1 Second SCSI tape, mode 0
216 33 = /dev/st1l Second SCSI tape, mode 1
219 65 = /dev/st1m Second SCSI tape, mode 2
222 97 = /dev/st1a Second SCSI tape, mode 3
[all …]
/Documentation/devicetree/bindings/clock/
Dqcom,gcc-sc8280xp.yaml27 - description: UFS memory second RX symbol clock
30 - description: UFS card second RX symbol clock
41 - description: Second USB4 PHY pipegmux clock source
42 - description: Second USB4 PHY DP gmux clock source
43 - description: Second USB4 PHY sys pipegmux clock source
44 - description: Second USB4 PHY PCIe pipe clock
45 - description: Second USB4 PHY router max pipe clock
49 - description: Multiport USB second SuperSpeed pipe clock
56 - description: Second EMAC controller reference clock
Dqcom,sa8775p-gcc.yaml27 - description: UFS memory second RX symbol clock
30 - description: UFS card second RX symbol clock
38 - description: Second EMAC controller reference clock
/Documentation/devicetree/bindings/dma/
Dmv-xor-v2.txt9 the second set is the global registers
15 - clock-names: mandatory if there is a second clock, in this case the
16 name must be "core" for the first clock and "reg" for the second
/Documentation/devicetree/bindings/interrupt-controller/
Dcdns,xtensa-pic.txt9 When it's 2, the first cell is the IRQ number, and the second cell
20 * two cells: second cell == 0: internal irq number
21 * second cell == 1: external irq number
Dcdns,xtensa-mx.txt13 * two cells: second cell == 0: internal irq number
14 * second cell == 1: external irq number
/Documentation/scsi/
Daha152x.rst52 override for the second controller
90 configuration override for second controller
95 IOPORT for first and second controller
98 IRQ for first and second controller
101 SCSIID for first and second controller
104 allow targets to disconnect for first and second controller
107 use parity for first and second controller
110 enable synchronous transfers for first and second controller
113 reset DELAY for first and second controller
116 enable extended translation for first and second controller
/Documentation/devicetree/bindings/crypto/
Dinside-secure-safexcel.txt12 - clocks: Reference to the crypto engine clocks, the second clock is
14 - clock-names: mandatory if there is a second clock, in this case the
16 the second one.
/Documentation/devicetree/bindings/sound/
Dmvebu-audio.txt15 (named "pll_regs") and the second one ("soc_ctrl") - for register
21 the data flow, and the second for errors.
25 The second one is optional and defines an external clock.
Dcirrus,madera.yaml40 and the second two cells must be 0. For muxed inputs the
42 right A inputs and the second two cells set the mode of the
102 description of this value. The second cell is ignored for
112 of this value. The second cell is ignored for codecs that
/Documentation/ABI/testing/
Dsysfs-kernel-vmcoreinfo10 second value contains the size of note in hex. This ELF
11 note info is parsed by second kernel and exported to user
/Documentation/devicetree/bindings/gpio/
Dgpio-clps711x.txt6 There should be two registers, first is DATA register, the second
10 the second cell is used to specify the gpio polarity:
Dgpio-thunderx.txt8 - Second cell is a standard generic flag bitfield as described in gpio.txt.
16 - Second cell is triggering flags as defined in interrupts.txt.
Dgpio-twl4030.txt8 - second cell is used to specify optional parameters (unused)
13 The second cell is not used.
Dgpio_atmel.txt8 the second cell is used to specify optional parameters to declare if the GPIO
13 second cell is used to specify irq type flags, see the two cell description
Dcdns,gpio.txt8 * second cell specifies the GPIO flags, as defined in
23 * second cell specifies the IRQ type, as defined in
/Documentation/devicetree/bindings/powerpc/fsl/
Dpamu.txt12 "fsl,pamu-v1.0". The second is "fsl,pamu".
22 interrupt, used for reporting access violations. The second
61 second is the number of "ways". For direct-mapped caches,
67 second is the number of "ways". For direct-mapped caches,
87 the registers where the LIODN is to be set. The second is
/Documentation/trace/
Devents-power.rst59 The second parameter is '1' for enable, '0' for disable, the target
70 The second parameter is the power domain target state.
82 The second parameter is the previous QoS value.
94 The second parameter gives the request type (e.g. "DEV_PM_QOS_RESUME_LATENCY").
/Documentation/devicetree/bindings/iio/adc/
Dti,twl4030-madc.yaml23 ti,system-uses-second-madc-irq:
26 Set if the second madc irq register should be used, which is intended
/Documentation/userspace-api/media/drivers/
Dcx2341x-uapi.rst16 values, the second containing UV macroblocks.
22 second 16 bytes are the second line of the top-left block, etc. After
30 contain 8 UV value pairs (16 bytes in total). The second 16 bytes are the
31 second line of 8 UV pairs of the top-left block, etc. After transmitting
156 the first unsigned long and bits 0-3 of the second unsigned long are used for the
157 second field.
/Documentation/hid/
Dhidreport-parsing.rst34 function is ``Usage Page``, thus for parsing the value 0x01 in the second byte
37 The second number is the actual data, and its meaning can be found in
42 Moving now to the second two bytes, and following the same scheme,
/Documentation/devicetree/bindings/net/
Dcavium-mix.txt10 bank contains the MIX registers. The second bank the corresponding
19 interrupt routing and the second the routing for the AGL interrupts.
/Documentation/sound/cards/
Dbt87x.rst18 The first does video, it is backward compatible to the bt848. The second
19 does audio. snd-bt87x is a driver for the second function. It's a sound
67 The second device (hw:X,1) gives you 8 or 16 bit mono sound. Supported
/Documentation/filesystems/
Didmappings.rst62 what id ``k11000`` corresponds to in the second or third idmapping. The
65 either the second idmapping mapping or third idmapping mapping. The second
77 the full range of the second idmapping.). Neither the second or third idmapping
79 an id mapped. We can simply say that ``u1000`` is unmapped in the second and
114 Now assume we are given the id ``u1100`` in the upper idmapset of the second
116 of the second idmapping. This means we're mapping down in the second
212 then translate ``k11000`` into a userspace id in the second idmapping using the
213 kernel idmapset of the second idmapping::
215 /* Map the kernel id up into a userspace id in the second idmapping. */
221 /* Map the userspace id down into a kernel id in the second idmapping. */
[all …]
/Documentation/devicetree/bindings/usb/
Dtwlxxxx-usb.txt7 the controller has to act as host and the second interrupt number is the
27 and VBUS interrupts. The second interrupt number is optional.

12345678910>>...41