From: Florian Fainelli <florian.fainelli@broadcom.com>
To: Avri Altman <Avri.Altman@sandisk.com>,
Ulf Hansson <ulf.hansson@linaro.org>,
Kamal Dasu <kamal.dasu@broadcom.com>,
Jens Wiklander <jens.wiklander@linaro.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"adrian.hunter@intel.com" <adrian.hunter@intel.com>,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
"robh@kernel.org" <robh@kernel.org>,
"krzk+dt@kernel.org" <krzk+dt@kernel.org>,
"conor+dt@kernel.org" <conor+dt@kernel.org>,
"wsa+renesas@sang-engineering.com"
<wsa+renesas@sang-engineering.com>,
"f.fainelli@gmail.com" <f.fainelli@gmail.com>,
"bcm-kernel-feedback-list@broadcom.com"
<bcm-kernel-feedback-list@broadcom.com>
Subject: Re: [PATCH RFC 0/3] mmc: sdhci-brcmstb: Add rpmb sharing support
Date: Tue, 11 Feb 2025 09:01:49 -0800 [thread overview]
Message-ID: <d51a9d7a-b942-4c3b-93d2-65b1bb04c8da@broadcom.com> (raw)
In-Reply-To: <PH7PR16MB61967C18645C64E582B222B6E5FD2@PH7PR16MB6196.namprd16.prod.outlook.com>
On 2/11/25 00:13, Avri Altman wrote:
>>>> This patch set adds support for Broadcom TZOS to read and write to
>>>> RPMB partition using synchronized access to the controller hardware.
> Practically it establishes a communication channel between the trust zone and the host controller regardless of the rpmb protocol.
> Or did I get it wrong?
Rather than communication channel, I would describe it as an arbitration
scheme between N participants, with guaranteed forward progress and
fairness between all participants.
The interest here is for one of those participants to own the eMMC
controller for a certain amount of time and indicate when it is done
with it. This is not specific to eMMC as this could scale to virtually
any piece of HW that is driven by transactions from a CPU, but the main
application is for allowing the Trusted OS to own the eMMC controller
for a short period of time in order to do its RPMB access, and then give
it back in the same state it found it to the next participant.
--
Florian
next prev parent reply other threads:[~2025-02-11 17:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-06 22:09 [PATCH RFC 0/3] mmc: sdhci-brcmstb: Add rpmb sharing support Kamal Dasu
2025-02-06 22:09 ` [PATCH RFC 1/3] mmc: add request_start() and request_done() mmc ops Kamal Dasu
2025-02-06 22:09 ` [PATCH RFC 2/3] dt-bindings: mmc: brcm,sdhci-brcmstb: Add sdio sharing support Kamal Dasu
2025-02-09 16:30 ` Krzysztof Kozlowski
2025-02-06 22:09 ` [PATCH RFC 3/3] mmc: sdhci-brcmstb: Add rpmb sharing support in host driver Kamal Dasu
2025-02-10 13:21 ` [PATCH RFC 0/3] mmc: sdhci-brcmstb: Add rpmb sharing support Ulf Hansson
2025-02-10 17:09 ` Florian Fainelli
2025-02-11 8:13 ` Avri Altman
2025-02-11 17:01 ` Florian Fainelli [this message]
2025-02-11 18:39 ` Avri Altman
2025-03-12 13:17 ` Ulf Hansson
2025-03-12 17:51 ` 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=d51a9d7a-b942-4c3b-93d2-65b1bb04c8da@broadcom.com \
--to=florian.fainelli@broadcom.com \
--cc=Avri.Altman@sandisk.com \
--cc=adrian.hunter@intel.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=conor+dt@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=jens.wiklander@linaro.org \
--cc=kamal.dasu@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=robh@kernel.org \
--cc=ulf.hansson@linaro.org \
--cc=wsa+renesas@sang-engineering.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox