devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Dragan Simic <dsimic@manjaro.org>
Cc: "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>,
	"Uwe Kleine-König" <ukleinek@debian.org>,
	"Sebastian Reichel" <sebastian.reichel@collabora.com>,
	"Anand Moon" <linux.amoon@gmail.com>,
	"Sascha Hauer" <s.hauer@pengutronix.de>,
	"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 v3 2/3] hwrng: add Rockchip SoC hwrng driver
Date: Sat, 22 Jun 2024 20:05:03 +0200	[thread overview]
Message-ID: <303bc9df-c887-41d0-8613-0fa2898ab48e@kernel.org> (raw)
In-Reply-To: <173ce1663186ab8282356748abcac3f4@manjaro.org>

On 21/06/2024 20:13, Dragan Simic wrote:
> Hello Krzysztof,
> 
> On 2024-06-21 11:57, Krzysztof Kozlowski wrote:
>> On 21/06/2024 03:25, Daniel Golle wrote:
>>> From: Aurelien Jarno <aurelien@aurel32.net>
> 
> [snip]
> 
>>> +	pm_runtime_set_autosuspend_delay(dev, RK_RNG_AUTOSUSPEND_DELAY);
>>> +	pm_runtime_use_autosuspend(dev);
>>> +	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_info(&pdev->dev, "Registered Rockchip hwrng\n");
>>
>> Drop, driver should be silent on success.
> 
> I respectfully disagree.  Many drivers print a single line upon
> successful probing, which I find very useful.  In this particular

No, it's duplicating existing interfaces and polluting log unnecessarily
without any useful information.

> case, it's even more useful, because some people may be concerned
> about the use of hardware TRNGs, so we should actually make sure
> to announce it.

Best regards,
Krzysztof


  parent reply	other threads:[~2024-06-22 18:05 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-21  1:24 [PATCH v3 0/3] hwrng: add hwrng support for Rockchip RK3568 Daniel Golle
2024-06-21  1:25 ` [PATCH v3 1/3] dt-bindings: RNG: Add Rockchip RNG bindings Daniel Golle
2024-06-21  9:12   ` Diederik de Haas
2024-06-21  9:39     ` Diederik de Haas
2024-06-21  9:52   ` Krzysztof Kozlowski
2024-06-21  1:25 ` [PATCH v3 2/3] hwrng: add Rockchip SoC hwrng driver Daniel Golle
2024-06-21  9:32   ` Diederik de Haas
2024-06-21  9:57   ` Krzysztof Kozlowski
2024-06-21 10:18     ` Chen-Yu Tsai
2024-06-21 18:13     ` Dragan Simic
2024-06-21 22:16       ` Uwe Kleine-König
2024-06-22 10:29         ` Dragan Simic
2024-06-22 20:26           ` Heiko Stübner
2024-06-22 20:45             ` Dragan Simic
2024-06-23  0:20               ` Uwe Kleine-König
2024-06-23  5:41                 ` Dragan Simic
2024-06-22 18:05       ` Krzysztof Kozlowski [this message]
2024-06-22 19:10         ` Dragan Simic
2024-06-21 10:04   ` Chen-Yu Tsai
2024-06-21 11:41   ` Philipp Zabel
2024-06-21  1:25 ` [PATCH v3 3/3] arm64: dts: rockchip: add DT entry for RNG to RK356x Daniel Golle
2024-06-21  9:36   ` Diederik de Haas
2024-06-21  9:49     ` Heiko Stübner
2024-06-22  9:58 ` [PATCH v3 0/3] hwrng: add hwrng support for Rockchip RK3568 Aurelien Jarno

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=303bc9df-c887-41d0-8613-0fa2898ab48e@kernel.org \
    --to=krzk@kernel.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=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=linux.amoon@gmail.com \
    --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 \
    --cc=ukleinek@debian.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).