Searched +full:bcm6328 +full:- +full:power +full:- +full:controller (Results 1 – 10 of 10) sorted by relevance
/freebsd/sys/contrib/device-tree/src/mips/brcm/ |
H A D | bcm6328.dtsi | 1 // SPDX-License-Identifier: GPL-2.0 3 #include "dt-bindings/clock/bcm6328-clock.h" 4 #include "dt-bindings/reset/bcm6328-reset.h" 5 #include "dt-bindings/soc/bcm6328-pm.h" 8 #address-cells = <1>; 9 #size-cells = <1>; 10 compatible = "brcm,bcm6328"; 13 #address-cells = <1>; 14 #size-cells = <0>; 16 mips-hpt-frequency = <160000000>; [all …]
|
H A D | bcm63268.dtsi | 1 // SPDX-License-Identifier: GPL-2.0 3 #include "dt-bindings/clock/bcm63268-clock.h" 4 #include "dt-bindings/reset/bcm63268-reset.h" 5 #include "dt-bindings/soc/bcm63268-pm.h" 8 #address-cells = <1>; 9 #size-cells = <1>; 13 #address-cells = <1>; 14 #size-cells = <0>; 16 mips-hpt-frequency = <200000000>; 32 periph_osc: periph-osc { [all …]
|
H A D | bcm6362.dtsi | 1 // SPDX-License-Identifier: GPL-2.0 3 #include "dt-bindings/clock/bcm6362-clock.h" 4 #include "dt-bindings/reset/bcm6362-reset.h" 5 #include "dt-bindings/soc/bcm6362-pm.h" 8 #address-cells = <1>; 9 #size-cells = <1>; 13 #address-cells = <1>; 14 #size-cells = <0>; 16 mips-hpt-frequency = <200000000>; 32 periph_osc: periph-osc { [all …]
|
/freebsd/sys/contrib/device-tree/Bindings/power/ |
H A D | brcm,bcm63xx-power.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/power/brcm,bcm63xx-power.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: BCM63xx power domain driver 10 - Álvaro Fernández Rojas <noltari@gmail.com> 13 BCM6318, BCM6328, BCM6362 and BCM63268 SoCs have a power domain controller 14 to enable/disable certain components in order to save power. 19 - enum: 20 - brcm,bcm6318-power-controller [all …]
|
/freebsd/sys/contrib/device-tree/Bindings/leds/ |
H A D | leds-bcm6328.txt | 1 LEDs connected to Broadcom BCM6328 controller 3 This controller is present on BCM6318, BCM6328, BCM6362 and BCM63268. 6 controller), which can either be controlled by software (exporting the 74x164 7 as spi-gpio. See Documentation/devicetree/bindings/gpio/fairchild,74hc595.yaml), 10 exporting the 74x164 as spi-gpio prevents those LEDs to be hardware 13 BCM6328 LED controller has a HWDIS register, which controls whether a LED 18 explained later in brcm,link-signal-sources). Even if a LED is hardware 24 - compatible : should be "brcm,bcm6328-leds". 25 - #address-cells : must be 1. 26 - #size-cells : must be 0. [all …]
|
H A D | leds-bcm6328.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause 3 --- 4 $id: http://devicetree.org/schemas/leds/leds-bcm6328.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: LEDs connected to Broadcom BCM6328 controller 10 - Álvaro Fernández Rojas <noltari@gmail.com> 13 This controller is present on BCM6318, BCM6328, BCM6362 and BCM63268. 16 controller), which can either be controlled by software (exporting the 74x164 17 as spi-gpio. See 21 exporting the 74x164 as spi-gpio prevents those LEDs to be hardware [all …]
|
/freebsd/sys/contrib/device-tree/Bindings/arm/bcm/ |
H A D | brcm,bcm63138.txt | 1 Broadcom BCM63138 DSL System-on-a-Chip device tree bindings 2 ----------------------------------------------------------- 4 Boards compatible with the BCM63138 DSL System-on-a-Chip should have the 12 initialization as well as a 'resets' phandle to the correct PMB controller as 13 defined in reset/brcm,bcm63138-pmb.txt for this secondary CPU, and an 14 'enable-method' property. 17 - compatible: should be "brcm,bcm63138-bootlut" 18 - reg: register base address and length for the Boot Lookup table 21 - enable-method: should be "brcm,bcm63138" 24 - enable-method: should be "brcm,bcm63138" [all …]
|
/freebsd/sys/contrib/device-tree/Bindings/mips/brcm/ |
H A D | soc.txt | 5 - compatible: "brcm,bcm3368", "brcm,bcm3384", "brcm,bcm33843" 6 "brcm,bcm3384-viper", "brcm,bcm33843-viper" 7 "brcm,bcm6328", "brcm,bcm6358", "brcm,bcm6362", "brcm,bcm6368", 12 The experimental -viper variants are for running Linux on the 3384's 15 Power management 16 ---------------- 18 For power management (particularly, S2/S3/S5 system suspend), the following SoC 21 = Always-On control block (AON CTRL) 23 This hardware provides control registers for the "always-on" (even in low-power 24 modes) hardware, such as the Power Management State Machine (PMSM). [all …]
|
/freebsd/sys/contrib/device-tree/Bindings/usb/ |
H A D | generic-ohci.yaml | 1 # SPDX-License-Identifier: GPL-2.0 3 --- 4 $id: http://devicetree.org/schemas/usb/generic-ohci.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: USB OHCI Controller 10 - Gre [all...] |
H A D | generic-ehci.yaml | 1 # SPDX-License-Identifier: GPL-2.0 3 --- 4 $id: http://devicetree.org/schemas/usb/generic-ehci.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: USB EHCI Controller 10 - Greg Kroah-Hartman <gregkh@linuxfoundation.org> 13 - $ref: usb-hcd.yaml 14 - if: 19 const: ibm,usb-ehci-440epx 28 - items: [all …]
|