-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge tag 'amlogic-dt64' of git://git.kernel.org/pub/scm/linux/kernel…
…/git/khilman/linux-amlogic into next/late Pull "Amlogic 64-bit DT changes for v4.9" from Kevin Hilman: - add watchdog, reset, IR remote, PWM - add secure monitor and eFuse - add always-on (AO) domain clock and reset * tag 'amlogic-dt64' of git://git.kernel.org/pub/scm/linux/kernel/git/khilman/linux-amlogic: ARM64: dts: amlogic: gxbb: Enable NVMEM documentation: Add nvmem bindings documentation ARM64: dts: amlogic: gxbb: Enable secure monitor documentation: Add secure monitor bindings documentation ARM64: dts: meson-gxbb: Add PWM pinctrl nodes ARM64: dts: meson-gxbb: Enable the the IR decoder on supported boards ARM64: dts: meson-gxbb: Add Infrared Remote Controller decoder dt-bindings: media: meson-ir: Add Meson8b and GXBB compatible strings ARM64: dts: amlogic: add the input pin for the IR remote ARM64: dts: meson-gxbb: Add GXBB AO Clock and Reset node clk: meson: Fix invalid use of sizeof in gxbb_aoclkc_probe() clk: meson: Add GXBB AO Clock and Reset controller driver dt-bindings: clock: reset: Add GXBB AO Clock and Reset Bindings ARM64: DTS: meson-gxbb: switch ethernet to real clock ARM64: dts: amlogic: meson-gxbb: Add watchdog node
- Loading branch information
Showing
12 changed files
with
575 additions
and
3 deletions.
There are no files selected for viewing
45 changes: 45 additions & 0 deletions
45
Documentation/devicetree/bindings/clock/amlogic,gxbb-aoclkc.txt
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,45 @@ | ||
* Amlogic GXBB AO Clock and Reset Unit | ||
|
||
The Amlogic GXBB AO clock controller generates and supplies clock to various | ||
controllers within the Always-On part of the SoC. | ||
|
||
Required Properties: | ||
|
||
- compatible: should be "amlogic,gxbb-aoclkc" | ||
- reg: physical base address of the clock controller and length of memory | ||
mapped region. | ||
|
||
- #clock-cells: should be 1. | ||
|
||
Each clock is assigned an identifier and client nodes can use this identifier | ||
to specify the clock which they consume. All available clocks are defined as | ||
preprocessor macros in the dt-bindings/clock/gxbb-aoclkc.h header and can be | ||
used in device tree sources. | ||
|
||
- #reset-cells: should be 1. | ||
|
||
Each reset is assigned an identifier and client nodes can use this identifier | ||
to specify the reset which they consume. All available resets are defined as | ||
preprocessor macros in the dt-bindings/reset/gxbb-aoclkc.h header and can be | ||
used in device tree sources. | ||
|
||
Example: AO Clock controller node: | ||
|
||
clkc_AO: clock-controller@040 { | ||
compatible = "amlogic,gxbb-aoclkc"; | ||
reg = <0x0 0x040 0x0 0x4>; | ||
#clock-cells = <1>; | ||
#reset-cells = <1>; | ||
}; | ||
|
||
Example: UART controller node that consumes the clock and reset generated | ||
by the clock controller: | ||
|
||
uart_AO: serial@4c0 { | ||
compatible = "amlogic,meson-uart"; | ||
reg = <0x4c0 0x14>; | ||
interrupts = <0 90 1>; | ||
clocks = <&clkc_AO CLKID_AO_UART1>; | ||
resets = <&clkc_AO RESET_AO_UART1>; | ||
status = "disabled"; | ||
}; |
15 changes: 15 additions & 0 deletions
15
Documentation/devicetree/bindings/firmware/meson/meson_sm.txt
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,15 @@ | ||
* Amlogic Secure Monitor | ||
|
||
In the Amlogic SoCs the Secure Monitor code is used to provide access to the | ||
NVMEM, enable JTAG, set USB boot, etc... | ||
|
||
Required properties for the secure monitor node: | ||
- compatible: Should be "amlogic,meson-gxbb-sm" | ||
|
||
Example: | ||
|
||
firmware { | ||
sm: secure-monitor { | ||
compatible = "amlogic,meson-gxbb-sm"; | ||
}; | ||
}; |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,39 @@ | ||
= Amlogic eFuse device tree bindings = | ||
|
||
Required properties: | ||
- compatible: should be "amlogic,meson-gxbb-efuse" | ||
|
||
= Data cells = | ||
Are child nodes of eFuse, bindings of which as described in | ||
bindings/nvmem/nvmem.txt | ||
|
||
Example: | ||
|
||
efuse: efuse { | ||
compatible = "amlogic,meson-gxbb-efuse"; | ||
#address-cells = <1>; | ||
#size-cells = <1>; | ||
|
||
sn: sn@14 { | ||
reg = <0x14 0x10>; | ||
}; | ||
|
||
eth_mac: eth_mac@34 { | ||
reg = <0x34 0x10>; | ||
}; | ||
|
||
bid: bid@46 { | ||
reg = <0x46 0x30>; | ||
}; | ||
}; | ||
|
||
= Data consumers = | ||
Are device nodes which consume nvmem data cells. | ||
|
||
For example: | ||
|
||
eth_mac { | ||
... | ||
nvmem-cells = <ð_mac>; | ||
nvmem-cell-names = "eth_mac"; | ||
}; |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.