Home
last modified time | relevance | path

Searched +full:bcm6328 +full:- +full:power +full:- +full:controller (Results 1 – 15 of 15) sorted by relevance

/kernel/linux/linux-5.10/Documentation/devicetree/bindings/power/
Dbrcm,bcm63xx-power.yaml1 # 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 …]
/kernel/linux/linux-5.10/arch/mips/boot/dts/brcm/
Dbcm6328.dtsi1 // SPDX-License-Identifier: GPL-2.0
3 #address-cells = <1>;
4 #size-cells = <1>;
5 compatible = "brcm,bcm6328";
8 #address-cells = <1>;
9 #size-cells = <0>;
11 mips-hpt-frequency = <160000000>;
27 periph_clk: periph-clk {
28 compatible = "fixed-clock";
29 #clock-cells = <0>;
[all …]
Dbcm63268.dtsi1 // SPDX-License-Identifier: GPL-2.0
3 #address-cells = <1>;
4 #size-cells = <1>;
8 #address-cells = <1>;
9 #size-cells = <0>;
11 mips-hpt-frequency = <200000000>;
27 periph_clk: periph-clk {
28 compatible = "fixed-clock";
29 #clock-cells = <0>;
30 clock-frequency = <50000000>;
[all …]
Dbcm6362.dtsi1 // SPDX-License-Identifier: GPL-2.0
3 #address-cells = <1>;
4 #size-cells = <1>;
8 #address-cells = <1>;
9 #size-cells = <0>;
11 mips-hpt-frequency = <200000000>;
27 periph_clk: periph-clk {
28 compatible = "fixed-clock";
29 #clock-cells = <0>;
30 clock-frequency = <50000000>;
[all …]
/kernel/linux/linux-4.19/Documentation/devicetree/bindings/leds/
Dleds-bcm6328.txt1 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/gpio-74x164.txt), or
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 …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/leds/
Dleds-bcm6328.txt1 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/gpio-74x164.txt), or
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 …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/arm/bcm/
Dbrcm,bcm63138.txt1 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 …]
/kernel/linux/linux-4.19/Documentation/devicetree/bindings/arm/bcm/
Dbrcm,bcm63138.txt1 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 …]
/kernel/linux/linux-5.10/drivers/soc/bcm/bcm63xx/
DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
5 bool "BCM63xx power domain driver"
9 This enables support for the BCM63xx power domains controller on
10 BCM6318, BCM6328, BCM6362 and BCM63268 SoCs.
Dbcm63xx-power.c1 // SPDX-License-Identifier: GPL-2.0-or-later
3 * BCM63xx Power Domain Controller Driver
8 #include <dt-bindings/soc/bcm6318-pm.h>
9 #include <dt-bindings/soc/bcm6328-pm.h>
10 #include <dt-bindings/soc/bcm6362-pm.h>
11 #include <dt-bindings/soc/bcm63268-pm.h>
21 struct bcm63xx_power *power; member
41 struct bcm63xx_power *power = pmd->power; in bcm63xx_power_get_state() local
43 if (!pmd->mask) { in bcm63xx_power_get_state()
45 return -EINVAL; in bcm63xx_power_get_state()
[all …]
/kernel/linux/linux-4.19/Documentation/devicetree/bindings/mips/brcm/
Dsoc.txt5 - 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 …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/mips/brcm/
Dsoc.txt5 - 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 …]
/kernel/linux/linux-4.19/drivers/leds/
DKconfig39 See Documentation/ABI/testing/sysfs-class-led for details.
48 This option enables support for on-chip LED drivers found on Marvell
70 module will be called leds-apu.
78 controller. V4L2 flash API is provided as well if
82 tristate "LED Support for Broadcom BCM6328"
87 This option enables support for LEDs connected to the BCM6328
88 LED HW controller accessed via MMIO registers.
97 LED HW controller accessed via MMIO registers.
119 will be called leds-cr0014114.
137 TI LM3533 Lighting Power chips.
[all …]
/kernel/linux/linux-5.10/drivers/leds/
DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
50 See Documentation/ABI/testing/sysfs-class-led for details.
59 This option enables support for on-chip LED drivers found on Marvell
76 This option enables support for the AN30259A 3-channel
80 will be called leds-an30259a.
90 If you're looking for APU2/3, use the pcengines-apu2 driver.
94 module will be called leds-apu.
103 Controller.
113 controller. V4L2 flash API is provided as well if
120 This option enables support for the AW2013 3-channel
[all …]
/kernel/linux/linux-5.10/drivers/phy/broadcom/
Dphy-bcm63xx-usbh.c1 // SPDX-License-Identifier: GPL-2.0-or-later
3 * BCM6328 USBH PHY Controller Driver
75 /* PLLC bits to set/clear for power on */
79 /* Setup bits to set/clear for power on */
86 /* Test Port Control value to set if non-zero */
107 [USBH_BRT_CONTROL1] = -1,
108 [USBH_BRT_CONTROL2] = -1,
109 [USBH_BRT_STATUS1] = -1,
110 [USBH_BRT_STATUS2] = -1,
115 [USBH_GENERIC_CONTROL] = -1,
[all …]