public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jerome Brunet <jbrunet@baylibre.com>
To: Alexey Romanov <avromanov@salutedevices.com>
Cc: neil.armstrong@linaro.org, clabbe@baylibre.com,
	herbert@gondor.apana.org.au, davem@davemloft.net,
	robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
	conor+dt@kernel.org, khilman@baylibre.com, jbrunet@baylibre.com,
	martin.blumenstingl@googlemail.com, vadim.fedorenko@linux.dev,
	linux-crypto@vger.kernel.org, linux-amlogic@lists.infradead.org,
	linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, kernel@salutedevices.com
Subject: Re: [PATCH v5 03/21] drivers: crypto: meson: make CLK controller optional
Date: Fri, 01 Mar 2024 16:21:20 +0100	[thread overview]
Message-ID: <1jwmqmrmva.fsf@starbuckisacylon.baylibre.com> (raw)
In-Reply-To: <20240301132936.621238-4-avromanov@salutedevices.com>


On Fri 01 Mar 2024 at 16:29, Alexey Romanov <avromanov@salutedevices.com> wrote:

> Amlogic crypto IP doesn't take a clock input on some
> SoCs: AXG / A1 / S4 / G12. So make it optional.
>

I commented this patch on v2 and the comment keep on being un-addressed.

The SoC either:
* has a clock that is required for the IP to work
* Or does not

It is not something you are free to provide or not.

For the record, I find very hard believe that some SoC would have clock,
and other would not, for the same HW.

Isn't it more likely that the clock just happens to be left enabled by
the bootloader on some SoC and it conviently allows to ignore it ?

> Signed-off-by: Alexey Romanov <avromanov@salutedevices.com>
> ---
>  drivers/crypto/amlogic/amlogic-gxl-core.c | 14 +++-----------
>  1 file changed, 3 insertions(+), 11 deletions(-)
>
> diff --git a/drivers/crypto/amlogic/amlogic-gxl-core.c b/drivers/crypto/amlogic/amlogic-gxl-core.c
> index e9e733ed98e0..a3a69a59f476 100644
> --- a/drivers/crypto/amlogic/amlogic-gxl-core.c
> +++ b/drivers/crypto/amlogic/amlogic-gxl-core.c
> @@ -269,16 +269,11 @@ static int meson_crypto_probe(struct platform_device *pdev)
>  		dev_err(&pdev->dev, "Cannot request MMIO err=%d\n", err);
>  		return err;
>  	}
> -	mc->busclk = devm_clk_get(&pdev->dev, "blkmv");
> +
> +	mc->busclk = devm_clk_get_optional_enabled(&pdev->dev, "blkmv");
>  	if (IS_ERR(mc->busclk)) {
>  		err = PTR_ERR(mc->busclk);
> -		dev_err(&pdev->dev, "Cannot get core clock err=%d\n", err);
> -		return err;
> -	}
> -
> -	err = clk_prepare_enable(mc->busclk);
> -	if (err != 0) {
> -		dev_err(&pdev->dev, "Cannot prepare_enable busclk\n");
> +		dev_err(&pdev->dev, "Cannot get and enable core clock err=%d\n", err);
>  		return err;
>  	}
>  
> @@ -306,7 +301,6 @@ static int meson_crypto_probe(struct platform_device *pdev)
>  	meson_unregister_algs(mc);
>  error_flow:
>  	meson_free_chanlist(mc, mc->flow_cnt - 1);
> -	clk_disable_unprepare(mc->busclk);
>  	return err;
>  }
>  
> @@ -321,8 +315,6 @@ static void meson_crypto_remove(struct platform_device *pdev)
>  	meson_unregister_algs(mc);
>  
>  	meson_free_chanlist(mc, mc->flow_cnt - 1);
> -
> -	clk_disable_unprepare(mc->busclk);
>  }
>  
>  static const struct meson_pdata meson_gxl_pdata = {


-- 
Jerome

  reply	other threads:[~2024-03-01 15:30 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-01 13:29 [PATCH v5 00/21] Support more Amlogic SoC families in crypto driver Alexey Romanov
2024-03-01 13:29 ` [PATCH v5 01/21] drivers: crypto: meson: don't hardcode IRQ count Alexey Romanov
2024-03-01 13:29 ` [PATCH v5 02/21] drviers: crypto: meson: add platform data Alexey Romanov
2024-03-01 13:29 ` [PATCH v5 03/21] drivers: crypto: meson: make CLK controller optional Alexey Romanov
2024-03-01 15:21   ` Jerome Brunet [this message]
2024-03-04 13:49     ` Alexey Romanov
2024-03-05 13:47       ` Alexey Romanov
2024-03-01 13:29 ` [PATCH v5 04/21] drivers: crypto: meson: add MMIO helpers Alexey Romanov
2024-03-01 13:29 ` [PATCH v5 05/21] drivers: crypto: meson: move get_engine_number() Alexey Romanov
2024-03-01 13:29 ` [PATCH v5 06/21] drivers: crypto: meson: drop status field from meson_flow Alexey Romanov
2024-03-01 13:29 ` [PATCH v5 07/21] drivers: crypto: meson: move algs definition and cipher API to cipher.c Alexey Romanov
2024-03-01 13:29 ` [PATCH v5 08/21] drivers: crypto: meson: cleanup defines Alexey Romanov
2024-03-01 13:29 ` [PATCH v5 09/21] drivers: crypto: meson: process more than MAXDESCS descriptors Alexey Romanov
2024-03-22  8:27   ` Corentin Labbe
2024-03-22 10:14     ` neil.armstrong
2024-03-01 13:29 ` [PATCH v5 10/21] drivers: crypto: meson: avoid kzalloc in engine thread Alexey Romanov
2024-03-01 13:29 ` [PATCH v5 11/21] drivers: crypto: meson: introduce hasher Alexey Romanov
2024-03-01 13:29 ` [PATCH v5 12/21] drivers: crypto: meson: add support for AES-CTR Alexey Romanov
2024-03-01 13:29 ` [PATCH v5 13/21] drivers: crypto: meson: use fallback for 192-bit keys Alexey Romanov
2024-03-01 13:29 ` [PATCH v5 14/21] drivers: crypto: meson: add support for G12-series Alexey Romanov
2024-03-01 13:29 ` [PATCH v5 15/21] drivers: crypto: meson: add support for AXG-series Alexey Romanov
2024-03-01 13:29 ` [PATCH v5 16/21] drivers: crypto: meson: add support for A1-series Alexey Romanov
2024-03-01 13:29 ` [PATCH v5 17/21] dt-bindings: crypto: meson: support new SoC's Alexey Romanov
2024-03-01 14:56   ` Krzysztof Kozlowski
2024-03-01 13:29 ` [PATCH v5 18/21] arch: arm64: dts: meson: a1: add crypto node Alexey Romanov
2024-03-01 13:29 ` [PATCH v5 19/21] arch: arm64: dts: meson: s4: " Alexey Romanov
2024-03-01 13:29 ` [PATCH v5 20/21] arch: arm64: dts: meson: g12: " Alexey Romanov
2024-03-01 13:29 ` [PATCH v5 21/21] arch: arm64: dts: meson: axg: " Alexey Romanov

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=1jwmqmrmva.fsf@starbuckisacylon.baylibre.com \
    --to=jbrunet@baylibre.com \
    --cc=avromanov@salutedevices.com \
    --cc=clabbe@baylibre.com \
    --cc=conor+dt@kernel.org \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=herbert@gondor.apana.org.au \
    --cc=kernel@salutedevices.com \
    --cc=khilman@baylibre.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-amlogic@lists.infradead.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin.blumenstingl@googlemail.com \
    --cc=neil.armstrong@linaro.org \
    --cc=robh+dt@kernel.org \
    --cc=vadim.fedorenko@linux.dev \
    /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