Received: by 2002:a05:6358:9144:b0:117:f937:c515 with SMTP id r4csp144558rwr; Wed, 26 Apr 2023 22:16:53 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ4DS6HcbzCTdfT9kU+HrQmxbYfGIJTaXzkVEHYNv4wQILq/jaZ47FZpFNYC61yp4U8BQY5O X-Received: by 2002:a17:90a:c89:b0:249:78db:2635 with SMTP id v9-20020a17090a0c8900b0024978db2635mr658527pja.0.1682572613556; Wed, 26 Apr 2023 22:16:53 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1682572613; cv=none; d=google.com; s=arc-20160816; b=Q329hwAK+EVNN9+dxSIBpQJf41mMnR90WDTgrcvBGZ5Slyn5No5WeakW4wGJ4gZlW4 nBuBFZQg5muJlD8Gm9mhGJMQucXDMFsmzKljTNPOe6WAfv6j7iGlnm9BL7T7H1FDxSUz 17aBdb0pjsm4KHMXgVEIk/0zcmSmA7MPwpb3focjPRppqvPCS6/theCc676tdXsSzZRl M2BUwU88ganWKLXB5ex4jvXVr8IN6R+fI8ukfHTtq94ssonoGOm6kPQpgEM7B6cvRVXN 9lV6URSZ6ylqiwipxVNP3vyl9c5NS57sC/v49qnyHwO4ElvrzFy12AzGpTVWBrNiHMn4 oEtQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to:from :content-language:references:cc:to:subject:user-agent:mime-version :date:message-id; bh=EvdLM4Z9T+D8kilbYef4uKrZWSBulPcF92FHajrnkik=; b=A/tzIn+KEe6Uxx47aofWkQqdAfEQmolJPzStzR1Xlo3HBb611/kJ3nomrW0AqF1PqB YJsfOh49Lozb6DD/w9fbD/wYTiabpqBp67WkEI4FC5YIQz1YPNTMzJenOEnwt1UXBt9J HPLvs7JMj8NzkendMPpDuYKDLssU3c/dKlirvlWHYOPpXNKAfUnshaTHXmFJYWiIMtr2 J3cXvJSgXhM87nxAXluLzfhG/yjU653qkrG0lrZgfwdvr/wf5JVFxgG/wkvFKRBCVNqH 0MyonBHrpaWHdTtuUZ5j8KTfrPpDzL7ausKQEv+LMgLFkpsy3aHXeMDyT1ggYMw6EvRt A3qQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id v67-20020a632f46000000b005289d0633e6si965068pgv.733.2023.04.26.22.16.31; Wed, 26 Apr 2023 22:16:53 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S242586AbjD0FHN convert rfc822-to-8bit (ORCPT + 99 others); Thu, 27 Apr 2023 01:07:13 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:43272 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S242675AbjD0FHM (ORCPT ); Thu, 27 Apr 2023 01:07:12 -0400 Received: from fd01.gateway.ufhost.com (fd01.gateway.ufhost.com [61.152.239.71]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 2247B4489; Wed, 26 Apr 2023 22:07:08 -0700 (PDT) Received: from EXMBX166.cuchost.com (unknown [175.102.18.54]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "EXMBX166", Issuer "EXMBX166" (not verified)) by fd01.gateway.ufhost.com (Postfix) with ESMTP id E186C24E12B; Thu, 27 Apr 2023 13:06:54 +0800 (CST) Received: from EXMBX168.cuchost.com (172.16.6.78) by EXMBX166.cuchost.com (172.16.6.76) with Microsoft SMTP Server (TLS) id 15.0.1497.42; Thu, 27 Apr 2023 13:06:54 +0800 Received: from [192.168.155.161] (202.188.176.82) by EXMBX168.cuchost.com (172.16.6.78) with Microsoft SMTP Server (TLS) id 15.0.1497.42; Thu, 27 Apr 2023 13:06:51 +0800 Message-ID: <65fde5d5-6d86-c94e-9985-231e81641386@starfivetech.com> Date: Thu, 27 Apr 2023 13:06:49 +0800 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.10.1 Subject: Re: [PATCH v6 2/4] crypto: starfive - Add crypto engine support To: Christophe JAILLET CC: , , , , , , , , , References: <20230426065848.842221-1-jiajie.ho@starfivetech.com> <20230426065848.842221-3-jiajie.ho@starfivetech.com> Content-Language: en-US From: Jia Jie Ho In-Reply-To: Content-Type: text/plain; charset="UTF-8" X-Originating-IP: [202.188.176.82] X-ClientProxiedBy: EXCAS066.cuchost.com (172.16.6.26) To EXMBX168.cuchost.com (172.16.6.78) X-YovoleRuleAgent: yovoleflag Content-Transfer-Encoding: 8BIT X-Spam-Status: No, score=-3.3 required=5.0 tests=BAYES_00,NICE_REPLY_A, RCVD_IN_MSPIKE_H2,SPF_HELO_PASS,SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-crypto@vger.kernel.org On 26/4/2023 3:56 pm, Christophe JAILLET wrote: > Le 26/04/2023 à 08:58, Jia Jie Ho a écrit : >> Adding device probe and DMA init for StarFive cryptographic module. >> >> Co-developed-by: Huan Feng >> Signed-off-by: Huan Feng >> Signed-off-by: Jia Jie Ho >> --- >>   MAINTAINERS                           |   7 + >>   drivers/crypto/Kconfig                |   1 + >>   drivers/crypto/Makefile               |   1 + >>   drivers/crypto/starfive/Kconfig       |  17 +++ >>   drivers/crypto/starfive/Makefile      |   4 + >>   drivers/crypto/starfive/jh7110-cryp.c | 199 ++++++++++++++++++++++++++ >>   drivers/crypto/starfive/jh7110-cryp.h |  63 ++++++++ >>   7 files changed, 292 insertions(+) >>   create mode 100644 drivers/crypto/starfive/Kconfig >>   create mode 100644 drivers/crypto/starfive/Makefile >>   create mode 100644 drivers/crypto/starfive/jh7110-cryp.c >>   create mode 100644 drivers/crypto/starfive/jh7110-cryp.h >> [...] >> + >> +static int starfive_dma_init(struct starfive_cryp_dev *cryp) >> +{ >> +    dma_cap_mask_t mask; >> + >> +    cryp->tx = NULL; >> +    cryp->rx = NULL; > > Harmless, but 'crypt' is kzalloc()'ed, so these fields are already NULL. > Hi Christophe, I'll remove these in the next version. >> + >> +    dma_cap_zero(mask); >> +    dma_cap_set(DMA_SLAVE, mask); >> + >> +    cryp->tx = dma_request_chan(cryp->dev, "tx"); >> +    if (IS_ERR(cryp->tx)) >> +        return dev_err_probe(cryp->dev, PTR_ERR(cryp->tx), >> +                     "Error requesting tx dma channel.\n"); >> + >> +    cryp->rx = dma_request_chan(cryp->dev, "rx"); >> +    if (IS_ERR(cryp->rx)) { >> +        dma_release_channel(cryp->tx); >> +        return dev_err_probe(cryp->dev, PTR_ERR(cryp->rx), >> +                     "Error requesting rx dma channel.\n"); >> +    } >> + >> +    return 0; >> +} >> + >> +static void starfive_dma_cleanup(struct starfive_cryp_dev *cryp) >> +{ >> +    dma_release_channel(cryp->tx); >> +    dma_release_channel(cryp->rx); >> +} >> + >> +static int starfive_cryp_probe(struct platform_device *pdev) >> +{ [...] >> + >> +    ret = crypto_engine_start(cryp->engine); >> +    if (ret) >> +        goto err_engine_start; >> + >> +    return 0; >> + >> +err_engine_start: >> +    crypto_engine_exit(cryp->engine); >> +err_engine: >> +    starfive_dma_cleanup(cryp); >> +err_dma_init: >> +    spin_lock(&dev_list.lock); >> +    list_del(&cryp->list); >> +    spin_unlock(&dev_list.lock); > > I think that there should be: >     clk_disable_unprepare(cryp->hclk); >     clk_disable_unprepare(cryp->ahb); >     reset_control_assert(cryp->rst); > > as in the remove function. > Will add these in next version. >> + >> +    return ret; >> +} >> + >> +static int starfive_cryp_remove(struct platform_device *pdev) >> +{ >> +    struct starfive_cryp_dev *cryp = platform_get_drvdata(pdev); >> + >> +    if (!cryp) >> +        return -ENODEV; > > I don't think that this can happen. > I'll update this too along with your other comments. Thanks for taking time reviewing this patch series. Best regards, Jia Jie