From: Kamal Dasu <kamal.dasu@broadcom.com>
To: andersson@kernel.org, baolin.wang@linux.alibaba.com,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
florian.fainelli@broadcom.com, ulf.hansson@linaro.org,
adrian.hunter@intel.com
Cc: bcm-kernel-feedback-list@broadcom.com, kamal.dasu@broadcom.com,
linux-remoteproc@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-mmc@vger.kernel.org
Subject: [PATCH 0/4] mmc: sdhci-brcmstb: rpmb sharing by claiming host for TZOS
Date: Fri, 11 Jul 2025 11:42:17 -0400 [thread overview]
Message-ID: <20250711154221.928164-2-kamal.dasu@broadcom.com> (raw)
In-Reply-To: <20250711154221.928164-1-kamal.dasu@broadcom.com>
This patch adds support to claim host for TZOS RPMB access and synchronized
access to the controller hardware using hwspinlock framework.
To achieve this Linux OS and the secure TZOS make use of:
- shared hardware semaphore register
- a set of SDIO shared work registers and
- IPI interrupt registers
The currently running OS that needs access to the controller puts itself in its
slot of work register and if its next in line it can try to grab the hardware
semaphore and complete its mmc requests. The shared work registers indicate next
in queue to access the controller, and current agent in the queue. Next agent
queue state is changed under the hwspinlock is owned by the current OS accessing
the controller hardware before release the semaphore, send and receive IPI
interrupts between linux and secure world are used to indicate completion of
transaction to the waiting OS. TZOS has its own RPMB driver which accesses
partition when it wants to read/write RPMB frames. Current implementation
assumes Linux and TZOS as the two work agents.
Kamal Dasu (4):
dt-bindings: brcmstb-hwspinlock: support for hwspinlock
hwspinlock: brcmstb hardware semaphore support
dt-bindings: mmc: add brcmstb share register and hwlocks reference
mmc: sdhci-brcmstb: rpmb sharing by claiming host for TZOS
.../hwlock/brcm,brcmstb-hwspinlock.yaml | 36 +++
.../bindings/mmc/brcm,sdhci-brcmstb.yaml | 29 ++-
drivers/hwspinlock/Kconfig | 9 +
drivers/hwspinlock/Makefile | 1 +
drivers/hwspinlock/brcmstb_hwspinlock.c | 98 +++++++
drivers/mmc/host/sdhci-brcmstb.c | 243 +++++++++++++++++-
6 files changed, 413 insertions(+), 3 deletions(-)
create mode 100644 Documentation/devicetree/bindings/hwlock/brcm,brcmstb-hwspinlock.yaml
create mode 100644 drivers/hwspinlock/brcmstb_hwspinlock.c
--
2.34.1
next prev parent reply other threads:[~2025-07-11 15:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-11 15:42 Kamal Dasu
2025-07-11 15:42 ` Kamal Dasu [this message]
2025-07-11 15:42 ` [PATCH 1/4] dt-bindings: brcmstb-hwspinlock: support for hwspinlock Kamal Dasu
2025-07-13 8:37 ` Krzysztof Kozlowski
2025-07-11 15:42 ` [PATCH 2/4] hwspinlock: brcmstb hardware semaphore support Kamal Dasu
2025-07-13 6:33 ` kernel test robot
2025-07-11 15:42 ` [PATCH 3/4] dt-bindings: mmc: add brcmstb share register and hwlocks reference Kamal Dasu
2025-07-13 8:40 ` Krzysztof Kozlowski
2025-07-11 15:42 ` [PATCH 4/4] mmc: sdhci-brcmstb: rpmb sharing by claiming host for TZOS Kamal Dasu
2025-07-13 8:44 ` Krzysztof Kozlowski
2025-07-28 9:11 ` [PATCH 0/4] " Adrian Hunter
2025-07-31 16:43 ` Florian Fainelli
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=20250711154221.928164-2-kamal.dasu@broadcom.com \
--to=kamal.dasu@broadcom.com \
--cc=adrian.hunter@intel.com \
--cc=andersson@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=florian.fainelli@broadcom.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=robh@kernel.org \
--cc=ulf.hansson@linaro.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
all inboxes | Powered by JetHome®