-
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 branch 'v4.8/dt64' into v4.8/dt64-2
- Loading branch information
Showing
8 changed files
with
478 additions
and
4 deletions.
There are no files selected for viewing
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
Oops, something went wrong.