From: "Uwe Kleine-König" <ukleinek@debian.org>
To: Krzysztof Kozlowski <krzk@kernel.org>,
Daniel Golle <daniel@makrotopia.org>,
Aurelien Jarno <aurelien@aurel32.net>,
Olivia Mackall <olivia@selenic.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Heiko Stuebner <heiko@sntech.de>,
Philipp Zabel <p.zabel@pengutronix.de>,
Sebastian Reichel <sebastian.reichel@collabora.com>,
Sascha Hauer <s.hauer@pengutronix.de>,
Dragan Simic <dsimic@manjaro.org>,
Martin Kaiser <martin@kaiser.cx>,
Ard Biesheuvel <ardb@kernel.org>,
linux-crypto@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 2/3] hwrng: add Rockchip SoC hwrng driver
Date: Sun, 23 Jun 2024 11:46:25 +0200 [thread overview]
Message-ID: <395f8ebe-1392-4d8f-b91f-c9a8f5f48afe@debian.org> (raw)
In-Reply-To: <612bd49c-c44a-41f2-89e9-c96e62e52a0a@kernel.org>
Hello Krzysztof,
On 6/23/24 09:00, Krzysztof Kozlowski wrote:
> On 23/06/2024 05:33, Daniel Golle wrote:
>> +
>> + pm_runtime_set_autosuspend_delay(dev, RK_RNG_AUTOSUSPEND_DELAY);
>> + pm_runtime_use_autosuspend(dev);
>> + devm_pm_runtime_enable(dev);
>> +
>> + ret = devm_hwrng_register(dev, &rk_rng->rng);
>> + if (ret)
>> + return dev_err_probe(&pdev->dev, ret, "Failed to register Rockchip hwrng\n");
>> +
>> + dev_dbg(&pdev->dev, "Registered Rockchip hwrng\n");
>
> Drop, it is not useful at all. Srsly, we had already long enough talk,
> [...]
And in this long talk using dev_dbg() was one of the suggestions for a
compromise. For me this is ok.
> There is no single benefit of such debug statement. sysfs already
> provides you this information. Simple entry/exit is provided by
> tracing. You duplicate existing interfaces without any benefit, because
> this prints nothing more.
There might be a (small) value if you want to know when during boot the
device becomes available. So having a dev_dbg() that can be enabled
dynamically (assuming DYNAMIC_DEBUG=y) and isn't in the way otherwise
might be justified. IMHO a dev_dbg is lightweight enough that *I* won't
continue the discussion.
Best regards
Uwe
next prev parent reply other threads:[~2024-06-23 9:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-23 3:32 [PATCH v4 0/3] hwrng: add hwrng support for Rockchip RK3568 Daniel Golle
2024-06-23 3:32 ` [PATCH v4 1/3] dt-bindings: rng: Add Rockchip RNG bindings Daniel Golle
2024-06-23 7:03 ` Krzysztof Kozlowski
2024-06-23 13:08 ` Daniel Golle
2024-06-26 7:30 ` Krzysztof Kozlowski
2024-06-23 3:33 ` [PATCH v4 2/3] hwrng: add Rockchip SoC hwrng driver Daniel Golle
2024-06-23 7:00 ` Krzysztof Kozlowski
2024-06-23 9:46 ` Uwe Kleine-König [this message]
2024-06-23 11:47 ` Dragan Simic
2024-06-23 10:42 ` Aurelien Jarno
2024-06-23 14:10 ` Anand Moon
2024-06-23 3:33 ` [PATCH v4 3/3] arm64: dts: rockchip: add DT entry for RNG to RK356x Daniel Golle
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=395f8ebe-1392-4d8f-b91f-c9a8f5f48afe@debian.org \
--to=ukleinek@debian.org \
--cc=ardb@kernel.org \
--cc=aurelien@aurel32.net \
--cc=conor+dt@kernel.org \
--cc=daniel@makrotopia.org \
--cc=devicetree@vger.kernel.org \
--cc=dsimic@manjaro.org \
--cc=heiko@sntech.de \
--cc=herbert@gondor.apana.org.au \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=martin@kaiser.cx \
--cc=olivia@selenic.com \
--cc=p.zabel@pengutronix.de \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=sebastian.reichel@collabora.com \
/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®