public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Shyam Saini <shyamsaini@linux.microsoft.com>
To: linux-kernel@vger.kernel.org
Cc: linux-mmc@vger.kernel.org, op-tee@lists.trustedfirmware.org,
	linux-scsi@vger.kernel.org, shyamsaini@linux.microsoft.com
Subject: [RFC, PATCH 0/1] Replay Protected Memory Block (RPMB) driver
Date: Fri, 21 Jul 2023 18:40:36 -0700	[thread overview]
Message-ID: <20230722014037.42647-1-shyamsaini@linux.microsoft.com> (raw)

Hi everyone,

This is yet another attempt to come up with an RPMB API for the kernel.
This patch is based on patch 1 of last submission except few minor changes.
The last discussion of this was in the thread:

  Subject: [PATCH  v2 1/4] rpmb: add Replay Protected Memory Block (RPMB) subsystem
  Date: Tue,  5 Apr 2022 10:37:56 +0100 [thread overview]
  Message-ID: <20220405093759.1126835-2-alex.bennee@linaro.org>

The patch provides a simple RPMB driver. This is a RFC version and this
single driver can't be used by its own. It would require further work to
make use of API's provided by this driver.

Changes since the last posting:
  drop RPMB char driver
  drop virtio rpmb frontend driver
  drop rpmb: add RPBM access tool
  Rename get_write_count to get_write_counter
  Make return type for rpmb_set_key() function explicit

Alex Bennée (1):
  rpmb: add Replay Protected Memory Block (RPMB) driver

 MAINTAINERS           |   7 +
 drivers/Kconfig       |   1 +
 drivers/Makefile      |   2 +
 drivers/rpmb/Kconfig  |  11 ++
 drivers/rpmb/Makefile |   7 +
 drivers/rpmb/core.c   | 439 ++++++++++++++++++++++++++++++++++++++++++
 include/linux/rpmb.h  | 182 +++++++++++++++++
 7 files changed, 649 insertions(+)
 create mode 100644 drivers/rpmb/Kconfig
 create mode 100644 drivers/rpmb/Makefile
 create mode 100644 drivers/rpmb/core.c
 create mode 100644 include/linux/rpmb.h

-- 
2.34.1


             reply	other threads:[~2023-07-22  1:41 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-22  1:40 Shyam Saini [this message]
2023-07-22  1:40 ` [RFC, PATCH 1/1] rpmb: add Replay Protected Memory Block (RPMB) driver Shyam Saini
2023-07-22  3:11   ` Randy Dunlap
2023-07-26 20:10     ` Shyam Saini
2023-08-07 15:00   ` Ulf Hansson
2023-08-16 23:31     ` Shyam Saini
2023-08-21  9:49       ` Jerome Forissier
2023-08-21 10:03         ` Sumit Garg
2023-08-21 11:18           ` Jens Wiklander
2023-08-21 11:54             ` Sumit Garg
2023-08-21 11:55             ` Ilias Apalodimas
2023-08-21 12:17               ` Sumit Garg
2023-08-22 19:07                 ` Shyam Saini
2023-08-23  8:04                   ` Linus Walleij
2023-08-24 14:07                     ` Sumit Garg
2023-08-21 12:35             ` Jerome Forissier
2023-08-22 18:59           ` Shyam Saini
2023-08-24 14:01             ` Sumit Garg
2023-08-22 18:47         ` Shyam Saini
2023-08-07 21:02   ` Bart Van Assche
2023-08-22 18:43     ` Shyam Saini

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=20230722014037.42647-1-shyamsaini@linux.microsoft.com \
    --to=shyamsaini@linux.microsoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=op-tee@lists.trustedfirmware.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