From: Chen-Yu Tsai <wens@kernel.org>
To: Daniel Golle <daniel@makrotopia.org>
Cc: "Krzysztof Kozlowski" <krzk@kernel.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>,
"Dragan Simic" <dsimic@manjaro.org>,
"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: Fri, 21 Jun 2024 18:18:13 +0800 [thread overview]
Message-ID: <CAGb2v66VHXvBGH9X9nj1=fSnCgP035HEMU-L2NShg08rE5Qnug@mail.gmail.com> (raw)
In-Reply-To: <f8e6b1b9-f8ff-42df-b1ef-bcc439c2e913@kernel.org>
On Fri, Jun 21, 2024 at 5:58 PM Krzysztof Kozlowski <krzk@kernel.org> wrote:
>
> On 21/06/2024 03:25, Daniel Golle wrote:
> > From: Aurelien Jarno <aurelien@aurel32.net>
> >
>
> > +
> > +static int rk_rng_init(struct hwrng *rng)
> > +{
> > + struct rk_rng *rk_rng = container_of(rng, struct rk_rng, rng);
> > + int ret;
> > +
> > + /* start clocks */
> > + ret = clk_bulk_prepare_enable(rk_rng->clk_num, rk_rng->clk_bulks);
> > + if (ret < 0) {
> > + dev_err((struct device *) rk_rng->rng.priv,
> > + "Failed to enable clks %d\n", ret);
> > + return ret;
> > + }
> > +
> > + /* set the sample period */
> > + writel(RK_RNG_SAMPLE_CNT, rk_rng->base + TRNG_RNG_SAMPLE_CNT);
> > +
> > + /* set osc ring speed and enable it */
> > + writel_relaxed(TRNG_RNG_CTL_LEN_256_BIT |
> > + TRNG_RNG_CTL_OSC_RING_SPEED_0 |
> > + TRNG_RNG_CTL_ENABLE,
> > + rk_rng->base + TRNG_RNG_CTL);
>
> I doubt relaxed write is here intentional. Enabling should be last
> instruction, so this should be ordered write.
I agree that the driver should just do all non-relaxed writes for simplicity.
The penalty isn't that severe since commit 22ec71615d82 ("arm64: io: Relax
implicit barriers in default I/O accessors").
Just to clarify, writes to devices are always ordered. The non-relaxed
writes are ordered to _memory writes_, which doesn't really matter for
this driver.
ChenYu
> > +
> > + return 0;
> > +}
> > +
> > +static void rk_rng_cleanup(struct hwrng *rng)
> > +{
> > + struct rk_rng *rk_rng = container_of(rng, struct rk_rng, rng);
> > +
> > + /* stop TRNG */
> > + writel_relaxed(0, rk_rng->base + TRNG_RNG_CTL);
>
> This should not be relaxed. This might lead to very tricky to debug issues.
>
> > +
> > + /* stop clocks */
> > + clk_bulk_disable_unprepare(rk_rng->clk_num, rk_rng->clk_bulks);
> > +}
> > +
> > +static int rk_rng_read(struct hwrng *rng, void *buf, size_t max, bool wait)
> > +{
> > + struct rk_rng *rk_rng = container_of(rng, struct rk_rng, rng);
> > + size_t to_read = min_t(size_t, max, RK_RNG_MAX_BYTE);
> > + u32 reg;
> > + int ret = 0;
> > +
> > + ret = pm_runtime_get_sync((struct device *) rk_rng->rng.priv);
>
> Why this cannot be just simpler pm_runtime_resume_and_get()?
>
> > + if (ret < 0)
> > + goto out;
>
> This does not look like correct error path. Device was not busy here.
>
> > +
> > + /* Start collecting random data */
> > + writel_relaxed(TRNG_RNG_CTL_START, rk_rng->base + TRNG_RNG_CTL);
> > +
> > + ret = readl_poll_timeout(rk_rng->base + TRNG_RNG_CTL, reg,
> > + !(reg & TRNG_RNG_CTL_START),
> > + RK_RNG_POLL_PERIOD_US,
> > + RK_RNG_POLL_TIMEOUT_US);
> > + if (ret < 0)
> > + goto out;
> > +
> > + /* Read random data stored in the registers */
> > + memcpy_fromio(buf, rk_rng->base + TRNG_RNG_DOUT, to_read);
> > +out:
> > + pm_runtime_mark_last_busy((struct device *) rk_rng->rng.priv);
> > + pm_runtime_put_sync_autosuspend((struct device *) rk_rng->rng.priv);
> > +
> > + return to_read;
> > +}
> > +
> > +static int rk_rng_probe(struct platform_device *pdev)
> > +{
> > + struct device *dev = &pdev->dev;
> > + struct rk_rng *rk_rng;
> > + int ret;
> > +
> > + rk_rng = devm_kzalloc(dev, sizeof(*rk_rng), GFP_KERNEL);
> > + if (!rk_rng)
> > + return -ENOMEM;
> > +
> > + rk_rng->base = devm_platform_ioremap_resource(pdev, 0);
> > + if (IS_ERR(rk_rng->base))
> > + return PTR_ERR(rk_rng->base);
> > +
> > + rk_rng->clk_num = devm_clk_bulk_get_all(dev, &rk_rng->clk_bulks);
> > + if (rk_rng->clk_num < 0)
> > + return dev_err_probe(dev, rk_rng->clk_num,
> > + "Failed to get clks property\n");
> > +
> > + rk_rng->rst = devm_reset_control_array_get(&pdev->dev, false, false);
> > + if (IS_ERR(rk_rng->rst))
> > + return dev_err_probe(dev, PTR_ERR(rk_rng->rst),
> > + "Failed to get reset property\n");
> > +
> > + reset_control_assert(rk_rng->rst);
> > + udelay(2);
> > + reset_control_deassert(rk_rng->rst);
> > +
> > + platform_set_drvdata(pdev, rk_rng);
> > +
> > + rk_rng->rng.name = dev_driver_string(dev);
> > +#ifndef CONFIG_PM
> > + rk_rng->rng.init = rk_rng_init;
> > + rk_rng->rng.cleanup = rk_rng_cleanup;
> > +#endif
> > + rk_rng->rng.read = rk_rng_read;
> > + rk_rng->rng.priv = (unsigned long) dev;
> > + rk_rng->rng.quality = 900;
> > +
> > + 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.
>
>
> Best regards,
> Krzysztof
>
>
next prev parent reply other threads:[~2024-06-21 10:18 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 [this message]
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
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='CAGb2v66VHXvBGH9X9nj1=fSnCgP035HEMU-L2NShg08rE5Qnug@mail.gmail.com' \
--to=wens@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=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=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).