Home
last modified time | relevance | path

Searched refs:driving (Results 1 – 47 of 47) sorted by relevance

/linux-4.1.27/drivers/mfd/
Drts5227.c43 u8 (*driving)[3], drive_sel; in rts5227_fill_driving() local
46 driving = driving_3v3; in rts5227_fill_driving()
49 driving = driving_1v8; in rts5227_fill_driving()
54 0xFF, driving[drive_sel][0]); in rts5227_fill_driving()
56 0xFF, driving[drive_sel][1]); in rts5227_fill_driving()
58 0xFF, driving[drive_sel][2]); in rts5227_fill_driving()
Drts5249.c50 u8 (*driving)[3], drive_sel; in rts5249_fill_driving() local
53 driving = driving_3v3; in rts5249_fill_driving()
56 driving = driving_1v8; in rts5249_fill_driving()
61 0xFF, driving[drive_sel][0]); in rts5249_fill_driving()
63 0xFF, driving[drive_sel][1]); in rts5249_fill_driving()
65 0xFF, driving[drive_sel][2]); in rts5249_fill_driving()
/linux-4.1.27/Documentation/devicetree/bindings/media/
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-4.1.27/Documentation/devicetree/bindings/gpio/
Dgpio-restart.txt28 - open-source : Treat the GPIO as being open source and defer driving
40 - active-delay: Delay (default 100) to wait after driving gpio active [ms]
41 - inactive-delay: Delay (default 100) to wait after driving gpio inactive [ms]
Dgpio-pcf857x.txt7 (a) as output and driving the signal low/high, or (b) as input and reporting a
/linux-4.1.27/Documentation/devicetree/bindings/bus/
Drenesas,bsc.txt7 SoC, driving several chip select lines, for e.g. NOR FLASH, Ethernet and USB.
13 driving the BSC must be enabled.
/linux-4.1.27/Documentation/devicetree/bindings/powerpc/fsl/cpm_qe/cpm/
Dbrg.txt11 - clock-frequency : Specifies the base frequency driving
/linux-4.1.27/Documentation/devicetree/bindings/timer/
Dmediatek,mtk-timer.txt7 - clocks: Clocks driving the timer hardware. This list should include two
Darm,sp804.txt11 - clocks: clocks driving the dual timer hardware. This list should be 1 or 3
/linux-4.1.27/Documentation/devicetree/bindings/serial/
Dbrcm,bcm6345-uart.txt11 - clocks: Clock driving the hardware; used to figure out the baud rate
Dmtk-uart.txt17 - clocks: Clock driving the hardware.
/linux-4.1.27/Documentation/gpio/
Dgpio.txt64 MMC/SD card insertion/removal, detecting card write-protect status, driving
110 The same logic can be applied to emulate open source signaling, by driving the
114 If you are "driving" the signal high but gpiod_get_value(gpio) reports a low
116 driving the shared signal low. That's not necessarily an error. As one common
Dgpio-legacy.txt51 MMC/SD card insertion/removal, detecting card writeprotect status, driving
339 to make the pin HIGH. The pin is make to LOW by driving value 0 in output mode.
345 to make the pin LOW. The pin is make to HIGH by driving value 1 in output mode.
434 If you are "driving" the signal high but gpio_get_value(gpio) reports a low
436 is driving the shared signal low. That's not necessarily an error. As one
/linux-4.1.27/Documentation/devicetree/bindings/net/can/
Dfsl-flexcan.txt17 - clock-frequency : The oscillator frequency driving the flexcan device
/linux-4.1.27/drivers/clk/versatile/
DKconfig24 Simple regmap-based driver driving clock generators on Versatile
/linux-4.1.27/Documentation/hwmon/
Dpwm-fan14 The driver implements a simple interface for driving a fan connected to
Dg76247 pwm1_mode: set or get fan driving mode: 1 for PWM mode, 0 for DC mode.
Dadm9240151 Datasheet has an example of an external temperature sensor driving
Dlm9396 The LM93 can also override the #PROCHOT pins by driving a PWM signal onto
/linux-4.1.27/Documentation/devicetree/bindings/powerpc/fsl/
Dgtm.txt11 - clock-frequency : specifies the frequency driving the timer.
/linux-4.1.27/Documentation/ABI/testing/
Dsysfs-bus-iio-frequency-ad952328 Writing this file has the effect as driving the external
Dsysfs-class-led36 it is useful when driving a LED which is intended to indicate
/linux-4.1.27/Documentation/devicetree/bindings/usb/
Dusb3503.txt18 - refclk: Clock used for driving REFCLK signal (optional, if not provided
/linux-4.1.27/drivers/pinctrl/mediatek/
Dpinctrl-mtk-common.c159 unsigned int pin, unsigned char driving) in mtk_pconf_set_driving() argument
174 if (driving >= drv_grp->min_drv && driving <= drv_grp->max_drv in mtk_pconf_set_driving()
175 && !(driving % drv_grp->step)) { in mtk_pconf_set_driving()
176 val = driving / drv_grp->step - 1; in mtk_pconf_set_driving()
/linux-4.1.27/drivers/staging/iio/Documentation/
Dinkernel.txt4 providing a means of obtaining ADC type readings or of driving DAC type
/linux-4.1.27/drivers/staging/speakup/
DTODO22 as was already done for the serial port driving part.
/linux-4.1.27/Documentation/timers/
Dtimekeeping.txt93 a different thing. The hardware driving clock events has to be able to
95 system, it is ideal (and customary) to have one such event driving timer per
137 The clock driving sched_clock() may stop or reset to zero during system
Dtimers-howto.txt53 driving each of these calls varies, thus there are
/linux-4.1.27/Documentation/devicetree/bindings/spi/
Dspi-samsung.txt35 indicate the clock to be used for driving the spi bus clock. If not specified,
/linux-4.1.27/Documentation/arm/pxa/
Dmfp.txt15 also controls the low power state, driving strength, pull-up/down and event
267 selection of 1, driving strength of 0b101, and a float state in low power
/linux-4.1.27/Documentation/
Dunicode.txt173 The CSUR people are driving adding Tengwar and Cirth into Unicode
Dpinctrl.txt11 biasing and driving mode specific pins, such as pull-up/down, open drain,
202 stable value when nothing is driving the rail it is connected to, or when it's
829 separate memory range only intended for GPIO driving, and the register
DDMA-API-HOWTO.txt149 your device only capable of driving the low order 24-bits of address?
Dkernel-parameters.txt3610 Default is on (1). Disable the driving of swap pages
/linux-4.1.27/drivers/gpio/
DKconfig404 that can be up to 24 bit. This peripheral is aimed at driving leds.
724 This driver provides support for driving the pins in output
765 This driver provides the support for driving/reading the gpio pins
/linux-4.1.27/drivers/staging/panel/
DKconfig159 be driving a serial LCD or a parallel one. Serial LCDs only use 2 wires
/linux-4.1.27/Documentation/ide/
Dide.txt77 or may not be harmful to your hardware.. two or more cards driving the same IRQ
/linux-4.1.27/Documentation/devicetree/bindings/gpu/
Dnvidia,tegra20-host1x.txt223 Optional properties when driving an eDP output:
/linux-4.1.27/arch/arm/boot/dts/
Dste-nomadik-stn8815.dtsi270 * IP AMBA bus clocks, driving the bus side of the
/linux-4.1.27/drivers/usb/gadget/
DKconfig446 userspace program driving the print engine. The user space
/linux-4.1.27/drivers/usb/gadget/legacy/
DKconfig307 userspace program driving the print engine. The user space
/linux-4.1.27/Documentation/scsi/
Dscsi_eh.txt198 of driving error handling. EH's goals are two - make LLDD, host and
/linux-4.1.27/Documentation/cgroups/
Dblkio-controller.txt386 groups and put applications in that group which are not driving enough
/linux-4.1.27/drivers/scsi/aic7xxx/
Daic7xxx.seq413 * driving REQ on the bus for the next byte.
2012 * out (initiator driving) to in (target driving),
/linux-4.1.27/Documentation/devicetree/
Dusage-model.txt147 If one does, then that machine_desc is a candidate for driving the
/linux-4.1.27/Documentation/filesystems/caching/
Dbackend-api.txt166 various asynchronous operations that need to be done as part of driving
/linux-4.1.27/Documentation/laptops/
Dthinkpad-acpi.txt1077 amplifiers driving the speakers and headphone output, and the firmware