From: Corentin Labbe <clabbe.montjoie@gmail.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, 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 v2 03/20] drviers: crypto: meson: add platform data
Date: Wed, 24 Jan 2024 08:30:48 +0100 [thread overview]
Message-ID: <ZbC8qLXogjxJD8LD@Red> (raw)
In-Reply-To: <20240123165831.970023-4-avromanov@salutedevices.com>
Le Tue, Jan 23, 2024 at 07:58:14PM +0300, Alexey Romanov a écrit :
> To support other Amlogic SoC's we have to
> use platform data: descriptors and status registers
> offsets are individual for each SoC series.
>
> Signed-off-by: Alexey Romanov <avromanov@salutedevices.com>
> ---
> drivers/crypto/amlogic/amlogic-gxl-cipher.c | 2 +-
> drivers/crypto/amlogic/amlogic-gxl-core.c | 31 +++++++++++++++------
> drivers/crypto/amlogic/amlogic-gxl.h | 11 ++++++++
> 3 files changed, 35 insertions(+), 9 deletions(-)
>
> diff --git a/drivers/crypto/amlogic/amlogic-gxl-cipher.c b/drivers/crypto/amlogic/amlogic-gxl-cipher.c
> index b19032f92415..7eff3ae7356f 100644
> --- a/drivers/crypto/amlogic/amlogic-gxl-cipher.c
> +++ b/drivers/crypto/amlogic/amlogic-gxl-cipher.c
> @@ -225,7 +225,7 @@ static int meson_cipher(struct skcipher_request *areq)
>
> reinit_completion(&mc->chanlist[flow].complete);
> mc->chanlist[flow].status = 0;
> - writel(mc->chanlist[flow].t_phy | 2, mc->base + (flow << 2));
> + writel(mc->chanlist[flow].t_phy | 2, mc->base + ((mc->pdata->descs_reg + flow) << 2));
> wait_for_completion_interruptible_timeout(&mc->chanlist[flow].complete,
> msecs_to_jiffies(500));
> if (mc->chanlist[flow].status == 0) {
> diff --git a/drivers/crypto/amlogic/amlogic-gxl-core.c b/drivers/crypto/amlogic/amlogic-gxl-core.c
> index a58644be76e9..2be381e157c4 100644
> --- a/drivers/crypto/amlogic/amlogic-gxl-core.c
> +++ b/drivers/crypto/amlogic/amlogic-gxl-core.c
> @@ -18,6 +18,7 @@
> #include <linux/kernel.h>
> #include <linux/module.h>
> #include <linux/of.h>
> +#include <linux/of_device.h>
> #include <linux/platform_device.h>
>
> #include "amlogic-gxl.h"
> @@ -30,9 +31,10 @@ static irqreturn_t meson_irq_handler(int irq, void *data)
>
> for (flow = 0; flow < mc->flow_cnt; flow++) {
> if (mc->chanlist[flow].irq == irq) {
> - p = readl(mc->base + ((0x04 + flow) << 2));
> + p = readl(mc->base + ((mc->pdata->status_reg + flow) << 2));
> if (p) {
> - writel_relaxed(0xF, mc->base + ((0x4 + flow) << 2));
> + writel_relaxed(0xF, mc->base +
> + ((mc->pdata->status_reg + flow) << 2));
> mc->chanlist[flow].status = 1;
> complete(&mc->chanlist[flow].complete);
> return IRQ_HANDLED;
> @@ -245,15 +247,34 @@ static void meson_unregister_algs(struct meson_dev *mc)
> }
> }
>
> +static const struct meson_pdata meson_gxl_pdata = {
> + .descs_reg = 0x0,
> + .status_reg = 0x4,
> +};
> +
> +static const struct of_device_id meson_crypto_of_match_table[] = {
> + {
> + .compatible = "amlogic,gxl-crypto",
> + .data = &meson_gxl_pdata,
> + },
> + {},
> +};
> +
> static int meson_crypto_probe(struct platform_device *pdev)
> {
> + const struct of_device_id *match;
> struct meson_dev *mc;
> int err;
>
> + match = of_match_device(meson_crypto_of_match_table, &pdev->dev);
> + if (!match)
> + return -EINVAL;
> +
> mc = devm_kzalloc(&pdev->dev, sizeof(*mc), GFP_KERNEL);
> if (!mc)
> return -ENOMEM;
>
> + mc->pdata = match->data;
> mc->dev = &pdev->dev;
> platform_set_drvdata(pdev, mc);
>
> @@ -312,12 +333,6 @@ static void meson_crypto_remove(struct platform_device *pdev)
> clk_disable_unprepare(mc->busclk);
> }
>
> -static const struct of_device_id meson_crypto_of_match_table[] = {
> - { .compatible = "amlogic,gxl-crypto", },
> - {}
> -};
> -MODULE_DEVICE_TABLE(of, meson_crypto_of_match_table);
Hello
This patch breaks bisection, since it removes MODULE_DEVICE_TABLE.
After applying patchs 1,2,3 the driver does not load anymore on lepotato board.
Regards
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2024-01-24 7:31 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-23 16:58 [PATCH v2 00/20] Support more Amlogic SoC families in crypto driver Alexey Romanov
2024-01-23 16:58 ` [PATCH v2 01/20] drivers: crypto: meson: don't hardcode IRQ count Alexey Romanov
2024-01-23 16:58 ` [PATCH v2 02/20] drivers: crypto: meson: make CLK controller optional Alexey Romanov
2024-01-24 8:28 ` Jerome Brunet
2024-01-23 16:58 ` [PATCH v2 03/20] drviers: crypto: meson: add platform data Alexey Romanov
2024-01-24 7:30 ` Corentin Labbe [this message]
2024-02-01 17:13 ` Alexey Romanov
2024-02-01 19:45 ` Corentin Labbe
2024-01-23 16:58 ` [PATCH v2 04/20] drivers: crypto: meson: add MMIO helpers Alexey Romanov
2024-01-23 16:58 ` [PATCH v2 05/20] drivers: crypto: meson: move get_engine_number() Alexey Romanov
2024-01-23 16:58 ` [PATCH v2 06/20] drivers: crypto: meson: drop status field from meson_flow Alexey Romanov
2024-01-23 16:58 ` [PATCH v2 07/20] drivers: crypto: meson: move algs definition and cipher API to cipher.c Alexey Romanov
2024-01-23 16:58 ` [PATCH v2 08/20] drivers: crypto: meson: cleanup defines Alexey Romanov
2024-01-23 16:58 ` [PATCH v2 09/20] drivers: crypto: meson: process more than MAXDESCS descriptors Alexey Romanov
2024-01-23 16:58 ` [PATCH v2 10/20] drivers: crypto: meson: avoid kzalloc in engine thread Alexey Romanov
2024-01-23 16:58 ` [PATCH v2 11/20] drivers: crypto: meson: introduce hasher Alexey Romanov
2024-01-23 16:58 ` [PATCH v2 12/20] drivers: crypto: meson: add support for AES-CTR Alexey Romanov
2024-01-23 16:58 ` [PATCH v2 13/20] drivers: crypto: meson: use fallback for 192-bit keys Alexey Romanov
2024-01-23 16:58 ` [PATCH v2 14/20] drivers: crypto: meson: add support for G12-series Alexey Romanov
2024-01-23 16:58 ` [PATCH v2 15/20] drivers: crypto: meson: add support for AXG-series Alexey Romanov
2024-01-23 16:58 ` [PATCH v2 16/20] dt-bindings: crypto: meson: add new compatibles Alexey Romanov
2024-01-23 18:37 ` Rob Herring
2024-01-24 7:22 ` Krzysztof Kozlowski
2024-01-23 16:58 ` [PATCH v2 17/20] arch: arm64: dts: meson: a1: add crypto node Alexey Romanov
2024-01-23 16:58 ` [PATCH v2 18/20] arch: arm64: dts: meson: s4: " Alexey Romanov
2024-01-23 16:58 ` [PATCH v2 19/20] arch: arm64: dts: meson: g12: " Alexey Romanov
2024-01-23 16:58 ` [PATCH v2 20/20] arch: arm64: dts: meson: axg: " Alexey Romanov
2024-01-24 7:22 ` Krzysztof Kozlowski
2024-01-24 9:13 ` [PATCH v2 00/20] Support more Amlogic SoC families in crypto driver neil.armstrong
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=ZbC8qLXogjxJD8LD@Red \
--to=clabbe.montjoie@gmail.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=jbrunet@baylibre.com \
--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 \
/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).