From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 1B29BC27C4F for ; Fri, 21 Jun 2024 22:17:50 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender:List-Subscribe:List-Help :List-Post:List-Archive:List-Unsubscribe:List-Id:Content-Transfer-Encoding: Content-Type:In-Reply-To:From:References:Cc:To:Subject:MIME-Version:Date: Message-ID:Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=lkjWpzw0fQHhk8t6BZ8etJcAyMy91SJQnID9y78b/Ec=; b=dM7yLlnDH3sythNP4bDTlpNohb rOJm9P4CR/3aJ1lfWEdFVi+cHtxWJ9NnaePeagJMjIkeqx71k1a01gNtMVD9CAhnt6tgp7/rzkprZ wld0gKDXYXXJ4v/rng7yOe+6c45rATH+bRM3iCd3uJPDuGwXCQRzVh59poCWYfLFB68Bey6yP5C2i oSL05NlBzXFdv2yQ+DI9BUNgUzE2lO2tu0bjEb25GnNw25bn9xeuTJMWlEDmPpBDjvgfNL65AZYig v1LWFAYTuSZOGwZnAPdpZ1EcodjDQjcCB+d8DVDuNASaHltiqXs8op/gTbCEAGe8x05ZK7wKKoAWV lgQNEqjw==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.97.1 #2 (Red Hat Linux)) id 1sKmZc-0000000AjTt-0pTc; Fri, 21 Jun 2024 22:17:36 +0000 Received: from sin.source.kernel.org ([145.40.73.55]) by bombadil.infradead.org with esmtps (Exim 4.97.1 #2 (Red Hat Linux)) id 1sKmZX-0000000AjT4-43HV; Fri, 21 Jun 2024 22:17:33 +0000 Received: from smtp.kernel.org (transwarp.subspace.kernel.org [100.75.92.58]) by sin.source.kernel.org (Postfix) with ESMTP id ACA18CE3D30; Fri, 21 Jun 2024 22:17:25 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id D0FBAC2BBFC; Fri, 21 Jun 2024 22:17:19 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1719008244; bh=XIgP3gnjd7LTC0cYexQhnrJXzTEPBFd9t0ht0ox/1jo=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=FNLs4VxLGgEYEzsY52miCNNujSfXwPo8nvN02pkUceS4AGd/t9R0YBoGuSz0iSBC5 1P24T8SfRPpNKmYsJD3FQf44uMwvChSF0oWtp9SwcqssBupu93Dg7mQNvgDm9G60Uv U2FFjo9EmbwgtSJ5EizcIuV+n3ybPB4bOryBaXpCd92LGyHoja7v/Y+S7s8WBBfq9C XvOamhRIhWggfPWdi28OLfKdK+MZBdU6E++x8qWpRn2D5+Wu3w0XzST89l7AeJewfc Y6jKnIVav4PDjOgs66bE1oBclTu97rV0yQDXG1sDtBRGWuesPPneNSCW+t+RoGwt3N CuVYcjsbcJRYA== Message-ID: Date: Sat, 22 Jun 2024 00:16:56 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH v3 2/3] hwrng: add Rockchip SoC hwrng driver To: Dragan Simic , Krzysztof Kozlowski Cc: Daniel Golle , Aurelien Jarno , Olivia Mackall , Herbert Xu , Rob Herring , Krzysztof Kozlowski , Conor Dooley , Heiko Stuebner , Philipp Zabel , Sebastian Reichel , Anand Moon , Sascha Hauer , Martin Kaiser , Ard Biesheuvel , 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 References: <57a7fb13451f066ddc8d1d9339d8f6c1e1946bf1.1718921174.git.daniel@makrotopia.org> <173ce1663186ab8282356748abcac3f4@manjaro.org> Content-Language: en-US, de-DE From: =?UTF-8?Q?Uwe_Kleine-K=C3=B6nig?= In-Reply-To: <173ce1663186ab8282356748abcac3f4@manjaro.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20240621_151732_382435_758775FA X-CRM114-Status: GOOD ( 14.77 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org Hello Dragan, On 6/21/24 20:13, Dragan Simic wrote: > On 2024-06-21 11:57, Krzysztof Kozlowski wrote: >> On 21/06/2024 03:25, Daniel Golle wrote: >>> From: Aurelien Jarno > > [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 > 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. I agree to Krzysztof here. From the POV of a driver author, your own driver is very important and while you write it, it really interests *you* if the driver is successfully probed. However from a system perspective these are annoying: There are easily >50 devices[1] on a system, if all of these print a message in probe, you have little chance to see the relevant messages. Even if every driver author thinks their work is a special snow flake that is worth announcing, in practice users only care about your driver if there is a problem. Additionally each message takes time and so delays the boot process. Additionally each message takes place in the printk ring buffer and so edges out earlier messages that might be more important. So +1 for dropping the dev_info() or at least using dev_debug() for it. Best regards Uwe [1] On my laptop if have: $ find /sys/devices -name driver | wc -l 87 On a Raspberrypi it yields 66.