From: Matti Vaittinen <mazziesaccount@gmail.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>
Cc: Lee Jones <lee@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
Wim Van Sebroeck <wim@linux-watchdog.org>,
Guenter Roeck <linux@roeck-us.net>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-watchdog@vger.kernel.org,
Fabio Aiuto <fabio.aiuto@engicam.com>
Subject: Re: [RFC PATCH v2 2/6] dt-bindings: mfd: bd96801 PMIC core
Date: Mon, 15 Apr 2024 09:24:41 +0300 [thread overview]
Message-ID: <63d3891f-98d3-450f-967b-c72b0516b66b@gmail.com> (raw)
In-Reply-To: <d3e555c2-e740-4aff-aac7-661877166399@gmail.com>
On 4/15/24 08:50, Matti Vaittinen wrote:
> Morning Krzysztof,
>
> Thanks again for the review/help!
>
> On 4/14/24 00:33, Krzysztof Kozlowski wrote:
>> On 12/04/2024 13:21, Matti Vaittinen wrote
>>> +
>>> + rohm,hw-timeout-ms:
>>> + description:
>>> + Watchdog timeout value(s). First walue is timeout limit.
>>> Second value is
>>> + optional value for 'too early' watchdog ping if window timeout
>>> mode is
>>> + to be used.
>>
>> Standard property timeout-sec does not work for you? It should allow two
>> items as well.
>
> I don't think so. We need sub-second units. Furthermore, the timeout-sec
> (if I understand it correctly) updates the "timeout policy", which tells
> the expected ping-interval. This can be different from the "HW
> heart-beat" which tells the HW's ping expectation. Hence the "hw-" prefix.
Oh, I just found out that this is an existing property. The ROHM
BD9576/BD9573 do aleady use this. It seems I've had some discussion
about it with Rob/Guenter when adding it. Frightening thing is that I
didin't remember the discussion or that the property existed at all...
Well, luckily we have lore :)
https://lore.kernel.org/all/c390476e4279d8b75de53271e9fb8948d8854528.camel@fi.rohmeurope.com/#r
(I don't see the final conclusion in this discussion, it has probably
been done on some later version of the series).
Yours,
-- Matti
--
Matti Vaittinen
Linux kernel developer at ROHM Semiconductors
Oulu Finland
~~ When things go utterly wrong vim users can always type :help! ~~
next prev parent reply other threads:[~2024-04-15 6:24 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-12 11:20 [RFC PATCH v2 0/6] Support ROHM BD96801 scalable PMIC Matti Vaittinen
2024-04-12 11:21 ` [RFC PATCH v2 1/6] dt-bindings: ROHM BD96801 PMIC regulators Matti Vaittinen
2024-04-13 21:27 ` Krzysztof Kozlowski
2024-04-15 6:51 ` Matti Vaittinen
2024-04-15 15:29 ` Krzysztof Kozlowski
2024-04-12 11:21 ` [RFC PATCH v2 2/6] dt-bindings: mfd: bd96801 PMIC core Matti Vaittinen
2024-04-13 21:33 ` Krzysztof Kozlowski
2024-04-13 21:36 ` Krzysztof Kozlowski
2024-04-15 5:50 ` Matti Vaittinen
2024-04-15 6:24 ` Matti Vaittinen [this message]
2024-04-15 15:25 ` Krzysztof Kozlowski
2024-04-15 8:28 ` Matti Vaittinen
2024-04-18 17:28 ` Krzysztof Kozlowski
2024-04-19 5:48 ` Matti Vaittinen
2024-04-12 11:22 ` [RFC PATCH v2 3/6] mfd: support ROHM BD96801 " Matti Vaittinen
2024-04-12 11:22 ` [RFC PATCH v2 4/6] regulator: bd96801: ROHM BD96801 PMIC regulators Matti Vaittinen
2024-04-12 11:22 ` [RFC PATCH v2 5/6] watchdog: ROHM BD96801 PMIC WDG driver Matti Vaittinen
2024-04-17 4:29 ` George Cherian
2024-04-17 7:35 ` Matti Vaittinen
2024-04-17 18:20 ` Matti Vaittinen
2024-04-12 11:23 ` [RFC PATCH v2 6/6] MAINTAINERS: Add ROHM BD96801 'scalable PMIC' entries Matti Vaittinen
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=63d3891f-98d3-450f-967b-c72b0516b66b@gmail.com \
--to=mazziesaccount@gmail.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=fabio.aiuto@engicam.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=lee@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=matti.vaittinen@fi.rohmeurope.com \
--cc=robh@kernel.org \
--cc=wim@linux-watchdog.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;
as well as URLs for NNTP newsgroup(s).