From: Krzysztof Kozlowski <krzk@kernel.org>
To: Pavitrakumar Managutte <pavitrakumarm@vayavyalabs.com>
Cc: linux-crypto@vger.kernel.org, devicetree@vger.kernel.org,
herbert@gondor.apana.org.au, Ruud.Derwig@synopsys.com,
manjunath.hadli@vayavyalabs.com, adityak@vayavyalabs.com,
Bhoomika Kadabi <bhoomikak@vayavyalabs.com>
Subject: Re: [PATCH v1 1/6] dt-bindings: crypto: Document support for SPAcc
Date: Mon, 28 Apr 2025 21:05:29 +0200 [thread overview]
Message-ID: <78062089-3cb1-45e2-818d-fa99c746bb30@kernel.org> (raw)
In-Reply-To: <CALxtO0nFtAiK8oG=7k8bhxwwxcQo0XZawEbkRG9Prg4z6JshXQ@mail.gmail.com>
On 28/04/2025 12:28, Pavitrakumar Managutte wrote:
> Hi Krzysztof,
> Its not possible to use it outside of the SoC. So for the current
> SPAcc IP testing we flash it to the PL part of the Zynq. Post which it
> behaves like a peripheral sitting on the system bus. The device is
> memory mapped and its interrupt is connected to GIC. A platform driver
> works perfectly in this case and that's what we have.
> All the drivers that we have in the kernel are for crypto
> hardware/engines, which already are available as part of some SoC in
> the market. But in our case its still an IP. Since I dont have any
> reference/expertise, it would be great if you could suggest a way to
> handle such a case.
Respond inline, instead of top-posting.
There are IP blocks which do not require much of per-soc customization
so with proper arguments this could go. But if you have a working
hardware, then just describe that hardware in the bindings.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-04-28 19:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-23 10:15 [PATCH v1 0/6] Add SPAcc Crypto Driver Pavitrakumar M
2025-04-23 10:15 ` [PATCH v1 1/6] dt-bindings: crypto: Document support for SPAcc Pavitrakumar M
2025-04-23 12:53 ` Krzysztof Kozlowski
2025-04-28 8:26 ` Pavitrakumar Managutte
[not found] ` <CALxtO0k0jeZF=Y5Ut_yhX8DxC3hVHWpnrcdJeBXP_GpA=O5T4w@mail.gmail.com>
2025-04-28 9:11 ` Krzysztof Kozlowski
2025-04-28 10:28 ` Pavitrakumar Managutte
2025-04-28 19:05 ` Krzysztof Kozlowski [this message]
2025-04-23 10:15 ` [PATCH v1 2/6] Add SPAcc Skcipher support Pavitrakumar M
2025-04-23 10:15 ` [PATCH v1 3/6] Add SPAcc AUTODETECT Support Pavitrakumar M
2025-04-23 10:15 ` [PATCH v1 4/6] Add SPAcc ahash support Pavitrakumar M
2025-04-27 9:10 ` Herbert Xu
2025-04-29 10:46 ` Pavitrakumar Managutte
2025-04-23 10:15 ` [PATCH v1 5/6] Add SPAcc AEAD support Pavitrakumar M
2025-04-23 10:15 ` [PATCH v1 6/6] Add SPAcc Kconfig and Makefile Pavitrakumar M
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=78062089-3cb1-45e2-818d-fa99c746bb30@kernel.org \
--to=krzk@kernel.org \
--cc=Ruud.Derwig@synopsys.com \
--cc=adityak@vayavyalabs.com \
--cc=bhoomikak@vayavyalabs.com \
--cc=devicetree@vger.kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=manjunath.hadli@vayavyalabs.com \
--cc=pavitrakumarm@vayavyalabs.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.