All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Sander Speetjens <sander.speetjens@gmail.com>
Cc: Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Florian Fainelli <florian.fainelli@broadcom.com>,
	Jonathan Bell <jonathan@raspberrypi.com>,
	Stefan Wahren <wahrenst@gmx.net>,
	linux-rtc@vger.kernel.org, devicetree@vger.kernel.org,
	linux-rpi-kernel@lists.infradead.org,
	linux-arm-kernel@lists.infradead.org, pbrobinson@gmail.com,
	Conor Dooley <conor.dooley@microchip.com>,
	Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
Subject: Re: [PATCH v11 2/3] dt-bindings: rtc: Add property for Raspberry Pi 5 RTC
Date: Wed, 14 Oct 2026 19:28:35 +0200	[thread overview]
Message-ID: <20261014172835a731fd1b@mail.local> (raw)
In-Reply-To: <20261014083016.332338-3-sander.speetjens@gmail.com>

On 14/10/2026 10:30:15+0200, Sander Speetjens wrote:
> The Raspberry Pi 5 has a built-in RTC that can be battery-backed
> via the VBAT pin. When a rechargeable coin cell is used, the
> hardware requires a trickle-charge voltage to keep the battery
> topped up.
> 
> Expose the trickle-voltage-millivolt DT property so the driver can
> program the correct charge voltage for board specific configurations with
> the attached battery.
> 

You are missing a comment from Krzysztof:
"Commit msg could explain that you do not reference rtc.yaml due to node
naming rule."

> Acked-by: Conor Dooley <conor.dooley@microchip.com>
> Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
> Signed-off-by: Sander Speetjens <sander.speetjens@gmail.com>
> ---
> V10 -> V11: No changes
> 
> V9 -> V10: No changes
> 
> V8 -> V9: No changes
> 
> V7 -> V8: No changes
> 
> V6 -> V7: No changes
> 
> V5 -> V6: No changes
> 
> V4 -> V5: As discussed with Conor Dooley, the reff to uint32 is removed
> and a PR is made on dt-schema adding millivolt to property-units.yaml
> 
> V3 -> V4: Add a reff to uint32
> 
> V2 -> V3: Fixed the firmware property naming
> 
> V1 -> V2: As discussed with Krzysztof Kozlowski, this property is folded into
> the existing raspberrypi,bcm2835-firmware properties.
> 
>  .../bindings/arm/bcm/raspberrypi,bcm2835-firmware.yaml      | 6 ++++++
>  1 file changed, 6 insertions(+)
> 
> diff --git a/Documentation/devicetree/bindings/arm/bcm/raspberrypi,bcm2835-firmware.yaml b/Documentation/devicetree/bindings/arm/bcm/raspberrypi,bcm2835-firmware.yaml
> index 983ea80eaec9..dc71fd57834e 100644
> --- a/Documentation/devicetree/bindings/arm/bcm/raspberrypi,bcm2835-firmware.yaml
> +++ b/Documentation/devicetree/bindings/arm/bcm/raspberrypi,bcm2835-firmware.yaml
> @@ -133,6 +133,11 @@ properties:
>      required:
>        - compatible
>  
> +  trickle-voltage-millivolt:
> +    $ref: /schemas/rtc/rtc.yaml#/properties/trickle-voltage-millivolt
> +    minimum: 1300
> +    maximum: 5000
> +
>  required:
>    - compatible
>    - mboxes
> @@ -144,6 +149,7 @@ examples:
>      firmware {
>          compatible = "raspberrypi,bcm2835-firmware", "simple-mfd";
>          mboxes = <&mailbox>;
> +        trickle-voltage-millivolt = <3300>;
>  
>          firmware_clocks: clocks {
>              compatible = "raspberrypi,firmware-clocks";
> -- 
> 2.56.0
> 

-- 
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  parent reply	other threads:[~2026-10-14 17:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-14  8:30 [PATCH v11 0/3] Raspberry Pi 5 RTC driver Sander Speetjens
2026-10-14  8:30 ` [PATCH v11 1/3] dt-bindings: rtc: Add missing type to trickle-voltage-millivolt Sander Speetjens
2026-10-14  8:33   ` sashiko-bot
2026-10-14  8:30 ` [PATCH v11 2/3] dt-bindings: rtc: Add property for Raspberry Pi 5 RTC Sander Speetjens
2026-10-14  8:35   ` sashiko-bot
2026-10-14 17:28   ` Alexandre Belloni [this message]
2026-10-14  8:30 ` [PATCH v11 3/3] rtc: Add Raspberry Pi 5 RTC driver Sander Speetjens
2026-10-14  8:42   ` 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=20261014172835a731fd1b@mail.local \
    --to=alexandre.belloni@bootlin.com \
    --cc=conor+dt@kernel.org \
    --cc=conor.dooley@microchip.com \
    --cc=devicetree@vger.kernel.org \
    --cc=florian.fainelli@broadcom.com \
    --cc=jonathan@raspberrypi.com \
    --cc=krzk+dt@kernel.org \
    --cc=krzysztof.kozlowski@oss.qualcomm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-rpi-kernel@lists.infradead.org \
    --cc=linux-rtc@vger.kernel.org \
    --cc=pbrobinson@gmail.com \
    --cc=robh@kernel.org \
    --cc=sander.speetjens@gmail.com \
    --cc=wahrenst@gmx.net \
    /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.