Received: by 2002:ac0:aed5:0:0:0:0:0 with SMTP id t21csp351606imb; Fri, 1 Mar 2019 02:22:29 -0800 (PST) X-Google-Smtp-Source: AHgI3IZeP1GUYyCk5nNQy21WVCYqwmIlC1CEoVGjBovP30iXwCypMaBXISwzBJ8Qutneg/08WicN X-Received: by 2002:aa7:83ca:: with SMTP id j10mr4829715pfn.50.1551435748974; Fri, 01 Mar 2019 02:22:28 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1551435748; cv=none; d=google.com; s=arc-20160816; b=v103dI4r7HA7RQeLg0nShtPUxzBqKMzumCCQQndwSYHmR45w8mXZnhHuyJbFqGPt6n c4MSAJSI0WJWJ2G3bGTJVmtXM/K4Ykr/3AOvszuKukcsUC05aR6Xh4IhjpDJoBx8b6Xi IIZe7JOnjsC28TJenKhom969OjZCNi6IJ6Rz5uiDxV7IHeZC7Q7bK0OquDCxYv4i6UM6 Wm/otcYBXnY1KZJTga049bwDpglYLo9Rs2Zz0+2rL7auLdv8xIj16k5gU+tOAjQjvEDM smT9vNi+N2hn4VDiT7NyyQJQWczHnVXkUrCLNEZiVi41koTPOe+25chJ2v7GmnxRiAV6 b50Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=n/1R8jnDVbRJqE4oXc5mbYqJdFpdhGIzxdyNLe9Vh0s=; b=RnCsOhU43J1Hf2Ad2jeWlCHIa8HdNcVj0tVHkNj8taBvg8IE0t5ZPJ0Nw+VmsiQlco QDLeHgdDLyoURbGbUlyVbxtHTw1Mz7/XedJQmhFc6amX7DTUBiZMeeJDzBUSa2Bu/Vi8 /znOGNOBMSSubEV8lNUgucygqofAwbbsa4fxOYwSFLftZ++/2GlkK1CAANVrOAv1xnVj DarD9npJOZ2Ufkwl3pPAW8LKwD7idyLxE0f84l7ZIj2GcnJze6mwvr3WKhdgT9f8T+lS ZhwO1Q8x88NgZN+56/X/2XdtjAFG0DuLMSAd/r5LUHx+H1ofyDHCC0slo+zS24oXm2I0 XeOw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=QUsCSPTI; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id ay6si20014416plb.293.2019.03.01.02.22.14; Fri, 01 Mar 2019 02:22:28 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=QUsCSPTI; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2387600AbfCAJ4R (ORCPT + 99 others); Fri, 1 Mar 2019 04:56:17 -0500 Received: from mail.kernel.org ([198.145.29.99]:51974 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727915AbfCAJ4Q (ORCPT ); Fri, 1 Mar 2019 04:56:16 -0500 Received: from mail-lj1-f180.google.com (mail-lj1-f180.google.com [209.85.208.180]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id B218D218AE; Fri, 1 Mar 2019 09:56:14 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1551434175; bh=u/wRiDrea89nFXVHsddZyzJYhNj2t3SsSsVsPi2L7fI=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=QUsCSPTIJyKdIcUR1Pku7cSqGruFSRDzXVZXd/V5919Ig6tdQMLXFDZYhTScl3r7g /RVZ03Dib5vUa642psznyYcwl0fkUYfASALYGZXqF7c0DKwHUImPBemmy0iK0bPfPq 8TQrNWdLdpfZCKJ63TssaZCUR5juLjduUNHLEMl4= Received: by mail-lj1-f180.google.com with SMTP id l5so19859247lje.1; Fri, 01 Mar 2019 01:56:14 -0800 (PST) X-Gm-Message-State: APjAAAU3D3Ycsf5TiYKfAhorjxDzNSkcDm4ZcZnC/1nnube4r6cnx1E6 Wx9hWaG9fmwdM+RydaJ5Lfme0pi3yAE9zOqHxwg= X-Received: by 2002:a2e:3c10:: with SMTP id j16mr2257270lja.113.1551434172849; Fri, 01 Mar 2019 01:56:12 -0800 (PST) MIME-Version: 1.0 References: <20190222122144.19024-1-k.konieczny@partner.samsung.com> <20190222122144.19024-4-k.konieczny@partner.samsung.com> In-Reply-To: <20190222122144.19024-4-k.konieczny@partner.samsung.com> From: Krzysztof Kozlowski Date: Fri, 1 Mar 2019 10:56:01 +0100 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH v4 3/3] crypto: s5p: add AES support for Exynos5433 To: Kamil Konieczny Cc: Vladimir Zapolskiy , Herbert Xu , "David S. Miller" , linux-crypto@vger.kernel.org, "linux-samsung-soc@vger.kernel.org" , linux-kernel@vger.kernel.org, Bartlomiej Zolnierkiewicz , Marek Szyprowski Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 22 Feb 2019 at 13:22, Kamil Konieczny wrote: > > Add AES crypto HW acceleration for Exynos5433, with the help of SlimSSS IP. > > Reviewed-by: Krzysztof Kozlowski > Signed-off-by: Kamil Konieczny > --- > drivers/crypto/s5p-sss.c | 50 ++++++++++++++++++++++++++++++++++++---- > 1 file changed, 46 insertions(+), 4 deletions(-) > diff --git a/drivers/crypto/s5p-sss.c b/drivers/crypto/s5p-sss.c > index 0064be0e3941..3f45cc5cb94a 100644 > --- a/drivers/crypto/s5p-sss.c > +++ b/drivers/crypto/s5p-sss.c > @@ -232,6 +232,7 @@ > * struct samsung_aes_variant - platform specific SSS driver data > * @aes_offset: AES register offset from SSS module's base. > * @hash_offset: HASH register offset from SSS module's base. > + * @clk_names: names of clocks needed to run SSS IP > * > * Specifies platform specific configuration of SSS module. > * Note: A structure for driver specific platform data is used for future > @@ -240,6 +241,7 @@ > struct samsung_aes_variant { > unsigned int aes_offset; > unsigned int hash_offset; > + const char *clk_names[]; > }; > > struct s5p_aes_reqctx { > @@ -296,6 +298,7 @@ struct s5p_aes_ctx { > struct s5p_aes_dev { > struct device *dev; > struct clk *clk; > + struct clk *pclk; > void __iomem *ioaddr; > void __iomem *aes_ioaddr; > int irq_fc; > @@ -384,11 +387,19 @@ struct s5p_hash_ctx { > static const struct samsung_aes_variant s5p_aes_data = { > .aes_offset = 0x4000, > .hash_offset = 0x6000, > + .clk_names = { "secss", }, > }; > > static const struct samsung_aes_variant exynos_aes_data = { > .aes_offset = 0x200, > .hash_offset = 0x400, > + .clk_names = { "secss", }, > +}; > + > +static const struct samsung_aes_variant exynos5433_slim_aes_data = { > + .aes_offset = 0x400, > + .hash_offset = 0x800, > + .clk_names = { "pclk", "aclk", }, > }; > > static const struct of_device_id s5p_sss_dt_match[] = { > @@ -400,6 +411,10 @@ static const struct of_device_id s5p_sss_dt_match[] = { > .compatible = "samsung,exynos4210-secss", > .data = &exynos_aes_data, > }, > + { > + .compatible = "samsung,exynos5433-slim-sss", > + .data = &exynos5433_slim_aes_data, > + }, > { }, > }; > MODULE_DEVICE_TABLE(of, s5p_sss_dt_match); > @@ -2208,18 +2223,39 @@ static int s5p_aes_probe(struct platform_device *pdev) > return PTR_ERR(pdata->ioaddr); > } > > - pdata->clk = devm_clk_get(dev, "secss"); > + pdata->clk = devm_clk_get(dev, variant->clk_names[0]); > if (IS_ERR(pdata->clk)) { > - dev_err(dev, "failed to find secss clock source\n"); > + dev_err(dev, "failed to find secss clock %s\n", > + variant->clk_names[0]); > return -ENOENT; > } > > err = clk_prepare_enable(pdata->clk); > if (err < 0) { > - dev_err(dev, "Enabling SSS clk failed, err %d\n", err); > + dev_err(dev, "Enabling clock %s failed, err %d\n", > + variant->clk_names[0], err); > return err; > } > > + if (variant->clk_names[1]) { > + pdata->pclk = devm_clk_get(dev, variant->clk_names[1]); I see on today's linux next: [ 6.391256] Unable to handle kernel paging request at virtual address 00004000 on all my Exynos boards (U3, XU, XU3, HC1). I did not do a bisect yet but it might be connected with this commit. The call trace is: (strcmp) from [] (of_property_match_string+0x58/0xd0) (of_property_match_string) from [] (__of_clk_get_by_name+0x5c/0x130) (__of_clk_get_by_name) from [] (clk_get+0x34/0x70) (clk_get) from [] (devm_clk_get+0x38/0x74) (devm_clk_get) from [] (s5p_aes_probe+0xd4/0x4a0) (s5p_aes_probe) from [] (platform_drv_probe+0x6c/0xa4) (platform_drv_probe) from [] (really_probe+0x280/0x414) (really_probe) from [] (driver_probe_device+0x78/0x1c0) (driver_probe_device) from [] (device_driver_attach+0x58/0x60) (device_driver_attach) from [] (__driver_attach+0xfc/0x160) (__driver_attach) from [] (bus_for_each_dev+0x68/0xb4) (bus_for_each_dev) from [] (bus_add_driver+0x158/0x214) (bus_add_driver) from [] (driver_register+0x78/0x110) (driver_register) from [] (do_one_initcall+0x8c/0x404) Full log: https://krzk.eu/#/builders/21/builds/1153/steps/12/logs/serial0 The s5p_aes_probe address points here. Best regards, Krzysztof > > + if (IS_ERR(pdata->pclk)) { > + dev_err(dev, "failed to find clock %s\n", > + variant->clk_names[1]); > + err = -ENOENT; > + goto err_clk; > + } > + > + err = clk_prepare_enable(pdata->pclk); > + if (err < 0) { > + dev_err(dev, "Enabling clock %s failed, err %d\n", > + variant->clk_names[0], err); > + goto err_clk; > + } > + } else { > + pdata->pclk = NULL; > + } > + > spin_lock_init(&pdata->lock); > spin_lock_init(&pdata->hash_lock); > > @@ -2295,8 +2331,11 @@ static int s5p_aes_probe(struct platform_device *pdev) > tasklet_kill(&pdata->tasklet); > > err_irq: > - clk_disable_unprepare(pdata->clk); > + if (pdata->pclk) > + clk_disable_unprepare(pdata->pclk); > > +err_clk: > + clk_disable_unprepare(pdata->clk); > s5p_dev = NULL; > > return err; > @@ -2323,6 +2362,9 @@ static int s5p_aes_remove(struct platform_device *pdev) > pdata->use_hash = false; > } > > + if (pdata->pclk) > + clk_disable_unprepare(pdata->pclk); > + > clk_disable_unprepare(pdata->clk); > s5p_dev = NULL; > > -- > 2.20.1 >