mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: LI Qingwu <Qing-wu.Li@leica-geosystems.com.cn>,
	"sre@kernel.org" <sre@kernel.org>,
	"robh@kernel.org" <robh@kernel.org>,
	"krzk+dt@kernel.org" <krzk+dt@kernel.org>,
	"conor+dt@kernel.org" <conor+dt@kernel.org>,
	"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: GEO-CHHER-bsp-development <bsp-development.geo@leica-geosystems.com>
Subject: Re: [PATCH V1 2/3] dt-bindings: power: sbs-battery: add polling interval property
Date: Tue, 30 Dec 2025 10:46:16 +0100	[thread overview]
Message-ID: <5c52b138-38ef-42c9-9f81-c605df68792e@kernel.org> (raw)
In-Reply-To: <GV2PR06MB108091652BE6C23A6F9A7127CD7BCA@GV2PR06MB10809.eurprd06.prod.outlook.com>

On 30/12/2025 10:40, LI Qingwu wrote:
>>>>>
>>>>> +  sbs,monitoring-interval-ms:
>>>>> +    description:
>>>>> +      Polling interval in milliseconds for battery status monitoring on
>>>>> +      systems without interrupt support. The driver periodically checks
>>>>> +      the battery status and notifies userspace of changes. Ignored when
>>>>> +      GPIO interrupt is available.
>>>>
>>>>
>>>> You described the desired Linux feature or behavior, not the actual hardware.
>>>> The bindings are about the latter, so instead you need to rephrase
>>>> the property and its description to match actual hardware
>>>> capabilities/features/configuration etc.
>>>>
>>>
>>> Thanks for the quick feedback!
>>> How about this?
>>>
>>>   sbs,monitoring-interval-ms:
>>>     description:
>>>       Polling interval in milliseconds for battery status monitoring.
>>>       Intended for hardware designs where the battery's interrupt signal
>>>       is not connected, necessitating periodic status checks to detect
>>>       changes.
>>
>>
>> Nothing changed. It's exactly the same.
>>
>> Explain me how "polling interval" by Linux driver is a hardware value?
>> What was not clear in my feedback?
>>
> 
> Thank you for the feedback. I apologize, but I am still not clear on
> the correct approach.
> 
> I understand that "polling interval" is software policy and should not
> be in device tree. However, I am unsure whether:
> 
> 1. I should rephrase the property to describe the hardware fact (e.g.,
>    "battery alert signal is not wired"), or

Isn't this already described in the binding implicitly by missing
interrupt? Or the device is not using dedicated interrupt pins and only
SMBus Alert? But if the latter, then alert is always available.


> 2. I should remove this from device tree entirely and use a module
>    parameter instead.

Module parameters are usually not the way to configure anything. Look at
other devices and how they do it. Usually this is sysfs interface.

Regardless, I don't give you advice nor instruction how to implement
this. I just do not agree with current phrasing for DT. If you come with
proper hardware description for DT, it could be fine. If you want to
remove it from DT completely, I am fine as well.


Best regards,
Krzysztof

  reply	other threads:[~2025-12-30  9:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-29  8:56 [PATCH V1 1/3] power: supply: sbs-battery: Fix false presence when registers read zero LI Qingwu
2025-12-29  8:56 ` [PATCH V1 2/3] dt-bindings: power: sbs-battery: add polling interval property LI Qingwu
2025-12-29  9:16   ` Krzysztof Kozlowski
2025-12-29  9:50     ` LI Qingwu
2025-12-29 12:47       ` Krzysztof Kozlowski
2025-12-30  9:40         ` LI Qingwu
2025-12-30  9:46           ` Krzysztof Kozlowski [this message]
2025-12-29 10:36   ` Rob Herring (Arm)
2025-12-29  8:56 ` [PATCH V1 3/3] power: supply: sbs-battery: Add optional status monitoring LI Qingwu

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=5c52b138-38ef-42c9-9f81-c605df68792e@kernel.org \
    --to=krzk@kernel.org \
    --cc=Qing-wu.Li@leica-geosystems.com.cn \
    --cc=bsp-development.geo@leica-geosystems.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=sre@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®