From: Kevin Hilman <khilman@baylibre.com>
To: Neil Armstrong <narmstrong@baylibre.com>
Cc: Jerome Brunet <jbrunet@baylibre.com>,
Carlo Caione <carlo@caione.org>,
linux-amlogic@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM64: dts: meson-axg: add sec_AO system controller
Date: Wed, 07 Mar 2018 17:09:42 -0800 [thread overview]
Message-ID: <7hina7gyp5.fsf@baylibre.com> (raw)
In-Reply-To: <412132e7-904d-61c4-d09f-0239e07a92be@baylibre.com> (Neil Armstrong's message of "Thu, 15 Feb 2018 12:55:35 +0100")
Neil Armstrong <narmstrong@baylibre.com> writes:
> On 15/02/2018 11:12, Jerome Brunet wrote:
>> add the secure AO system controller with chipid enabled
>>
>> Signed-off-by: Jerome Brunet <jbrunet@baylibre.com>
>> ---
>> arch/arm64/boot/dts/amlogic/meson-axg.dtsi | 6 ++++++
>> 1 file changed, 6 insertions(+)
>>
>> diff --git a/arch/arm64/boot/dts/amlogic/meson-axg.dtsi b/arch/arm64/boot/dts/amlogic/meson-axg.dtsi
>> index 880e25b113c1..7f4c00216b82 100644
>> --- a/arch/arm64/boot/dts/amlogic/meson-axg.dtsi
>> +++ b/arch/arm64/boot/dts/amlogic/meson-axg.dtsi
>> @@ -836,6 +836,12 @@
>> };
>> };
>>
>> + sec_AO: ao-secure@140 {
>> + compatible = "amlogic,meson-gx-ao-secure", "syscon";
>> + reg = <0x0 0x140 0x0 0x140>;
>> + amlogic,has-chip-id;
>> + };
>> +
>> pwm_AO_ab: pwm@7000 {
>> compatible = "amlogic,meson-axg-ao-pwm";
>> reg = <0x0 0x07000 0x0 0x20>;
>>
>
> Reviewed-by: Neil Armstrong <narmstrong@baylibre.com>
Applied to v4.17/dt64,
Kevin
prev parent reply other threads:[~2018-03-08 1:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-15 10:12 [PATCH] ARM64: dts: meson-axg: add sec_AO system controller Jerome Brunet
[not found] ` <20180215101207.19186-1-jbrunet-rdvid1DuHRBWk0Htik3J/w@public.gmane.org>
2018-02-15 11:55 ` Neil Armstrong
2018-03-08 1:09 ` Kevin Hilman [this message]
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=7hina7gyp5.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=carlo@caione.org \
--cc=devicetree@vger.kernel.org \
--cc=jbrunet@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=narmstrong@baylibre.com \
/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