From: Marc Zyngier <maz@kernel.org>
To: Kuldeep Singh <singh.kuldeep87k@gmail.com>
Cc: Rob Herring <robh+dt@kernel.org>, Joel Stanley <joel@jms.id.au>,
Andrew Jeffery <andrew@aj.id.au>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org
Subject: Re: [PATCH v2 3/3] ARM: dts: aspeed: Remove arch timer clocks property
Date: Thu, 17 Mar 2022 19:54:34 +0000 [thread overview]
Message-ID: <87h77wxslh.wl-maz@kernel.org> (raw)
In-Reply-To: <20220317191527.96237-4-singh.kuldeep87k@gmail.com>
On Thu, 17 Mar 2022 19:15:26 +0000,
Kuldeep Singh <singh.kuldeep87k@gmail.com> wrote:
>
> Arch timer either require clock-frequency property or doesn't need to
> specify clock at all in DT. In general, frequency can be determined
> internally and in case of brokern firmwares, need to extend
> clock-frequency to pass info to driver.
A clock frequency and a clock are not the same thing.
>
> Aspeed BMC is the platform which defines clocks property, an invalid
> entry which can be safely removed.
Safely removed? Says who? Have you tested this change?
>
> Moreover, clocks also matches incorrectly with the regex pattern.
> Remove this entry altogether to fix it.
> 'clocks' does not match any of the regexes: 'pinctrl-[0-9]+'
NAK. That's not a reason to randomly butcher things.
M.
>
> Signed-off-by: Kuldeep Singh <singh.kuldeep87k@gmail.com>
> ---
> arch/arm/boot/dts/aspeed-g6.dtsi | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/arch/arm/boot/dts/aspeed-g6.dtsi b/arch/arm/boot/dts/aspeed-g6.dtsi
> index c32e87fad4dc..d5ef9aceb632 100644
> --- a/arch/arm/boot/dts/aspeed-g6.dtsi
> +++ b/arch/arm/boot/dts/aspeed-g6.dtsi
> @@ -64,7 +64,6 @@ timer {
> <GIC_PPI 14 (GIC_CPU_MASK_SIMPLE(2) | IRQ_TYPE_LEVEL_LOW)>,
> <GIC_PPI 11 (GIC_CPU_MASK_SIMPLE(2) | IRQ_TYPE_LEVEL_LOW)>,
> <GIC_PPI 10 (GIC_CPU_MASK_SIMPLE(2) | IRQ_TYPE_LEVEL_LOW)>;
> - clocks = <&syscon ASPEED_CLK_HPLL>;
> arm,cpu-registers-not-fw-configured;
> always-on;
> };
> --
> 2.25.1
>
>
--
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2022-03-17 19:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-17 19:15 [PATCH v2 0/3] Fix for arch timer users Kuldeep Singh
2022-03-17 19:15 ` [PATCH v2 1/3] dt-bindings: timer: Rearrange compatible entries of arch timer Kuldeep Singh
2022-03-17 19:15 ` [PATCH v2 2/3] dt-bindings: timer: Document arm,cortex-a7-timer in " Kuldeep Singh
2022-03-17 20:25 ` [PATCH v2 2/3] dt-bindings: timer: Document arm, cortex-a7-timer " Robin Murphy
2022-03-17 21:25 ` Kuldeep Singh
2022-03-20 18:47 ` Rob Herring
2022-03-21 11:52 ` Robin Murphy
2022-03-23 18:35 ` Kuldeep Singh
2022-03-25 21:23 ` Rob Herring
2022-04-11 12:35 ` Geert Uytterhoeven
2022-03-17 19:15 ` [PATCH v2 3/3] ARM: dts: aspeed: Remove arch timer clocks property Kuldeep Singh
2022-03-17 19:54 ` Marc Zyngier [this message]
2022-03-17 21:10 ` Kuldeep Singh
2022-03-17 21:46 ` Marc Zyngier
2022-03-18 6:18 ` Joel Stanley
2022-03-18 13:44 ` Krzysztof Kozlowski
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=87h77wxslh.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=andrew@aj.id.au \
--cc=devicetree@vger.kernel.org \
--cc=joel@jms.id.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=singh.kuldeep87k@gmail.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;
as well as URLs for NNTP newsgroup(s).