Home
last modified time | relevance | path

Searched +full:foo +full:- +full:supply (Results 1 – 25 of 43) sorted by relevance

12

/kernel/linux/linux-4.19/Documentation/devicetree/bindings/iio/gyroscope/
Dinvensense,mpu3050.txt1 Invensense MPU-3050 Gyroscope device tree bindings
4 - compatible : should be "invensense,mpu3050"
5 - reg : the I2C address of the sensor
8 - interrupts : interrupt mapping for the trigger interrupt from the
13 - vdd-supply : supply regulator for the main power voltage.
14 - vlogic-supply : supply regulator for the signal voltage.
15 - mount-matrix : see iio/mount-matrix.txt
18 - The MPU-3050 will pass through and forward the I2C signals from the
21 i2c gate node. For details see: i2c/i2c-gate.txt
28 interrupt-parent = <&foo>;
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/iio/gyroscope/
Dinvensense,mpu3050.txt1 Invensense MPU-3050 Gyroscope device tree bindings
4 - compatible : should be "invensense,mpu3050"
5 - reg : the I2C address of the sensor
8 - interrupts : interrupt mapping for the trigger interrupt from the
13 - vdd-supply : supply regulator for the main power voltage.
14 - vlogic-supply : supply regulator for the signal voltage.
15 - mount-matrix : see iio/mount-matrix.txt
18 - The MPU-3050 will pass through and forward the I2C signals from the
21 i2c gate node. For details see: i2c/i2c-gate.txt
28 interrupt-parent = <&foo>;
[all …]
/kernel/linux/linux-4.19/Documentation/devicetree/bindings/clock/
Dmaxim,max9485.txt5 - MAX9485_MCLKOUT: A gated, buffered output of the input clock of 27 MHz
6 - MAX9485_CLKOUT: A PLL that can be configured to 16 different discrete
8 - MAX9485_CLKOUT[1,2]: Two gated outputs for MAX9485_CLKOUT
14 - compatible: "maxim,max9485"
15 - clocks: Input clock, must provice 27.000 MHz
16 - clock-names: Must be set to "xclk"
17 - #clock-cells: From common clock binding; shall be set to 1
20 - reset-gpios: GPIO descriptor connected to the #RESET input pin
21 - vdd-supply: A regulator node for Vdd
22 - clock-output-names: Name of output clocks, as defined in common clock
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/clock/
Dmaxim,max9485.txt5 - MAX9485_MCLKOUT: A gated, buffered output of the input clock of 27 MHz
6 - MAX9485_CLKOUT: A PLL that can be configured to 16 different discrete
8 - MAX9485_CLKOUT[1,2]: Two gated outputs for MAX9485_CLKOUT
14 - compatible: "maxim,max9485"
15 - clocks: Input clock, must provice 27.000 MHz
16 - clock-names: Must be set to "xclk"
17 - #clock-cells: From common clock binding; shall be set to 1
20 - reset-gpios: GPIO descriptor connected to the #RESET input pin
21 - vdd-supply: A regulator node for Vdd
22 - clock-output-names: Name of output clocks, as defined in common clock
[all …]
/kernel/linux/linux-4.19/Documentation/devicetree/bindings/iio/accel/
Dkionix,kxsd9.txt4 - compatible: should be set to "kionix,kxsd9"
5 - reg: i2c slave address
8 - vdd-supply: The input supply for VDD
9 - iovdd-supply: The input supply for IOVDD
10 - interrupts: The movement detection interrupt
11 - mount-matrix: See mount-matrix.txt
18 interrupt-parent = <&foo>;
20 iovdd-supply = <&bar>;
21 vdd-supply = <&baz>;
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/
Dexample-schema.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
4 ---
5 # All the top-level keys are standard json-schema keywords except for
10 $id: http://devicetree.org/schemas/example-schema.yaml#
11 # $schema is the meta-schema this schema should be validated with.
12 $schema: http://devicetree.org/meta-schemas/core.yaml#
17 - Rob Herring <robh@kernel.org>
20 A more detailed multi-line description of the binding.
44 - items:
51 - enum:
[all …]
/kernel/linux/linux-4.19/Documentation/devicetree/bindings/iio/pressure/
Dbmp085.txt4 - compatible: must be one of:
11 - interrupts: interrupt mapping for IRQ
12 - reset-gpios: a GPIO line handling reset of the sensor: as the line is
14 - vddd-supply: digital voltage regulator (see regulator/regulator.txt)
15 - vdda-supply: analog voltage regulator (see regulator/regulator.txt)
22 interrupt-parent = <&gpio0>;
24 reset-gpios = <&gpio0 26 GPIO_ACTIVE_LOW>;
25 vddd-supply = <&foo>;
26 vdda-supply = <&bar>;
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/display/panel/
Dsamsung,s6d16d0.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Linus Walleij <linus.walleij@linaro.org>
13 - $ref: panel-common.yaml#
21 reset-gpios: true
23 vdd1-supply:
24 description: I/O voltage supply
27 - compatible
28 - reg
[all …]
Dsony,acx424akp.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Linus Walleij <linus.walleij@linaro.org>
13 - $ref: panel-common.yaml#
19 reset-gpios: true
20 vddi-supply:
22 enforce-video-mode: true
25 - compatible
26 - reg
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/iio/pressure/
Dbmp085.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Andreas Klinger <ak@it-klinger.de>
16 https://www.bosch-sensortec.com/bst/products/all_products/bmp180
17 https://www.bosch-sensortec.com/bst/products/all_products/bmp280
18 https://www.bosch-sensortec.com/bst/products/all_products/bme280
23 - bosch,bmp085
24 - bosch,bmp180
25 - bosch,bmp280
[all …]
/kernel/linux/linux-5.10/arch/arm/boot/dts/
Dbcm2711-rpi-4-b.dts1 // SPDX-License-Identifier: GPL-2.0
2 /dts-v1/;
4 #include "bcm2835-rpi.dtsi"
5 #include "bcm283x-rpi-usb-peripheral.dtsi"
7 #include <dt-bindings/reset/raspberrypi,firmware-reset.h>
10 compatible = "raspberrypi,4-model-b", "brcm,bcm2711";
15 stdout-path = "serial1:115200n8";
31 led-act {
35 led-pwr {
38 default-state = "keep";
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/iio/amplifiers/
Dadi,hmc425a.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: HMC425A 6-bit Digital Step Attenuator
10 - Michael Hennerich <michael.hennerich@analog.com>
11 - Beniamin Bia <beniamin.bia@analog.com>
15 HMC425A 0.5 dB LSB GaAs MMIC 6-BIT DIGITAL POSITIVE CONTROL ATTENUATOR, 2.2 - 8.0 GHz
16 https://www.analog.com/media/en/technical-documentation/data-sheets/hmc425A.pdf
21 - adi,hmc425a
23 vcc-supply: true
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/display/
Dsimple-framebuffer.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/display/simple-framebuffer.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
11 - Hans de Goede <hdegoede@redhat.com>
14 A simple frame-buffer describes a frame-buffer setup by firmware or
20 sub-nodes of the chosen node (*). Simplefb nodes must be named
37 interaction, then the chosen node stdout-path property should point
42 It is advised that devicetree files contain pre-filled, disabled
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/usb/
Dusb251xb.txt1 Microchip USB 2.0 Hi-Speed Hub Controller
4 Hi-Speed Controller.
7 - compatible : Should be "microchip,usb251xb" or one of the specific types:
11 - reg : I2C address on the selected bus (default is <0x2C>)
14 - reset-gpios : Should specify the gpio for hub reset
15 - vdd-supply : Should specify the phandle to the regulator supplying vdd
16 - skip-config : Skip Hub configuration, but only send the USB-Attach command
17 - vendor-id : Set USB Vendor ID of the hub (16 bit, default is 0x0424)
18 - product-id : Set USB Product ID of the hub (16 bit, default depends on type)
19 - device-id : Set USB Device ID of the hub (16 bit, default is 0x0bb3)
[all …]
/kernel/linux/linux-5.10/arch/x86/include/asm/
Duser_32.h1 /* SPDX-License-Identifier: GPL-2.0 */
8 linux we use the 'trad-core' bfd). There are quite a number of
20 DATA: The data area is stored. We use current->end_text to
21 current->brk to pick up all of the user variables, plus any memory
23 is demand-zero or if a page is totally unused, we just cover the entire
28 current->start_stack, so we round each of these off in order to be able
38 * interacting with the FXSR-format floating point environment. Floating
51 long foo; member
53 long st_space[20]; /* 8*10 bytes for each FP-reg = 80 bytes */
63 long foo; member
[all …]
/kernel/linux/linux-4.19/arch/x86/include/asm/
Duser_32.h1 /* SPDX-License-Identifier: GPL-2.0 */
8 linux we use the 'trad-core' bfd). There are quite a number of
20 DATA: The data area is stored. We use current->end_text to
21 current->brk to pick up all of the user variables, plus any memory
23 is demand-zero or if a page is totally unused, we just cover the entire
28 current->start_stack, so we round each of these off in order to be able
38 * interacting with the FXSR-format floating point environment. Floating
51 long foo; member
53 long st_space[20]; /* 8*10 bytes for each FP-reg = 80 bytes */
63 long foo; member
[all …]
/kernel/linux/linux-4.19/Documentation/kbuild/
Dmodules.txt3 This document describes how to build an out-of-tree kernel module.
9 --- 2.1 Command Syntax
10 --- 2.2 Options
11 --- 2.3 Targets
12 --- 2.4 Building Separate Files
14 --- 3.1 Shared Makefile
15 --- 3.2 Separate Kbuild file and Makefile
16 --- 3.3 Binary Blobs
17 --- 3.4 Building Multiple Modules
19 --- 4.1 Kernel Includes
[all …]
/kernel/linux/linux-4.19/Documentation/media/kapi/
Dv4l2-controls.rst5 ------------
28 for V4L2 drivers and struct v4l2_subdev for sub-device drivers.
32 ------------------------
44 Basic usage for V4L2 and sub-device drivers
45 -------------------------------------------
49 1.1) Add the handler to your driver's top-level struct:
51 .. code-block:: none
59 struct foo_dev *foo;
63 .. code-block:: none
65 v4l2_ctrl_handler_init(&foo->ctrl_handler, nr_of_controls);
[all …]
/kernel/linux/linux-5.10/Documentation/driver-api/media/
Dv4l2-controls.rst1 .. SPDX-License-Identifier: GPL-2.0
7 ------------
31 sub-device drivers.
35 ------------------------
48 Basic usage for V4L2 and sub-device drivers
49 -------------------------------------------
53 .. code-block:: c
55 #include <media/v4l2-ctrls.h>
57 1.1) Add the handler to your driver's top-level struct:
61 .. code-block:: c
[all …]
/kernel/linux/linux-5.10/Documentation/kbuild/
Dmodules.rst5 This document describes how to build an out-of-tree kernel module.
11 --- 2.1 Command Syntax
12 --- 2.2 Options
13 --- 2.3 Targets
14 --- 2.4 Building Separate Files
16 --- 3.1 Shared Makefile
17 --- 3.2 Separate Kbuild file and Makefile
18 --- 3.3 Binary Blobs
19 --- 3.4 Building Multiple Modules
21 --- 4.1 Kernel Includes
[all …]
/kernel/linux/linux-4.19/Documentation/driver-api/
Dpinctl.rst9 - Enumerating and naming controllable pins
11 - Multiplexing of pins, pads, fingers (etc) see below for details
13 - Configuration of pins, pads, fingers (etc), such as software-controlled
14 biasing and driving mode specific pins, such as pull-up/down, open drain,
17 Top-level interface
22 - A pin controller is a piece of hardware, usually a set of registers, that
28 - PINS are equal to pads, fingers, balls or whatever packaging input or
32 be sparse - i.e. there may be gaps in the space with numbers where no
75 .name = "foo",
98 See for example arch/arm/mach-u300/Kconfig for an example.
[all …]
/kernel/linux/linux-5.10/Documentation/driver-api/
Dpinctl.rst9 - Enumerating and naming controllable pins
11 - Multiplexing of pins, pads, fingers (etc) see below for details
13 - Configuration of pins, pads, fingers (etc), such as software-controlled
14 biasing and driving mode specific pins, such as pull-up/down, open drain,
17 Top-level interface
22 - A pin controller is a piece of hardware, usually a set of registers, that
28 - PINS are equal to pads, fingers, balls or whatever packaging input or
32 be sparse - i.e. there may be gaps in the space with numbers where no
75 .name = "foo",
98 See for example arch/arm/mach-u300/Kconfig for an example.
[all …]
/kernel/linux/linux-4.19/arch/arm64/boot/dts/qcom/
Dapq8016-sbc.dtsi16 #include "apq8016-sbc-soc-pins.dtsi"
17 #include "apq8016-sbc-pmic-pins.dtsi"
18 #include <dt-bindings/gpio/gpio.h>
19 #include <dt-bindings/input/input.h>
20 #include <dt-bindings/sound/apq8016-lpass.h>
41 * UART3. This is only for the informational lines i.e. "[FOO]",
42 * the GPIO named lines "GPIO-A" thru "GPIO-L" are the only
59 stdout-path = "serial0";
62 reserved-memory {
67 record-size = <0x20000>;
[all …]
/kernel/linux/linux-5.10/arch/arm64/boot/dts/actions/
Ds900-bubblegum-96.dts1 // SPDX-License-Identifier: (GPL-2.0+ OR MIT)
6 /dts-v1/;
11 compatible = "ucrobotics,bubblegum-96", "actions,s900";
12 model = "Bubblegum-96";
22 stdout-path = "serial5:115200n8";
31 vcc_3v1: vcc-3v1 {
32 compatible = "regulator-fixed";
33 regulator-name = "fixed-3.1V";
34 regulator-min-microvolt = <3100000>;
35 regulator-max-microvolt = <3100000>;
[all …]
/kernel/linux/linux-5.10/arch/arm64/boot/dts/hisilicon/
Dhi6220-hikey.dts1 // SPDX-License-Identifier: GPL-2.0
9 /dts-v1/;
11 #include "hikey-pinctrl.dtsi"
12 #include <dt-bindings/gpio/gpio.h>
16 compatible = "hisilicon,hi6220-hikey", "hisilicon,hi6220";
26 stdout-path = "serial3:115200n8";
32 * 0x05e0,0000 - 0x05ef,ffff: MCU firmware runtime using
33 * 0x05f0,1000 - 0x05f0,1fff: Reboot reason
34 * 0x06df,f000 - 0x06df,ffff: Mailbox message data
35 * 0x0740,f000 - 0x0740,ffff: MCU firmware section
[all …]

12