On 06/22/2017 11:24 PM, Rob Herring wrote:
> On Wed, Jun 14, 2017 at 02:05:44PM +0200, Neil Armstrong wrote:
>> Add bindings for the SoC information register of the Amlogic SoCs.
>>
>> Signed-off-by: Neil Armstrong <narmstr...@baylibre.com>
>> ---
>> Documentation/devicetree/bindings/arm/amlogic.txt | 29
>> +++++++++++++++++++++++
>> 1 file changed, 29 insertions(+)
>>
>> diff --git a/Documentation/devicetree/bindings/arm/amlogic.txt
>> b/Documentation/devicetree/bindings/arm/amlogic.txt
>> index 5c01e65..a6d8754 100644
>> --- a/Documentation/devicetree/bindings/arm/amlogic.txt
>> +++ b/Documentation/devicetree/bindings/arm/amlogic.txt
>> @@ -60,3 +60,32 @@ Board compatible values (alphabetically, grouped by SoC):
>> - "amlogic,q201" (Meson gxm s912)
>> - "kingnovel,r-box-pro" (Meson gxm S912)
>> - "nexbox,a1" (Meson gxm s912)
>> +
>> +Amlogic Meson Firmware registers Interface
>> +------------------------------------------
>> +
>> +The Meson SoCs have a register bank with status and data shared with the
>> +secure firmware.
>> +
>> +Required properties:
>> + - compatible: For Meson GX SoCs, must be "amlogic,meson-gx-ao-secure",
>> "syscon"
>> +
>> +Properties should indentify components of this register interface :
>> +
>> +Meson GX SoC Information
>> +------------------------
>> +A firmware register encodes the SoC type, package and revision information
>> on
>> +the Meson GX SoCs.
>> +If present, the following property should be added :
>> +
>> +Optional properties:
>> + - has-chip-id: If present, the interface gives the current SoC version.
>
> amlogic,has-chip-id
OK, thanks I'll send a v3.1 with this small change.
Neil
>
> With that,
>
> Acked-by: Rob Herring <r...@kernel.org>
>
>> +
>> +Example
>> +-------
>> +
>> +ao-secure@140 {
>> + compatible = "amlogic,meson-gx-ao-secure", "syscon";
>> + reg = <0x0 0x140 0x0 0x140>;
>> + has-chip-id;
>> +};
>> --
>> 1.9.1
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe devicetree" in
>> the body of a message to majord...@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
