From: Krzysztof Kozlowski <krzk@kernel.org>
To: Md Sadre Alam <quic_mdalam@quicinc.com>,
vkoul@kernel.org, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, andersson@kernel.org,
konradybcio@kernel.org, thara.gopinath@gmail.com,
herbert@gondor.apana.org.au, davem@davemloft.net,
gustavoars@kernel.org, u.kleine-koenig@pengutronix.de,
kees@kernel.org, agross@kernel.org,
linux-arm-msm@vger.kernel.org, dmaengine@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-crypto@vger.kernel.org
Cc: quic_srichara@quicinc.com, quic_varada@quicinc.com,
quic_utiwari@quicinc.com
Subject: Re: [PATCH v2 04/16] crypto: qce - Add support for crypto address read
Date: Sat, 17 Aug 2024 11:10:57 +0200 [thread overview]
Message-ID: <72cef34a-acb0-4278-984c-dadd53817b5d@kernel.org> (raw)
In-Reply-To: <20240815085725.2740390-5-quic_mdalam@quicinc.com>
On 15/08/2024 10:57, Md Sadre Alam wrote:
> Get crypto base address from DT. This will use for
> command descriptor support for crypto register r/w
> via BAM/DMA
All your commit messages are oddly wrapped. This does not make reading
it easy...
>
> Signed-off-by: Md Sadre Alam <quic_mdalam@quicinc.com>
> ---
> Change in [v2]
>
> * Addressed all comments from v1
>
> Change in [v1]
>
> * Added support to read crypto base address from dt
>
> drivers/crypto/qce/core.c | 13 ++++++++++++-
> drivers/crypto/qce/core.h | 1 +
> 2 files changed, 13 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/crypto/qce/core.c b/drivers/crypto/qce/core.c
> index 28b5fd823827..9b23a948078a 100644
> --- a/drivers/crypto/qce/core.c
> +++ b/drivers/crypto/qce/core.c
> @@ -192,6 +192,7 @@ static int qce_crypto_probe(struct platform_device *pdev)
> {
> struct device *dev = &pdev->dev;
> struct qce_device *qce;
> + struct resource *res;
> int ret;
>
> qce = devm_kzalloc(dev, sizeof(*qce), GFP_KERNEL);
> @@ -201,10 +202,16 @@ static int qce_crypto_probe(struct platform_device *pdev)
> qce->dev = dev;
> platform_set_drvdata(pdev, qce);
>
> - qce->base = devm_platform_ioremap_resource(pdev, 0);
> + qce->base = devm_platform_get_and_ioremap_resource(pdev, 0, &res);
> if (IS_ERR(qce->base))
> return PTR_ERR(qce->base);
>
> + qce->base_dma = dma_map_resource(dev, res->start,
> + resource_size(res),
> + DMA_BIDIRECTIONAL, 0);
> + if (dma_mapping_error(dev, qce->base_dma))
> + return -ENXIO;
> +
> ret = dma_set_mask_and_coherent(dev, DMA_BIT_MASK(32));
> if (ret < 0)
> return ret;
And how do you handle error paths?
> @@ -280,6 +287,7 @@ static int qce_crypto_probe(struct platform_device *pdev)
> static void qce_crypto_remove(struct platform_device *pdev)
> {
> struct qce_device *qce = platform_get_drvdata(pdev);
> + struct resource *res = platform_get_resource(pdev, IORESOURCE_MEM, 0);
>
> tasklet_kill(&qce->done_tasklet);
> qce_unregister_algs(qce);
> @@ -287,6 +295,9 @@ static void qce_crypto_remove(struct platform_device *pdev)
> clk_disable_unprepare(qce->bus);
> clk_disable_unprepare(qce->iface);
> clk_disable_unprepare(qce->core);
> +
> + dma_unmap_resource(&pdev->dev, qce->base_dma, resource_size(res),
> + DMA_BIDIRECTIONAL, 0);
If you add code to the remove callback, not adding it to error paths is
suspicious by itself...
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-08-17 9:11 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-15 8:57 [PATCH v2 00/16] Add cmd descriptor support Md Sadre Alam
2024-08-15 8:57 ` [PATCH v2 01/16] dt-bindings: dma: qcom,bam: Add bam pipe lock Md Sadre Alam
2024-08-16 15:53 ` Bjorn Andersson
2024-08-21 4:54 ` Md Sadre Alam
2024-08-17 9:08 ` Krzysztof Kozlowski
2024-08-21 16:34 ` Md Sadre Alam
2024-08-22 6:27 ` Krzysztof Kozlowski
2024-08-22 11:45 ` Md Sadre Alam
2024-08-23 9:07 ` Krzysztof Kozlowski
2024-08-24 7:07 ` Md Sadre Alam
2024-08-23 15:39 ` Manivannan Sadhasivam
2024-08-24 7:04 ` Md Sadre Alam
2024-08-15 8:57 ` [PATCH v2 02/16] dmaengine: qcom: bam_dma: add bam_pipe_lock dt property Md Sadre Alam
2024-08-17 9:08 ` Krzysztof Kozlowski
2024-08-21 16:36 ` Md Sadre Alam
2024-08-15 8:57 ` [PATCH v2 03/16] dmaengine: qcom: bam_dma: add LOCK & UNLOCK flag support Md Sadre Alam
2024-08-16 16:22 ` Bjorn Andersson
2024-08-21 16:31 ` Md Sadre Alam
2024-08-15 8:57 ` [PATCH v2 04/16] crypto: qce - Add support for crypto address read Md Sadre Alam
2024-08-17 9:10 ` Krzysztof Kozlowski [this message]
2024-08-21 16:40 ` Md Sadre Alam
2024-08-15 8:57 ` [PATCH v2 05/16] crypto: qce - Add bam dma support for crypto register r/w Md Sadre Alam
2024-08-15 8:57 ` [PATCH v2 06/16] crypto: qce - Convert register r/w for skcipher via BAM/DMA Md Sadre Alam
2024-08-15 8:57 ` [PATCH v2 07/16] crypto: qce - Convert register r/w for sha " Md Sadre Alam
2024-08-15 8:57 ` [PATCH v2 08/16] crypto: qce - Convert register r/w for aead " Md Sadre Alam
2024-08-15 8:57 ` [PATCH v2 09/16] crypto: qce - Add LOCK and UNLOCK flag support Md Sadre Alam
2024-08-15 8:57 ` [PATCH v2 10/16] crypto: qce - Add support for lock aquire,lock release api Md Sadre Alam
2024-08-16 16:38 ` Bjorn Andersson
2024-08-21 5:14 ` Md Sadre Alam
2024-08-15 8:57 ` [PATCH v2 11/16] crypto: qce - Add support for lock/unlock in skcipher Md Sadre Alam
2024-08-15 8:57 ` [PATCH v2 12/16] crypto: qce - Add support for lock/unlock in sha Md Sadre Alam
2024-08-15 8:57 ` [PATCH v2 13/16] crypto: qce - Add support for lock/unlock in aead Md Sadre Alam
2024-08-15 8:57 ` [PATCH v2 14/16] arm64: dts: qcom: ipq9574: enable bam pipe locking/unlocking Md Sadre Alam
2024-08-16 16:40 ` Bjorn Andersson
2024-08-21 5:16 ` Md Sadre Alam
2024-08-15 8:57 ` [PATCH v2 15/16] arm64: dts: qcom: ipq8074: " Md Sadre Alam
2024-08-15 8:57 ` [PATCH v2 16/16] arm64: dts: qcom: ipq6018: " Md Sadre Alam
2024-08-15 13:08 ` [PATCH v2 00/16] Add cmd descriptor support Caleb Connolly
2024-08-16 12:03 ` Md Sadre Alam
2024-08-16 15:45 ` Bjorn Andersson
2024-09-06 7:06 ` Md Sadre Alam
2024-08-16 16:01 ` Bjorn Andersson
2024-08-21 4:57 ` Md Sadre Alam
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=72cef34a-acb0-4278-984c-dadd53817b5d@kernel.org \
--to=krzk@kernel.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=gustavoars@kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=kees@kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_mdalam@quicinc.com \
--cc=quic_srichara@quicinc.com \
--cc=quic_utiwari@quicinc.com \
--cc=quic_varada@quicinc.com \
--cc=robh@kernel.org \
--cc=thara.gopinath@gmail.com \
--cc=u.kleine-koenig@pengutronix.de \
--cc=vkoul@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