From: Krzysztof Kozlowski <krzk@kernel.org>
To: Ian Ray <ian.ray@gehealthcare.com>
Cc: dmitry.torokhov@gmail.com, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, linux-input@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/1] Input: snvs_pwrkey - support power-off-time-sec
Date: Fri, 14 Mar 2025 14:31:12 +0100 [thread overview]
Message-ID: <e58f5851-9988-463b-824e-ad3da1137c33@kernel.org> (raw)
In-Reply-To: <Z9QuC7tZoXj3DRZs@9e5302bffcb7>
On 14/03/2025 14:24, Ian Ray wrote:
> On Fri, Mar 14, 2025 at 01:55:47PM +0100, Krzysztof Kozlowski wrote:
>> On 14/03/2025 10:42, Ian Ray wrote:
>>>
>>> /* Get SNVS register Page */
>>> @@ -148,6 +152,24 @@ static int imx_snvs_pwrkey_probe(struct platform_device *pdev)
>>> if (pdata->irq < 0)
>>> return -EINVAL;
>>>
>>> + if (!of_property_read_u32(np, "power-off-time-sec", &val)) {
>>
>> And when you test your DTS against binding what do you see? I suspect
>> new warning.
>
> I checked the build logs (from a clean workarea), plus run-time dmesg,
> both with the DTS change -- and without it. There are no new warnings
> (specifically nothing mentioning snvs-pwrkey or dts or power-off-time).
>
> If an invalid value (such as "42") is chosen then the probe fails with
> -EINVAL as expected.
>
> Is there something else that I should have checked?
I don't know what your build logs process has. I meant dtbs_check
against the bindings.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-03-14 13:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-14 9:42 [PATCH v2 0/1] Input: snvs_pwrkey - add configurable force shutdown time Ian Ray
2025-03-14 9:42 ` [PATCH v2 1/1] Input: snvs_pwrkey - support power-off-time-sec Ian Ray
2025-03-14 12:55 ` Krzysztof Kozlowski
2025-03-14 13:24 ` Ian Ray
2025-03-14 13:31 ` Krzysztof Kozlowski [this message]
2025-03-14 14:47 ` Ian Ray
2025-03-16 13:03 ` Krzysztof Kozlowski
2025-03-17 6:22 ` Ian Ray
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=e58f5851-9988-463b-824e-ad3da1137c33@kernel.org \
--to=krzk@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=ian.ray@gehealthcare.com \
--cc=krzk+dt@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@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 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).