Searched +full:firmware +full:- +full:gpios (Results 1 – 25 of 36) sorted by relevance
12
| /Documentation/devicetree/bindings/net/nfc/ |
| D | nxp,pn544.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Krzysztof Kozlowski <krzk@kernel.org>
14 const: nxp,pn544-i2c
22 enable-gpios:
26 firmware-gpios:
27 description: Output GPIO pin used to enter firmware download mode
31 - compatible
32 - reg
[all …]
|
| D | nxp,nci.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Krzysztof Kozlowski <krzk@kernel.org>
15 - const: nxp,nxp-nci-i2c
16 - items:
17 - enum:
18 - nxp,nq310
19 - nxp,pn547
20 - const: nxp,nxp-nci-i2c
[all …]
|
| D | samsung,s3fwrn5.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Krzysztof Kozlowski <krzk@kernel.org>
15 - samsung,s3fwrn5-i2c
16 - samsung,s3fwrn82
18 en-gpios:
32 wake-gpios:
35 Output GPIO pin used to enter firmware mode and sleep/wakeup control
37 s3fwrn5,en-gpios:
[all …]
|
| /Documentation/devicetree/bindings/net/bluetooth/ |
| D | amlogic,w155s2-bt.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
4 ---
5 $id: http://devicetree.org/schemas/net/bluetooth/amlogic,w155s2-bt.yaml#
6 $schema: http://devicetree.org/meta-schemas/core.yaml#
11 The W155S2 is an Amlogic Bluetooth and Wi-Fi combo chip. It works on
12 the standard H4 protocol via a 4-wire UART interface, with baud rates
16 - Yang Li <yang.li@amlogic.com>
21 - items:
22 - enum:
23 - amlogic,w265s1-bt
[all …]
|
| D | qualcomm-bluetooth.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/net/bluetooth/qualcomm-bluetooth.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Balakrishna Godavarthi <quic_bgodavar@quicinc.com>
11 - Rocky Liao <quic_rjliao@quicinc.com>
14 This binding describes Qualcomm UART-attached bluetooth chips.
19 - qcom,qca2066-bt
20 - qcom,qca6174-bt
21 - qcom,qca9377-bt
[all …]
|
| D | realtek,bluetooth.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Vasily Khoruzhick <anarsoul@gmail.com>
11 - Alistair Francis <alistair@alistair23.me>
16 H5 protocol with few extra commands to upload firmware and change
22 - enum:
23 - realtek,rtl8723bs-bt
24 - realtek,rtl8723cs-bt
25 - realtek,rtl8723ds-bt
[all …]
|
| /Documentation/devicetree/bindings/tpm/ |
| D | tpm-common.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/tpm/tpm-common.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Lukas Wunner <lukas@wunner.de>
14 pattern: '^tpm(@[0-9a-f]+)?$'
23 linux,sml-base:
25 base address of reserved memory allocated for firmware event log
28 linux,sml-size:
30 size of reserved memory allocated for firmware event log
[all …]
|
| /Documentation/devicetree/bindings/fpga/ |
| D | lattice-ice40-fpga-mgr.txt | 4 - compatible: Should contain "lattice,ice40-fpga-mgr"
5 - reg: SPI chip select
6 - spi-max-frequency: Maximum SPI frequency (>=1000000, <=25000000)
7 - cdone-gpios: GPIO input connected to CDONE pin
8 - reset-gpios: Active-low GPIO output connected to CRESET_B pin. Note
12 bus until the firmware is loaded.
16 compatible = "lattice,ice40-fpga-mgr";
18 spi-max-frequency = <1000000>;
19 cdone-gpios = <&gpio 24 GPIO_ACTIVE_HIGH>;
20 reset-gpios = <&gpio 22 GPIO_ACTIVE_LOW>;
|
| /Documentation/devicetree/bindings/input/touchscreen/ |
| D | silead,gsl1680.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Dmitry Torokhov <dmitry.torokhov@gmail.com>
13 - $ref: touchscreen.yaml#
18 - silead,gsl1680
19 - silead,gsl1688
20 - silead,gsl3670
21 - silead,gsl3675
22 - silead,gsl3692
[all …]
|
| /Documentation/devicetree/bindings/media/ |
| D | samsung,s5c73m3.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
11 - Sylwester Nawrocki <s.nawrocki@samsung.com>
14 The S5C73M3 camera ISP supports MIPI CSI-2 and parallel (ITU-R BT.656)
16 SPI bus is used, mostly for transferring the firmware to and from the
31 clock-names:
33 - const: cis_extclk
35 clock-frequency:
[all …]
|
| /Documentation/devicetree/bindings/net/ |
| D | ti,cc1352p7.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
13 - Ayush Singh <ayushdevel1325@gmail.com>
21 - description: high-frequency main system (MCU and peripherals) clock
22 - description: low-frequency system clock
24 clock-names:
26 - const: sclk_hf
27 - const: sclk_lf
29 reset-gpios:
[all …]
|
| /Documentation/devicetree/bindings/firmware/ |
| D | intel,ixp4xx-network-processing-engine.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
4 ---
5 $id: http://devicetree.org/schemas/firmware/intel,ixp4xx-network-processing-engine.yaml#
6 $schema: http://devicetree.org/meta-schemas/core.yaml#
11 - Linus Walleij <linus.walleij@linaro.org>
15 processor that can load a firmware to perform offloading of networking
24 - items:
25 - const: intel,ixp4xx-network-processing-engine
29 - description: NPE0 (NPE-A) register range
30 - description: NPE1 (NPE-B) register range
[all …]
|
| /Documentation/devicetree/bindings/mtd/ |
| D | mtd-physmap.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/mtd/mtd-physmap.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: CFI or JEDEC memory-mapped NOR flash, MTD-RAM (NVRAM...)
10 - Rob Herring <robh@kernel.org>
17 - $ref: mtd.yaml#
18 - $ref: /schemas/memory-controllers/mc-peripheral-props.yaml#
23 - items:
24 - enum:
[all …]
|
| /Documentation/devicetree/bindings/net/wireless/ |
| D | brcm,bcm4329-fmac.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/net/wireless/brcm,bcm4329-fmac.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Arend van Spriel <arend@broadcom.com>
19 - $ref: ieee80211.yaml#
24 - items:
25 - enum:
26 - brcm,bcm43143-fmac
27 - brcm,bcm4341b0-fmac
[all …]
|
| /Documentation/devicetree/bindings/sound/ |
| D | adi,adau1701.txt | 5 - compatible: Should contain "adi,adau1701"
6 - reg: The i2c address. Value depends on the state of ADDR0
11 - reset-gpio: A GPIO spec to define which pin is connected to the
14 - adi,pll-mode-gpios: An array of two GPIO specs to describe the GPIOs
18 firmware is loaded.
19 - adi,pin-config: An array of 12 numerical values selecting one of the
23 - avdd-supply: Power supply for AVDD, providing 3.3V
24 - dvdd-supply: Power supply for DVDD, providing 3.3V
32 reset-gpio = <&gpio 23 0>;
33 avdd-supply = <&vdd_3v3_reg>;
[all …]
|
| D | infineon,peb2466.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Herve Codina <herve.codina@bootlin.com>
13 The Infineon PEB2466 codec is a programmable DSP-based four channels codec
16 The time-slots used by the codec must be set and so, the properties
17 'dai-tdm-slot-num', 'dai-tdm-slot-width', 'dai-tdm-slot-tx-mask' and
18 'dai-tdm-slot-rx-mask' must be present in the sound card node for sub-nodes
19 that involve the codec. The codec uses one 8bit time-slot per channel.
20 'dai-tdm-tdm-slot-with' must be set to 8.
[all …]
|
| /Documentation/devicetree/bindings/misc/ |
| D | ge-achc.yaml | 1 # SPDX-License-Identifier: GPL-2.0 OR BSD-2-Clause
5 ---
6 $id: http://devicetree.org/schemas/misc/ge-achc.yaml#
7 $schema: http://devicetree.org/meta-schemas/core.yaml#
18 - Sebastian Reichel <sre@kernel.org>
23 - const: ge,achc
24 - const: nxp,kinetis-k20
29 vdd-supply:
32 vdda-supply:
37 - description: Control interface
[all …]
|
| /Documentation/devicetree/bindings/usb/ |
| D | ti,tps6598x.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Texas Instruments 6598x Type-C Port Switch and Power Delivery controller
10 - Bryan O'Donoghue <bryan.odonoghue@linaro.org>
13 Texas Instruments 6598x Type-C Port Switch and Power Delivery controller
21 - ti,tps6598x
22 - apple,cd321x
23 - ti,tps25750
28 - description: main PD controller address
[all …]
|
| /Documentation/devicetree/bindings/pci/ |
| D | pci.txt | 3 PCI Bus Binding to: IEEE Std 1275-1994
4 https://www.devicetree.org/open-firmware/bindings/pci/pci2_1.pdf
8 Open Firmware Recommended Practice: Interrupt Mapping
9 https://www.devicetree.org/open-firmware/practice/imap/imap0_9d.pdf
14 - linux,pci-domain:
21 - max-link-speed:
27 - reset-gpios:
30 - supports-clkreq:
34 not to advertise ASPM L1 Sub-States support if there is no CLKREQ signal.
36 PCI-PCI Bridge properties
[all …]
|
| /Documentation/devicetree/bindings/soc/qcom/ |
| D | qcom,pmic-glink.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/soc/qcom/qcom,pmic-glink.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Qualcomm PMIC GLINK firmware interface for battery management, USB
8 Type-C and other things.
11 - Bjorn Andersson <andersson@kernel.org>
15 platforms and implement USB Type-C handling and battery management. This
17 firmware and connect it's resources to those described in the Devicetree,
18 particularly the USB Type-C controllers relationship with USB and DisplayPort
[all …]
|
| /Documentation/fb/ |
| D | metronomefb.rst | 10 is from E-Ink Corporation. It is intended to be used to drive the E-Ink
11 Vizplex display media. E-Ink hosts some details of this controller and the
12 display media here http://www.e-ink.com/products/matrix/metronome.html .
17 The display and error status are each pulled through individual GPIOs.
21 PXA board used in the AM-200 EPD devkit. This example is am200epd.c
25 be delivered from userspace via the firmware class interface. The waveform file
28 which would typically go into /lib/firmware/metronome.wbf depending on your
|
| /Documentation/firmware-guide/acpi/ |
| D | enumeration.rst | 1 .. SPDX-License-Identifier: GPL-2.0
13 that are accessed through memory-mapped registers.
15 In order to support this and re-use the existing drivers as much as
18 - Devices that have no bus connector resource are represented as
21 - Devices behind real busses where there is a connector resource
34 This means that when ACPI_HANDLE(dev) returns non-NULL the device was
36 device-specific configuration. There is an example of this below.
43 for the device and add supported ACPI IDs. If this same IP-block is used on
44 some other non-ACPI platform, the driver might work out of the box or needs
64 configuring GPIOs it can get its ACPI handle and extract this information
[all …]
|
| D | chromeos-acpi-device.rst | 1 .. SPDX-License-Identifier: GPL-2.0
11 .. flat-table:: Supported ACPI Objects
13 :header-rows: 1
15 * - Object
16 - Description
18 * - CHSW
19 - Chrome OS switch positions
21 * - HWID
22 - Chrome OS hardware ID
24 * - FWID
[all …]
|
| /Documentation/driver-api/gpio/ |
| D | intro.rst | 10 GPIOs in drivers, and how to write a driver for a device that provides GPIOs
17 A "General Purpose Input/Output" (GPIO) is a flexible software-controlled
22 which GPIOs. Drivers can be written generically, so that board setup code
25 System-on-Chip (SOC) processors heavily rely on GPIOs. In some cases, every
26 non-dedicated pin can be configured as a GPIO; and most chips have at least
28 provide GPIOs; multifunction chips like power managers, and audio codecs
31 Most PC southbridges have a few dozen GPIO-capable pins (with only the BIOS
32 firmware knowing how they're used).
34 The exact capabilities of GPIOs vary between systems. Common options:
36 - Output values are writable (high=1, low=0). Some chips also have
[all …]
|
| D | board.rst | 5 This document explains how GPIOs can be assigned to given devices and functions.
9 Kconfig. Then, how GPIOs are mapped depends on what the platform uses to
14 -----------
15 GPIOs can easily be mapped to devices and functions in the device tree. The
16 exact way to do it depends on the GPIO controller providing the GPIOs, see the
19 GPIOs mappings are defined in the consumer device's node, in a property named
20 <function>-gpios, where <function> is the function the driver will request
26 led-gpios = <&gpio 15 GPIO_ACTIVE_HIGH>, /* red */
30 power-gpios = <&gpio 1 GPIO_ACTIVE_LOW>;
33 Properties named <function>-gpio are also considered valid and old bindings use
[all …]
|
12