linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Neil Armstrong <narmstrong@baylibre.com>
To: Rob Herring <robh@kernel.org>
Cc: khilman@baylibre.com, carlo@caione.org,
	linux-amlogic@lists.infradead.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v3 1/3] dt-bindings: arm: amlogic: Add SoC information bindings
Date: Fri, 23 Jun 2017 10:22:24 +0200	[thread overview]
Message-ID: <c62ace5a-f977-6f07-2e02-e20aac94bcb9@baylibre.com> (raw)
In-Reply-To: <20170622212449.wsck475jxabawqsv@rob-hp-laptop>

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 <narmstrong@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 <robh@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 majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2017-06-23  8:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-14 12:05 [PATCH v3 0/3] soc: amlogic: Add Amlogic SoC Information driver Neil Armstrong
2017-06-14 12:05 ` [PATCH v3 1/3] dt-bindings: arm: amlogic: Add SoC information bindings Neil Armstrong
2017-06-22 21:24   ` Rob Herring
2017-06-23  8:22     ` Neil Armstrong [this message]
2017-06-14 12:05 ` [PATCH v3 2/3] ARM64: dts: meson-gx: Add SoC info register Neil Armstrong
2017-06-14 12:05 ` [PATCH v3 3/3] soc: Add Amlogic SoC Information driver Neil Armstrong

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=c62ace5a-f977-6f07-2e02-e20aac94bcb9@baylibre.com \
    --to=narmstrong@baylibre.com \
    --cc=carlo@caione.org \
    --cc=devicetree@vger.kernel.org \
    --cc=khilman@baylibre.com \
    --cc=linux-amlogic@lists.infradead.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).