Home
last modified time | relevance | path

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

12345678910>>...17

/openbmc/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>;
/openbmc/linux/Documentation/devicetree/bindings/pinctrl/
H A Dmediatek,mt8183-pinctrl.yaml120 Describe the specific driving setup property.
121 For I2C pins, the existing generic driving setup can only support
122 2/4/6/8/10/12/14/16mA driving. But in specific driving setup, they
124 driving setup, the existing generic setup will be disabled.
125 The specific driving setup is controlled by E1E0EN.
130 EN is used to enable or disable the specific driving setup.
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
/openbmc/u-boot/drivers/ddr/marvell/axp/
H A Dddr3_axp_mc_static.h42 {0x000014C0, 0x192434e9}, /* DRAM address and Control Driving Strenght */
43 {0x000014C4, 0x092434e9}, /* DRAM Data and DQS Driving Strenght */
100 {0x000014C0, 0x192434e9}, /* DRAM address and Control Driving Strenght */
101 {0x000014C4, 0x092434e9}, /* DRAM Data and DQS Driving Strenght */
152 {0x000014C0, 0x192424C8}, /* DRAM address and Control Driving Strenght */
153 {0x000014C4, 0xEFB24C8}, /* DRAM Data and DQS Driving Strenght */
209 {0x000014C0, 0x192424C8}, /* DRAM address and Control Driving Strenght */
210 {0x000014C4, 0xEFB24C8}, /* DRAM Data and DQS Driving Strenght */
258 {0x000014C0, 0x192424C8}, /* DRAM address and Control Driving Strenght */
259 {0x000014C4, 0xEFB24C8}, /* DRAM Data and DQS Driving Strenght */
/openbmc/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.
96 that all devices are represented including the master driving
/openbmc/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.
/openbmc/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.yaml37 description: Delay to wait after driving gpio active
41 description: Delay to wait after driving gpio inactive
/openbmc/linux/Documentation/driver-api/gpio/
H A Dintro.rst69 MMC/SD card insertion/removal, detecting card write-protect status, driving
115 The same logic can be applied to emulate open source signaling, by driving the
119 If you are "driving" the signal high but gpiod_get_value(gpio) reports a low
121 driving the shared signal low. That's not necessarily an error. As one common
/openbmc/linux/drivers/misc/cardreader/
H A Drts5227.c39 u8 (*driving)[3], drive_sel; in rts5227_fill_driving() local
42 driving = driving_3v3; in rts5227_fill_driving()
45 driving = driving_1v8; in rts5227_fill_driving()
50 0xFF, driving[drive_sel][0]); in rts5227_fill_driving()
52 0xFF, driving[drive_sel][1]); in rts5227_fill_driving()
54 0xFF, driving[drive_sel][2]); in rts5227_fill_driving()
125 /* Configure driving */ in rts5227_extra_init_hw()
H A Drts5228.c41 u8 (*driving)[3], drive_sel; in rts5228_fill_driving() local
44 driving = driving_3v3; in rts5228_fill_driving()
47 driving = driving_1v8; in rts5228_fill_driving()
52 0xFF, driving[drive_sel][0]); in rts5228_fill_driving()
55 0xFF, driving[drive_sel][1]); in rts5228_fill_driving()
58 0xFF, driving[drive_sel][2]); in rts5228_fill_driving()
430 /* Configure driving */ in rts5228_extra_init_hw()
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()
/openbmc/u-boot/drivers/usb/gadget/
H A Dbcm_udc_otg_phy.c20 /* set Phy to driving mode */ in otg_phy_init()
50 /* set Phy to non-driving (reset) mode */ in otg_phy_off()
/openbmc/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
/openbmc/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
/openbmc/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)
/openbmc/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
/openbmc/u-boot/board/cssi/MCR3000/
H A Dnand.c30 /* Driving NCE pin */ in nand_hwcontrol()
36 /* Driving CLE and ALE pin */ in nand_hwcontrol()
/openbmc/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()
/openbmc/linux/Documentation/devicetree/bindings/display/panel/
H A Dboe,bf060y8m-aj0.yaml30 description: EL Driving positive (VDD) supply (4.40-4.80V)
32 description: EL Driving negative (VSS) supply (-5.00V to -1.40V)
/openbmc/linux/drivers/comedi/drivers/
H A Dcomedi_8255.c177 * subdev_8255_init - initialize DIO subdevice for driving I/O mapped 8255
183 * Initializes a comedi subdevice as a DIO subdevice driving an 8255 chip.
212 * subdev_8255_mm_init - initialize DIO subdevice for driving mmio-mapped 8255
218 * Initializes a comedi subdevice as a DIO subdevice driving an 8255 chip.
/openbmc/linux/Documentation/devicetree/bindings/mfd/
H A Drichtek,rt4831.yaml19 For the LCD backlight, it can provide four channel WLED driving capability.
20 Each channel driving current is up to 30mA
/openbmc/linux/Documentation/devicetree/bindings/sound/
H A Drt5682.txt62 - realtek,dmic-clk-driving-high : Set the high driving of the DMIC clock out.

12345678910>>...17