From: Matthias Brugger <matthias.bgg@gmail.com>
To: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
Cc: robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: mediatek: mt6795: Add CPUX system timer node
Date: Thu, 15 Sep 2022 18:32:24 +0200 [thread overview]
Message-ID: <990c00a4-f20d-1e7e-e4d3-6731947c1456@gmail.com> (raw)
In-Reply-To: <3a91e743-2b8f-51b6-9ac1-adc3e7ec8cc4@collabora.com>
On 14/09/2022 13:01, AngeloGioacchino Del Regno wrote:
> Il 29/07/22 11:35, AngeloGioacchino Del Regno ha scritto:
>> Add a node for mt6795-systimer: this is necessary to start the
>> System Timer(s) for all cores, finally making CNTVCT_EL0 usable.
>>
>> Signed-off-by: AngeloGioacchino Del Regno
>> <angelogioacchino.delregno@collabora.com>
>
> Hello Matthias,
>
> gentle ping for this one - this has no floating dependencies and it's
> verified to work as expected.
>
Applied, thanks!
> Cheers,
> Angelo
>
>> ---
>> arch/arm64/boot/dts/mediatek/mt6795.dtsi | 8 ++++++++
>> 1 file changed, 8 insertions(+)
>>
>> diff --git a/arch/arm64/boot/dts/mediatek/mt6795.dtsi
>> b/arch/arm64/boot/dts/mediatek/mt6795.dtsi
>> index d4842b4a4eb7..46f0e54be766 100644
>> --- a/arch/arm64/boot/dts/mediatek/mt6795.dtsi
>> +++ b/arch/arm64/boot/dts/mediatek/mt6795.dtsi
>> @@ -230,6 +230,14 @@ sysirq: intpol-controller@10200620 {
>> reg = <0 0x10200620 0 0x20>;
>> };
>> + systimer: timer@10200670 {
>> + compatible = "mediatek,mt6795-systimer";
>> + reg = <0 0x10200670 0 0x10>;
>> + interrupts = <GIC_SPI 64 IRQ_TYPE_LEVEL_HIGH>;
>> + clocks = <&system_clk>;
>> + clock-names = "clk13m";
>> + };
>> +
>> gic: interrupt-controller@10221000 {
>> compatible = "arm,gic-400";
>> #interrupt-cells = <3>;
>
>
prev parent reply other threads:[~2022-09-15 16:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-29 9:35 AngeloGioacchino Del Regno
2022-09-14 11:01 ` AngeloGioacchino Del Regno
2022-09-15 16:32 ` Matthias Brugger [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=990c00a4-f20d-1e7e-e4d3-6731947c1456@gmail.com \
--to=matthias.bgg@gmail.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=robh+dt@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
Powered by JetHome