| /linux-5.10/Documentation/devicetree/bindings/arm/bcm/ |
| D | raspberrypi,bcm2835-firmware.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/arm/bcm/raspberrypi,bcm2835-firmware.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Raspberry Pi VideoCore firmware driver
10 - Eric Anholt <eric@anholt.net>
11 - Stefan Wahren <wahrenst@gmx.net>
17 const: raspberrypi,bcm2835-firmware
20 - compatible
25 - const: raspberrypi,bcm2835-firmware
[all …]
|
| /linux-5.10/Documentation/devicetree/bindings/arm/ |
| D | arm,scpi.txt | 2 ----------------------------------------------------------
4 Firmware implementing the SCPI described in ARM document number ARM DUI 0922B
10 - compatible : should be
12 * "arm,scpi-pre-1.0" : For implementations complying to all
14 - mboxes: List of phandle and mailbox channel specifiers
15 All the channels reserved by remote SCP firmware for use by
17 - shmem : List of phandle pointing to the shared memory(SHM) area between the
26 Clock bindings for the clocks based on SCPI Message Protocol
27 ------------------------------------------------------------
34 - compatible : should be "arm,scpi-clocks"
[all …]
|
| /linux-5.10/Documentation/devicetree/bindings/clock/ |
| D | xlnx,zynqmp-clk.txt | 1 --------------------------------------------------------------------------
3 Zynq MPSoC firmware interface
4 --------------------------------------------------------------------------
7 as clock provider for all clock consumers of PS clocks.
12 - #clock-cells: Must be 1
13 - compatible: Must contain: "xlnx,zynqmp-clk"
14 - clocks: List of clock specifiers which are external input
15 clocks to the given clock controller. Please refer
16 the next section to find the input clocks for a
18 - clock-names: List of clock names which are exteral input clocks
[all …]
|
| D | xlnx,versal-clk.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/clock/xlnx,versal-clk.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Michal Simek <michal.simek@xilinx.com>
11 - Jolly Shah <jolly.shah@xilinx.com>
12 - Rajan Vaja <rajan.vaja@xilinx.com>
17 provider for all clock consumers of PS clocks.
23 const: xlnx,versal-clk
25 "#clock-cells":
[all …]
|
| /linux-5.10/drivers/clk/keystone/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
16 If you wish to use clock resources from the PMMC firmware, say Y.
20 bool "Probe available clocks from firmware"
24 Forces the TI SCI clock driver to probe available clocks from the
25 firmware. By default, only the used clocks are probed from DT.
27 increase the boot time of the device. If you want the clocks probed
28 from firmware, say Y. Otherwise, say N.
36 clocks on TI's K2 and K3 SoCs.
|
| /linux-5.10/Documentation/devicetree/bindings/net/ |
| D | qualcomm-bluetooth.txt | 2 ---------------------
11 - compatible: should contain one of the following:
12 * "qcom,qca6174-bt"
13 * "qcom,qca9377-bt"
14 * "qcom,wcn3990-bt"
15 * "qcom,wcn3991-bt"
16 * "qcom,wcn3998-bt"
17 * "qcom,qca6390-bt"
19 Optional properties for compatible string qcom,qca6174-bt:
21 - enable-gpios: gpio specifier used to enable chip
[all …]
|
| /linux-5.10/Documentation/devicetree/bindings/firmware/ |
| D | qcom,scm.txt | 3 Qualcomm processors include an interface to communicate to the secure firmware.
5 can include CPU power up/down, HDCP requests, loading of firmware, and other
9 - compatible: must contain one of the following:
10 * "qcom,scm-apq8064"
11 * "qcom,scm-apq8084"
12 * "qcom,scm-ipq4019"
13 * "qcom,scm-ipq806x"
14 * "qcom,scm-ipq8074"
15 * "qcom,scm-msm8660"
16 * "qcom,scm-msm8916"
[all …]
|
| /linux-5.10/drivers/clk/bcm/ |
| D | clk-raspberrypi.c | 1 // SPDX-License-Identifier: GPL-2.0+
3 * Raspberry Pi driver for firmware controlled clocks
5 * Even though clk-bcm2835 provides an interface to the hardware registers for
6 * the system clocks we've had to factor out 'pllb' as the firmware 'owns' it.
8 * over-temperature and under-voltage protections provided by the firmware.
14 #include <linux/clk-provider.h>
19 #include <soc/bcm2835/raspberrypi-firmware.h>
53 [RPI_FIRMWARE_PIXEL_BVB_CLK_ID] = "pixel-bvb",
61 struct rpi_firmware *firmware; member
74 * Structure of the message passed to Raspberry Pi's firmware in order to
[all …]
|
| /linux-5.10/arch/arm/boot/dts/ |
| D | bcm2711-rpi-4-b.dts | 1 // 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";
38 default-state = "keep";
39 linux,default-trigger = "default-on";
43 wifi_pwrseq: wifi-pwrseq {
[all …]
|
| D | meson8.dtsi | 1 // SPDX-License-Identifier: GPL-2.0 OR MIT
6 #include <dt-bindings/clock/meson8-ddr-clkc.h>
7 #include <dt-bindings/clock/meson8b-clkc.h>
8 #include <dt-bindings/gpio/meson8-gpio.h>
9 #include <dt-bindings/power/meson8-power.h>
10 #include <dt-bindings/reset/amlogic,meson8b-clkc-reset.h>
11 #include <dt-bindings/reset/amlogic,meson8b-reset.h>
19 #address-cells = <1>;
20 #size-cells = <0>;
24 compatible = "arm,cortex-a9";
[all …]
|
| /linux-5.10/Documentation/devicetree/bindings/display/msm/ |
| D | gpu.txt | 4 - compatible: "qcom,adreno-XYZ.W", "qcom,adreno" or
5 "amd,imageon-XYZ.W", "amd,imageon"
6 for example: "qcom,adreno-306.0", "qcom,adreno"
9 with the chip-id.
11 - reg: Physical base address and length of the controller's registers.
12 - interrupts: The interrupt signal from the gpu.
13 - clocks: device clocks (if applicable)
14 See ../clocks/clock-bindings.txt for details.
15 - clock-names: the following clocks are required by a3xx, a4xx and a5xx
20 For GMU attached devices the GPU clocks are not used and are not required. The
[all …]
|
| /linux-5.10/Documentation/devicetree/bindings/remoteproc/ |
| D | ti,omap-remoteproc.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only or BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/remoteproc/ti,omap-remoteproc.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Suman Anna <s-anna@ti.com>
13 The OMAP family of SoCs usually have one or more slave processor sub-systems
14 that are used to offload some of the processor-intensive tasks, or to manage
17 The processor cores in the sub-system are usually behind an IOMMU, and may
18 contain additional sub-modules like Internal RAM and/or ROMs, L1 and/or L2
21 The OMAP SoCs usually have a DSP processor sub-system and/or an IPU processor
[all …]
|
| /linux-5.10/Documentation/devicetree/bindings/media/ |
| D | qcom,sdm845-venus.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
4 ---
5 $id: "http://devicetree.org/schemas/media/qcom,sdm845-venus.yaml#"
6 $schema: "http://devicetree.org/meta-schemas/core.yaml#"
11 - Stanimir Varbanov <stanimir.varbanov@linaro.org>
19 const: qcom,sdm845-venus
27 power-domains:
30 clocks:
33 clock-names:
35 - const: core
[all …]
|
| D | qcom,msm8996-venus.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
4 ---
5 $id: "http://devicetree.org/schemas/media/qcom,msm8996-venus.yaml#"
6 $schema: "http://devicetree.org/meta-schemas/core.yaml#"
11 - Stanimir Varbanov <stanimir.varbanov@linaro.org>
19 const: qcom,msm8996-venus
27 power-domains:
30 clocks:
33 clock-names:
35 - const: core
[all …]
|
| D | qcom,msm8916-venus.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
4 ---
5 $id: "http://devicetree.org/schemas/media/qcom,msm8916-venus.yaml#"
6 $schema: "http://devicetree.org/meta-schemas/core.yaml#"
11 - Stanimir Varbanov <stanimir.varbanov@linaro.org>
19 const: qcom,msm8916-venus
27 power-domains:
30 clocks:
33 clock-names:
35 - const: core
[all …]
|
| D | qcom,sdm845-venus-v2.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
4 ---
5 $id: "http://devicetree.org/schemas/media/qcom,sdm845-venus-v2.yaml#"
6 $schema: "http://devicetree.org/meta-schemas/core.yaml#"
11 - Stanimir Varbanov <stanimir.varbanov@linaro.org>
19 const: qcom,sdm845-venus-v2
27 power-domains:
31 power-domain-names:
35 - const: venus
36 - const: vcodec0
[all …]
|
| D | qcom,sc7180-venus.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
4 ---
5 $id: "http://devicetree.org/schemas/media/qcom,sc7180-venus.yaml#"
6 $schema: "http://devicetree.org/meta-schemas/core.yaml#"
11 - Stanimir Varbanov <stanimir.varbanov@linaro.org>
19 const: qcom,sc7180-venus
27 power-domains:
31 power-domain-names:
35 - const: venus
36 - const: vcodec0
[all …]
|
| /linux-5.10/drivers/media/platform/exynos4-is/ |
| D | fimc-is.c | 1 // SPDX-License-Identifier: GPL-2.0-only
3 * Samsung EXYNOS4x12 FIMC-IS (Imaging Subsystem) driver
16 #include <linux/firmware.h>
30 #include <media/videobuf2-dma-contig.h>
32 #include "media-dev.h"
33 #include "fimc-is.h"
34 #include "fimc-is-command.h"
35 #include "fimc-is-errno.h"
36 #include "fimc-is-i2c.h"
37 #include "fimc-is-param.h"
[all …]
|
| /linux-5.10/drivers/clk/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0
76 These multi-function devices have two fixed-rate oscillators, clocked at 32KHz each.
86 multi-function device has one fixed-rate oscillator, clocked
93 This driver provides support for clocks that are controlled
94 by firmware that implements the SCMI interface.
97 firmware providing all the clock controls.
103 This driver provides support for clocks that are controlled
104 by firmware that implements the SCPI interface.
107 firmware providing all the clock controls.
117 be pre-programmed to support other configurations and features not yet
[all …]
|
| /linux-5.10/drivers/firmware/ |
| D | raspberrypi.c | 1 // SPDX-License-Identifier: GPL-2.0
3 * Defines interfaces for interacting wtih the Raspberry Pi firmware's
9 #include <linux/dma-mapping.h>
15 #include <soc/bcm2835/raspberrypi-firmware.h>
37 complete(&fw->c); in response_callback()
41 * Sends a request to the firmware through the BCM2835 mailbox driver,
53 reinit_completion(&fw->c); in rpi_firmware_transaction()
54 ret = mbox_send_message(fw->chan, &message); in rpi_firmware_transaction()
56 if (wait_for_completion_timeout(&fw->c, HZ)) { in rpi_firmware_transaction()
59 ret = -ETIMEDOUT; in rpi_firmware_transaction()
[all …]
|
| /linux-5.10/Documentation/devicetree/bindings/sound/ |
| D | fsl,easrc.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Shengjiu Wang <shengjiu.wang@nxp.com>
17 const: fsl,imx8mn-easrc
25 clocks:
27 - description: Peripheral clock
29 clock-names:
31 - const: mem
36 dma-names:
[all …]
|
| /linux-5.10/Documentation/devicetree/bindings/display/ |
| D | simple-framebuffer.yaml | 1 # 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 …]
|
| /linux-5.10/Documentation/devicetree/bindings/dma/ |
| D | brcm,bcm2835-dma.txt | 5 Some arbitrary channels are used by the firmware
6 (1,3,6,7 in the current firmware version).
11 - compatible: Should be "brcm,bcm2835-dma".
12 - reg: Should contain DMA registers location and length.
13 - interrupts: Should contain the DMA interrupts associated
15 - interrupt-names: Should contain the names of the interrupt
17 Use "dma-shared-all" for the common interrupt line
19 - #dma-cells: Must be <1>, the cell in the dmas property of the
21 - brcm,dma-channel-mask: Bit mask representing the channels
22 not used by the firmware in ascending order,
[all …]
|
| /linux-5.10/Documentation/devicetree/bindings/net/wireless/ |
| D | qcom,ath10k.txt | 4 - compatible: Should be one of the following:
6 * "qcom,ipq4019-wifi"
7 * "qcom,wcn3990-wifi"
10 data along with board specific data via "qcom,ath10k-calibration-data".
13 AHB based devices (i.e. ipq4019) uses compatible string "qcom,ipq4019-wifi"
15 "qcom,ath10k-calibration-data"). It uses "qcom,ath10k-pre-calibration-data"
18 In general, entry "qcom,ath10k-pre-calibration-data" and
19 "qcom,ath10k-calibration-data" conflict with each other and only one
22 SNOC based devices (i.e. wcn3990) uses compatible string "qcom,wcn3990-wifi".
24 - reg: Address and length of the register set for the device.
[all …]
|
| /linux-5.10/Documentation/arm64/ |
| D | arm-acpi.rst | 22 industry-standard ARMv8 servers, they also apply to more than one operating
24 ACPI and Linux only, on an ARMv8 system -- that is, what Linux expects of
29 ----------------
32 exist in Linux for describing non-enumerable hardware, after all. In this
39 - ACPI’s byte code (AML) allows the platform to encode hardware behavior,
44 - ACPI’s OSPM defines a power management model that constrains what the
48 - In the enterprise server environment, ACPI has established bindings (such
51 and x86 would end up using completely different code paths in both firmware
54 - Choosing a single interface to describe the abstraction between a platform
60 - The new ACPI governance process works well and Linux is now at the same
[all …]
|