Home
last modified time | relevance | path

Searched full:driving (Results 1 – 25 of 229) sorted by relevance

12345678910

/linux/Documentation/devicetree/bindings/phy/
H A Drealtek,usb2phy.yaml93 usb-dc-cal is the driving level for each phy specified via efuse.
102 realtek,driving-level:
113 realtek,driving-level-compensate:
115 For RTD1315e SoC, the driving level can be adjusted by reading the
159 realtek,driving-level-compensate: false
173 realtek,driving-level = <0xa>;
/linux/Documentation/devicetree/bindings/pinctrl/
H A Dmediatek,mt8365-pinctrl.yaml124 Describe the specific driving setup property.
125 For I2C pins, the existing generic driving setup can only support
126 2/4/6/8/10/12/14/16mA driving. But in specific driving setup, they
128 driving setup, the existing generic setup will be disabled.
129 The specific driving setup is controlled by E1E0EN.
134 EN is used to enable or disable the specific driving setup.
H A Dsprd,pinctrl.txt8 pad driving level, system control select and so on ("domain pad
9 driving level": One pin can output 3.0v or 1.8v, depending on the
10 related domain pad driving selection, if the related domain pad
H A Dnuvoton,ma35d1-pinctrl.yaml121 description: 1.8V I/O driving strength
123 description: 3.3V I/O driving strength
/linux/Documentation/ABI/testing/
H A Dsysfs-bus-i3c53 This entry describes the BCR of the master controller driving
63 This entry describes the DCR of the master controller driving
75 This entry describes the PID of the master controller driving
89 driving the bus.
104 Controller driving the bus.
111 that all devices are represented including the master driving
/linux/drivers/comedi/drivers/
H A Dcomedi_8255.c180 * subdev_8255_io_init - initialize DIO subdevice for driving I/O mapped 8255
185 * Initializes a comedi subdevice as a DIO subdevice driving an 8255 chip.
199 * subdev_8255_mm_init - initialize DIO subdevice for driving mmio-mapped 8255
204 * Initializes a comedi subdevice as a DIO subdevice driving an 8255 chip.
216 * subdev_8255_cb_init - initialize DIO subdevice for driving callback-mapped 8255
222 * Initializes a comedi subdevice as a DIO subdevice driving an 8255 chip.
/linux/drivers/pinctrl/mediatek/
H A Dpinctrl-mtk-common.h71 * struct mtk_drv_group_desc - Provide driving group data.
96 * struct mtk_pin_drv_grp - Provide each pin driving info.
98 * @offset: The offset of driving register for this pin.
99 * @bit: The bit of driving register for this pin.
194 * @grp_desc: The driving group info.
195 * @pin_drv_grp: The driving group for all pins.
/linux/Documentation/driver-api/gpio/
H A Dintro.rst57 MMC/SD card insertion/removal, detecting card write-protect status, driving
103 The same logic can be applied to emulate open source signaling, by driving the
107 If you are "driving" the signal high but gpiod_get_value(gpio) reports a low
109 driving the shared signal low. That's not necessarily an error. As one common
/linux/Documentation/devicetree/bindings/power/reset/
H A Dgpio-restart.yaml42 description: Treat the GPIO as being open source and defer driving it to when the restart is
51 description: Delay (default 100) to wait after driving gpio active [ms]
56 description: Delay (default 100) to wait after driving gpio inactive [ms]
H A Dgpio-poweroff.yaml40 description: Delay to wait after driving gpio active
44 description: Delay to wait after driving gpio inactive
/linux/Documentation/devicetree/bindings/media/
H A Dpxa-camera.txt11 - clock-output-names: should contain the name of the clock driving the
13 - clock-frequency: host interface is driving MCLK, and MCLK rate is this rate
/linux/drivers/misc/cardreader/
H A Drts5260.c41 u8 (*driving)[3], drive_sel; in rts5260_fill_driving() local
44 driving = driving_3v3; in rts5260_fill_driving()
47 driving = driving_1v8; in rts5260_fill_driving()
52 0xFF, driving[drive_sel][0]); in rts5260_fill_driving()
55 0xFF, driving[drive_sel][1]); in rts5260_fill_driving()
58 0xFF, driving[drive_sel][2]); in rts5260_fill_driving()
H A Drts5261.c40 u8 (*driving)[3], drive_sel; in rts5261_fill_driving() local
43 driving = driving_3v3; in rts5261_fill_driving()
46 driving = driving_1v8; in rts5261_fill_driving()
51 0xFF, driving[drive_sel][0]); in rts5261_fill_driving()
54 0xFF, driving[drive_sel][1]); in rts5261_fill_driving()
57 0xFF, driving[drive_sel][2]); in rts5261_fill_driving()
505 /* Configure driving */ in rts5261_extra_init_hw()
/linux/arch/arm/mach-tegra/
H A Dplatsmp.c49 * flow controller to stop driving reset if the CPU has been in tegra20_boot_secondary()
59 * stop driving reset. The CPU will remain in reset because the in tegra20_boot_secondary()
60 * clock and reset block is now driving reset. in tegra20_boot_secondary()
/linux/Documentation/devicetree/bindings/leds/backlight/
H A Drichtek,rt4831-backlight.yaml16 For the LCD backlight, it can provide four channel WLED driving capability.
17 Each channel driving current is up to 30mA
/linux/Documentation/devicetree/bindings/hwmon/
H A Dfan-common.yaml42 fan-driving-mode:
44 Select the driving mode of the fan.(DC, PWM and so on)
/linux/Documentation/devicetree/bindings/bus/
H A Drenesas,bsc.yaml15 devices to the SoC, driving several chip select lines, for e.g. NOR
21 must be powered on, and the functional clock driving the BSC must be
/linux/Documentation/devicetree/bindings/display/panel/
H A Dboe,bf060y8m-aj0.yaml33 description: EL Driving positive (VDD) supply (4.40-4.80V)
35 description: EL Driving negative (VSS) supply (-5.00V to -1.40V)
/linux/include/media/
H A Dcec-pin.h19 * @high: stop driving the CEC pin. The pull-up will drive the pin
20 * high, unless someone else is driving the pin low.
/linux/Documentation/devicetree/bindings/sound/
H A Drealtek,rt5682s.yaml72 realtek,dmic-clk-driving-high:
75 Set the high driving of the DMIC clock out.
/linux/Documentation/timers/
H A Dtimekeeping.rst94 a different thing. The hardware driving clock events has to be able to
96 system, it is ideal (and customary) to have one such event driving timer per
138 The clock driving sched_clock() may stop or reset to zero during system
/linux/drivers/video/fbdev/matrox/
H A Dmatroxfb_DAC1064.h44 /* pixel clock allowed to(0)/blocked from(1) driving CRTC1 */
48 /* CRTC2 pixel clock allowed to(0)/blocked from(1) driving CRTC2 */
/linux/tools/perf/pmu-events/arch/arm64/arm/neoverse-n1/
H A Dgeneral.json4 … cycles). The clock measured by this event is defined as the physical clock driving the CPU logic."
/linux/tools/perf/pmu-events/arch/arm64/arm/neoverse-v1/
H A Dgeneral.json4 … cycles). The clock measured by this event is defined as the physical clock driving the CPU logic."
/linux/Documentation/devicetree/bindings/soc/fsl/cpm_qe/cpm/
H A Dbrg.txt11 - clock-frequency : Specifies the base frequency driving

12345678910