From: sashiko-bot@kernel.org
To: "Markus Probst" <markus.probst@posteo.de>
Cc: devicetree@vger.kernel.org, conor+dt@kernel.org,
"Alexandre Belloni" <alexandre.belloni@bootlin.com>,
linux-rtc@vger.kernel.org, robh@kernel.org
Subject: Re: [PATCH v4 1/6] dt-bindings: rtc: Add pinctrl for S35390A
Date: Fri, 14 Aug 2026 23:04:42 +0000 [thread overview]
Message-ID: <20260814230443.5D6451F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260815-rtc_s35390a_int1-v4-1-3133309c365f@posteo.de>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] Invalid use of the `wakeup-parent` property on an RTC end-device.
--
--- Patch [1]: [PATCH v4 1/6] dt-bindings: rtc: Add pinctrl for S35390A ---
commit 58cc609a743d62ad0839cf063b2bd4bf9603a2d0
Author: Markus Probst <markus.probst@posteo.de>
Subject: dt-bindings: rtc: Add pinctrl for S35390A
This commit converts the devicetree bindings for the S-35390A RTC into a
standalone YAML schema. It also adds properties to configure individual pins
via pinctrl to allow the interrupt signal 1 to be used for wakeup alarms.
> diff --git a/Documentation/devicetree/bindings/rtc/sii,s35390a.yaml b/Documentation/devicetree/bindings/rtc/sii,s35390a.yaml
> new file mode 100644
> index 0000000000000..d9da3abbbd518
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/rtc/sii,s35390a.yaml
[ ... ]
> + interrupts:
> + minItems: 1
> + maxItems: 2
> + description: Supports up to 2 interrupt lines via the INT1 and INT2 pins.
> +
> + wakeup-parent: true
> +
> + wakeup-source: true
[Severity: Low]
Is wakeup-parent appropriate for this device? The wakeup-parent property is
typically defined strictly for cascaded interrupt controllers to specify an
upstream wakeup-capable interrupt controller. Since this is an end device,
should it only use the wakeup-source boolean instead?
[ ... ]
> +examples:
> + - |
> + i2c {
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + rtc@30 {
> + compatible = "sii,s35390a";
> + reg = <0x30>;
> + pinctrl-0 = <&rtc_pins_default>;
> + pinctrl-names = "default";
> +
> + wakeup-parent = <&int>;
[Severity: Low]
Should this example be updated to remove the wakeup-parent assignment,
assuming the property is dropped from the schema above?
[ ... ]
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260815-rtc_s35390a_int1-v4-0-3133309c365f@posteo.de?part=1
next prev parent reply other threads:[~2026-08-14 23:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-14 22:57 [PATCH v4 0/6] rtc: s35390a: Allow use of output pin for interrupt signal 1 for wakealarm Markus Probst
2026-08-14 22:57 ` [PATCH v4 1/6] dt-bindings: rtc: Add pinctrl for S35390A Markus Probst
2026-08-14 23:04 ` sashiko-bot [this message]
2026-08-14 23:06 ` Markus Probst
2026-08-14 22:57 ` [PATCH v4 2/6] rtc: s35390a: Add missing newline to dev_err Markus Probst
2026-08-14 23:06 ` sashiko-bot
2026-08-14 22:57 ` [PATCH v4 3/6] rtc: s35390a: Fix alarm not disabling Markus Probst
2026-08-14 23:02 ` sashiko-bot
2026-08-14 22:57 ` [PATCH v4 4/6] rtc: s35390a: force 24-hour mode Markus Probst
2026-08-14 23:06 ` sashiko-bot
2026-08-14 22:57 ` [PATCH v4 5/6] rtc: s35390a: Add pinctrl Markus Probst
2026-08-14 23:10 ` sashiko-bot
2026-08-14 22:57 ` [PATCH v4 6/6] rtc: s35390a: Add synology quirk Markus Probst
2026-08-14 23:02 ` sashiko-bot
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=20260814230443.5D6451F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=alexandre.belloni@bootlin.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=markus.probst@posteo.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox