From: Tom Rini <trini@konsulko.com>
To: Nishanth Menon <nm@ti.com>
Cc: Vignesh Raghavendra <vigneshr@ti.com>,
praneeth@ti.com, d-gole@ti.com, u-boot@lists.denx.de
Subject: Re: [PATCH] mailbox: k3-sec-proxy: Fill non-message tx data fields with 0x0
Date: Tue, 25 Jul 2023 17:12:41 -0400 [thread overview]
Message-ID: <20230725211241.GG3630934@bill-the-cat> (raw)
In-Reply-To: <20230620181709.38058-1-nm@ti.com>
[-- Attachment #1: Type: text/plain, Size: 1459 bytes --]
On Tue, Jun 20, 2023 at 01:17:09PM -0500, Nishanth Menon wrote:
> Sec proxy data buffer is 60 bytes with the last of the registers
> indicating transmission completion. This however poses a bit of a
> challenge.
>
> The backing memory for sec_proxy is regular memory, and all sec proxy
> does is to trigger a burst of all 60 bytes of data over to the target
> thread backing ring accelerator. It doesn't do a memory scrub when
> it moves data out in the burst. When we transmit multiple messages,
> remnants of previous message is also transmitted which results in
> some random data being set in TISCI fields of messages that have been
> expanded forward.
>
> The entire concept of backward compatibility hinges on the fact that
> the unused message fields remain 0x0 allowing for 0x0 value to be
> specially considered when backward compatibility of message extension
> is done.
>
> So, instead of just writing the completion register, we continue
> to fill the message buffer up with 0x0 (note: for partial message
> involving completion, we already do this).
>
> This allows us to scale and introduce ABI changes back also work with
> other boot stages that may have left data in the internal memory.
>
> While at this, drop the unused accessor function.
>
> Fixes: f9aa41023bd9 ("mailbox: Introduce K3 Secure Proxy Driver")
> Signed-off-by: Nishanth Menon <nm@ti.com>
Applied to u-boot/master, thanks!
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
prev parent reply other threads:[~2023-07-25 21:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-20 18:17 [PATCH] mailbox: k3-sec-proxy: Fill non-message tx data fields with 0x0 Nishanth Menon
2023-07-25 21:12 ` Tom Rini [this message]
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=20230725211241.GG3630934@bill-the-cat \
--to=trini@konsulko.com \
--cc=d-gole@ti.com \
--cc=nm@ti.com \
--cc=praneeth@ti.com \
--cc=u-boot@lists.denx.de \
--cc=vigneshr@ti.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