From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: Alexander Shiyan <eagle.alexander923@gmail.com>
Cc: Barebox List <barebox@lists.infradead.org>
Subject: Re: RK3588 optee question
Date: Tue, 11 Aug 2026 16:07:25 +0200 [thread overview]
Message-ID: <92b327a9-0253-4fb1-80d3-31d4c1ebc2d7@pengutronix.de> (raw)
In-Reply-To: <CAP1tNvRB6qH2Ujv7=AvKL3kZTdaDrWO2gDZSKRucW7_g3pwoeg@mail.gmail.com>
Hi,
On 8/11/26 2:54 PM, Alexander Shiyan wrote:
> Hello.
>
> As far as I can see, this option (CFG_CORE_DYN_SHM) is enabled
> by default in out/arm-plat-rockchip/conf.mk
>
> Experiments with the open (BL31) TF-A version give a different error:
> ...
> NOTICE: BL31: v2.15.0(release):v2.15.0-274-gc64fe42d7
> NOTICE: BL31: Built : 14:41:34, Jul 6 2026
> ...
> arm-scmi firmware:scmi.of: SCMI Protocol v2.0 'rockchip:' Firmware version 0x0
> optee: smc_abi: probing for conduit method.
> WARNING: optee: smc_abi: api uid mismatch
> ERROR: optee firmware:optee.of: probe failed: Invalid argument
Huh, no idea off the top my head what is still missing in the OP-TEE or
TF-A configuration.
Cheers,
Ahmad
>
> вт, 11 авг. 2026 г. в 15:19, Ahmad Fatoum <a.fatoum@pengutronix.de>:
>>
>> Hi,
>>
>> On 8/11/26 1:51 PM, Alexander Shiyan wrote:
>>> Am I missing something?
>>> The following lines confuse me, what is these line mean?:
>>> ERROR: optee: smc_abi: driver requires OP-TEE dynamic shared memory support
>>> ERROR: optee firmware:optee.of: probe failed: Function not implemented
>>
>> Try enabling CFG_CORE_DYN_SHM in OP-TEE.
>>
>> Cheers,
>> Ahmad
>>
>>
>> --
>> Pengutronix e.K. | |
>> Steuerwalder Str. 21 | http://www.pengutronix.de/ |
>> 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
>> Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
>>
>
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2026-08-11 14:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-11 11:51 Alexander Shiyan
2026-08-11 12:19 ` Ahmad Fatoum
2026-08-11 12:54 ` Alexander Shiyan
2026-08-11 14:07 ` Ahmad Fatoum [this message]
2026-08-11 14:13 ` Alexander Shiyan
2026-08-12 6:25 ` Sascha Hauer
[not found] ` <6a7c11f4.bd9e1b36.35e6eb.4491SMTPIN_ADDED_MISSING@mx.google.com>
2026-08-12 14:44 ` Alexander Shiyan
2026-08-13 6:41 ` Sascha Hauer
[not found] ` <6a7d6747.1bdbcb37.263332.61abSMTPIN_ADDED_MISSING@mx.google.com>
2026-08-14 6:49 ` Alexander Shiyan
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=92b327a9-0253-4fb1-80d3-31d4c1ebc2d7@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=eagle.alexander923@gmail.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