public inbox for linux-crypto@vger.kernel.org
 help / color / mirror / Atom feed
From: Bharat Bhushan <bbhushan2@marvell.com>
To: <bbrezillon@kernel.org>, <schalla@marvell.com>,
	<herbert@gondor.apana.org.au>, <davem@davemloft.net>,
	<giovanni.cabiddu@intel.com>, <linux@treblig.org>,
	<bharatb.linux@gmail.com>, <linux-crypto@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>
Cc: <stable@vger.kernel.org>, Bharat Bhushan <bbhushan2@marvell.com>
Subject: [PATCH v2 0/2] crypto: octeontx2: Changes related to LMTST memory
Date: Fri, 16 May 2025 14:14:39 +0530	[thread overview]
Message-ID: <20250516084441.3721548-1-bbhushan2@marvell.com> (raw)

v1->v2:
 -  Removed changes in pci-host-common.c, those were comitted
    by mistake.

The first patch moves the initialization of cptlfs device info to the early
probe stage, also eliminate redundant initialization.
 
The second patch updates the driver to use a dynamically allocated
memory region for LMTST instead of the statically allocated memory
from firmware. It also adds myself as a maintainer.

Bharat Bhushan (2):
  crypto: octeontx2: Initialize cptlfs device info once
  crypto: octeontx2: Use dynamic allocated memory region for lmtst

 MAINTAINERS                                   |  1 +
 drivers/crypto/marvell/octeontx2/cn10k_cpt.c  | 89 ++++++++++++++-----
 drivers/crypto/marvell/octeontx2/cn10k_cpt.h  |  1 +
 .../marvell/octeontx2/otx2_cpt_common.h       |  1 +
 .../marvell/octeontx2/otx2_cpt_mbox_common.c  | 25 ++++++
 drivers/crypto/marvell/octeontx2/otx2_cptlf.c |  5 +-
 drivers/crypto/marvell/octeontx2/otx2_cptlf.h | 12 ++-
 .../marvell/octeontx2/otx2_cptpf_main.c       | 18 +++-
 .../marvell/octeontx2/otx2_cptpf_mbox.c       |  6 +-
 .../marvell/octeontx2/otx2_cptpf_ucode.c      |  2 -
 .../marvell/octeontx2/otx2_cptvf_main.c       | 19 ++--
 .../marvell/octeontx2/otx2_cptvf_mbox.c       |  1 +
 12 files changed, 133 insertions(+), 47 deletions(-)

-- 
2.34.1


             reply	other threads:[~2025-05-16  8:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-16  8:44 Bharat Bhushan [this message]
2025-05-16  8:44 ` [PATCH v2 1/2] crypto: octeontx2: Initialize cptlfs device info once Bharat Bhushan
2025-05-16  8:44 ` [PATCH v2 2/2] crypto: octeontx2: Use dynamic allocated memory region for lmtst Bharat Bhushan
2025-05-19  6:02 ` [PATCH v2 0/2] crypto: octeontx2: Changes related to LMTST memory Herbert Xu

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=20250516084441.3721548-1-bbhushan2@marvell.com \
    --to=bbhushan2@marvell.com \
    --cc=bbrezillon@kernel.org \
    --cc=bharatb.linux@gmail.com \
    --cc=davem@davemloft.net \
    --cc=giovanni.cabiddu@intel.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@treblig.org \
    --cc=schalla@marvell.com \
    --cc=stable@vger.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