devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kuldeep Singh <singh.kuldeep87k@gmail.com>
To: Marc Zyngier <maz@kernel.org>,
	Daniel Lezcano <daniel.lezcano@linaro.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Rob Herring <robh+dt@kernel.org>,
	Marc Zyngier <marc.zyngier@arm.com>,
	Mark Rutland <mark.rutland@arm.com>
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 2/3] dt-bindings: timer: Document arm,cortex-a7-timer in arch timer
Date: Fri, 18 Mar 2022 00:45:25 +0530	[thread overview]
Message-ID: <20220317191527.96237-3-singh.kuldeep87k@gmail.com> (raw)
In-Reply-To: <20220317191527.96237-1-singh.kuldeep87k@gmail.com>

Renesas RZ/N1D platform uses compatible "arm,cortex-a7-timer" in
conjugation with "arm,armv7-timer". Since, initial entry is not
documented, it start raising dtbs_check warnings.

['arm,cortex-a7-timer', 'arm,armv7-timer'] is too long
'arm,cortex-a7-timer' is not one of ['arm,armv7-timer', 'arm,armv8-timer']
'arm,cortex-a7-timer' is not one of ['arm,cortex-a15-timer']

Document this compatible to address it. The motivation to add this
change is taken from an already existing entry "arm,cortex-a15-timer".
Please note, this will not hurt any arch timer users.

Signed-off-by: Kuldeep Singh <singh.kuldeep87k@gmail.com>
---
 Documentation/devicetree/bindings/timer/arm,arch_timer.yaml | 1 +
 1 file changed, 1 insertion(+)

diff --git a/Documentation/devicetree/bindings/timer/arm,arch_timer.yaml b/Documentation/devicetree/bindings/timer/arm,arch_timer.yaml
index ba2910f0a7b2..ea390e5df71d 100644
--- a/Documentation/devicetree/bindings/timer/arm,arch_timer.yaml
+++ b/Documentation/devicetree/bindings/timer/arm,arch_timer.yaml
@@ -26,6 +26,7 @@ properties:
           - arm,armv8-timer
       - items:
           - enum:
+              - arm,cortex-a7-timer
               - arm,cortex-a15-timer
           - const: arm,armv7-timer
 
-- 
2.25.1


  parent reply	other threads:[~2022-03-17 19:16 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 ` Kuldeep Singh [this message]
2022-03-17 20:25   ` [PATCH v2 2/3] dt-bindings: timer: Document arm, cortex-a7-timer in " 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
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=20220317191527.96237-3-singh.kuldeep87k@gmail.com \
    --to=singh.kuldeep87k@gmail.com \
    --cc=daniel.lezcano@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marc.zyngier@arm.com \
    --cc=mark.rutland@arm.com \
    --cc=maz@kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=tglx@linutronix.de \
    /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).