From: sashiko-bot@kernel.org
To: "Aleksa Paunovic via B4 Relay"
<devnull+aleksa.paunovic.htecgroup.com@kernel.org>
Cc: robh@kernel.org, devicetree@vger.kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH v8 1/3] dt-bindings: timer: mips,p8700-gcru
Date: Wed, 10 Jun 2026 08:26:46 +0000 [thread overview]
Message-ID: <20260610082646.B29F71F00893@smtp.kernel.org> (raw)
In-Reply-To: <20260610-riscv-time-mmio-v8-1-a865206675c6@htecgroup.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] Mismatch between the node's unit-address and the first address in its 'reg' property in the device tree example.
--
commit 28ad318962744fd052dc7a14265d2214d613bc60
Author: Aleksa Paunovic <aleksa.paunovic@htecgroup.com>
dt-bindings: timer: mips,p8700-gcru
Add dt-bindings for the GCR.U memory mapped timer device for RISC-V
platforms. The GCR.U memory region contains shadow copies of the RISC-V
mtime register and the hrtime Global Configuration Register.
> diff --git a/Documentation/devicetree/bindings/timer/mips,p8700-gcru.yaml b/Documentation/devicetree/bindings/timer/mips,p8700-gcru.yaml
> new file mode 100644
> index 0000000000000..3498255762cce
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/timer/mips,p8700-gcru.yaml
[ ... ]
> +examples:
> + - |
> + timer@1617f000 {
> + compatible = "mips,p8700-gcru";
> + reg = <0x1617f050 0x8>,
[Severity: Low]
Does the unit-address in the node name (1617f000) need to exactly match the
first address specified in the reg property (1617f050)? This mismatch will
likely trigger a unit_address_vs_reg warning during dt_binding_check.
> + <0x1617f090 0x8>;
> + };
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260610-riscv-time-mmio-v8-0-a865206675c6@htecgroup.com?part=1
next prev parent reply other threads:[~2026-06-10 8:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-10 8:22 [PATCH v8 0/3] riscv: Use GCR.U timer device as clocksource Aleksa Paunovic via B4 Relay
2026-06-10 8:22 ` Aleksa Paunovic
2026-06-10 8:22 ` Aleksa Paunovic via B4 Relay
2026-06-10 8:22 ` [PATCH v8 1/3] dt-bindings: timer: mips,p8700-gcru Aleksa Paunovic via B4 Relay
2026-06-10 8:22 ` Aleksa Paunovic
2026-06-10 8:22 ` Aleksa Paunovic via B4 Relay
2026-06-10 8:26 ` sashiko-bot [this message]
2026-06-10 16:18 ` Conor Dooley
2026-06-10 8:22 ` [PATCH v8 2/3] riscv: clocksource: Add readq options to clocksource mmio Aleksa Paunovic via B4 Relay
2026-06-10 8:22 ` Aleksa Paunovic
2026-06-10 8:22 ` Aleksa Paunovic via B4 Relay
2026-06-10 8:22 ` [PATCH v8 3/3] riscv: clocksource: Add p8700-gcru driver Aleksa Paunovic via B4 Relay
2026-06-10 8:22 ` Aleksa Paunovic
2026-06-10 8:22 ` Aleksa Paunovic via B4 Relay
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=20260610082646.B29F71F00893@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=devnull+aleksa.paunovic.htecgroup.com@kernel.org \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.