Linux RTC
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Lakshay Piplani" <lakshay.piplani@nxp.com>
Cc: "Alexandre Belloni" <alexandre.belloni@bootlin.com>,
	robh@kernel.org, linux-rtc@vger.kernel.org, conor+dt@kernel.org,
	devicetree@vger.kernel.org
Subject: Re: [PATCH v9 1/2] dt-bindings: rtc: Add pcf85053 support
Date: Mon, 14 Sep 2026 06:34:06 +0000	[thread overview]
Message-ID: <20260914063407.170931F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260914062048.3704059-1-lakshay.piplani@nxp.com>

Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
- [Low] The schema definition for `interrupts` lacks a description indicating that the alarm interrupt is active-low level triggered, contradicting the commit message.
- [Low] MAINTAINERS file changes are included in the dt-bindings patch despite the commit message claiming they were moved to the driver patch.
--

commit fbacfc3b449475be8cfd2e294eee7d9182570611
Author: Lakshay Piplani <lakshay.piplani@nxp.com>

dt-bindings: rtc: Add pcf85053 support

This commit adds device tree bindings for the NXP PCF85053 RTC chip.

> diff --git a/Documentation/devicetree/bindings/rtc/nxp,pcf85053.yaml b/Documentation/devicetree/bindings/rtc/nxp,pcf85053.yaml
> new file mode 100644
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/rtc/nxp,pcf85053.yaml
[ ... ]
> +  reg:
> +    maxItems: 1
> +
> +  interrupts:
> +    maxItems: 1
> +

[Severity: Low]
Does this property definition need an explicit description? The V8 -> V9
changelog states "Describe the alarm interrupt as active-low level
triggered," but this definition only contains maxItems: 1.

While the example at the bottom of the schema correctly uses
IRQ_TYPE_LEVEL_LOW, the property itself lacks the promised description text.

[ ... ]

> diff --git a/MAINTAINERS b/MAINTAINERS
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -19571,6 +19571,13 @@ S:	Maintained
>  F:	Documentation/devicetree/bindings/extcon/extcon-ptn5150.yaml
>  F:	drivers/extcon/extcon-ptn5150.c
>  
> +NXP RTC PCF85053 DRIVER
> +M:	Pankit Garg <pankit.garg@nxp.com>
> +M:	Lakshay Piplani <lakshay.piplani@nxp.com>
> +L:	linux-rtc@vger.kernel.org
> +S:	Maintained
> +F:	Documentation/devicetree/bindings/rtc/nxp,pcf85053.yaml
> +

[Severity: Low]
Should these MAINTAINERS file changes be included in this dt-bindings patch?

The V2 -> V3 changelog claims "Moved MAINTAINERS file changes to the driver
patch", but this patch still introduces the new section.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260914062048.3704059-1-lakshay.piplani@nxp.com?part=1

      parent reply	other threads:[~2026-09-14  6:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-14  6:20 [PATCH v9 1/2] dt-bindings: rtc: Add pcf85053 support Lakshay Piplani
2026-09-14  6:20 ` [PATCH v9 2/2] rtc: Add NXP PCF85053 driver support Lakshay Piplani
2026-09-14  6:36   ` sashiko-bot
2026-09-14  6:34 ` sashiko-bot [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=20260914063407.170931F000FF@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=alexandre.belloni@bootlin.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=lakshay.piplani@nxp.com \
    --cc=linux-rtc@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox