From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Adriana Stancu <adriana@arista.com>
Cc: linux-rtc@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH v2 1/2] dt-bindings: rtc: ti,bq32k: Add delay on rtc reads
Date: Thu, 16 Apr 2026 12:03:54 +0200 [thread overview]
Message-ID: <20260416100354ac85cb48@mail.local> (raw)
In-Reply-To: <20260416095706.3212158-2-adriana@arista.com>
On 16/04/2026 02:57:05-0700, Adriana Stancu wrote:
> Add a configurable "ti,read-settle-us" property to resolve a limitation
> where aggressive I2C polling prevents the BQ32000's internal register to
> update. This ensures the hardware has sufficient idle time to update its
> buffer, preventing stale data reads on systems where the "interrupts" are
> not configured.
>
Why does it need to be configured?
--
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2026-04-16 10:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-16 9:24 [PATCH v1 0/2] rtc: bq32000: Add settle delay for aggressive polling Adriana Stancu
2026-04-16 9:24 ` [PATCH v1 1/2] dt-bindings: rtc: ti,bq32k: Add delay on rtc reads Adriana Stancu
2026-04-16 9:27 ` Krzysztof Kozlowski
2026-04-16 9:24 ` [PATCH v1 2/2] rtc: bq32000: add configurable delay between RTC reads Adriana Stancu
2026-04-16 9:57 ` [PATCH v2 0/2] rtc: bq32000: Add settle delay for aggressive polling Adriana Stancu
2026-04-16 9:57 ` [PATCH v2 1/2] dt-bindings: rtc: ti,bq32k: Add delay on rtc reads Adriana Stancu
2026-04-16 10:03 ` Alexandre Belloni [this message]
2026-04-16 10:33 ` Adriana Nicolae
2026-04-16 11:00 ` Krzysztof Kozlowski
2026-04-16 11:14 ` Adriana Nicolae
2026-04-16 9:57 ` [PATCH v2 2/2] rtc: bq32000: add configurable delay between RTC reads Adriana Stancu
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=20260416100354ac85cb48@mail.local \
--to=alexandre.belloni@bootlin.com \
--cc=adriana@arista.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=robh@kernel.org \
/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.