On 1/7/25 7:39 AM, Alice Guo (OSS) wrote:
-----邮件原件-----
发件人: Marek Vasut <[email protected]>
发送时间: 2025年1月7日 4:46
收件人: Alice Guo (OSS) <[email protected]>; Tom Rini
<[email protected]>; Stefano Babic <[email protected]>; Fabio Estevam
<[email protected]>; dl-uboot-imx <[email protected]>; Lukasz
Majewski <[email protected]>; Sean Anderson <[email protected]>; Simon
Glass <[email protected]>; Alper Nebi Yasak <[email protected]>
抄送: [email protected]; [email protected]; Peng Fan
<[email protected]>; Ranjani Vaidyanathan
<[email protected]>; Ye Li <[email protected]>
主题: Re: 回复: [EXT] Re: [PATCH v3 03/17] pinctrl: nxp: add SCMI pin control
protocol driver
On 1/6/25 10:56 AM, Alice Guo (OSS) wrote:
This patch provides a driver for the SCMI pin control protocol which
is based on ARM's System Control and Management Interface (SCMI) 3.2.
Currently, only the PINCTRL_CONFIG_SET command is implemented.
What is the SCMI provider for this platform ?
Hi Marek,
System Manager which runs on M core sets pin or group configurations.
U-Boot sends a SCMI message to System Manager to perform hardware
operations. You can refer to the source code for details:
https://github.com/nxp-imx/imx-sm.
Can I use optee-os as a SCMI provider instead ?
You cannot replace System Manager with optee-os.
I think optee-os is also capable of being SCMI provider, so I have to
wonder, why does NXP use custom hand-written SCMI provider instead of
something already available, like that optee-os ?
And one more question, would it be possible to make U-Boot NOT depend on
SCMI at all and instead have regular clock/pinctrl drivers which can
configure the hardware using plain register writes, like it is done on
MX8M and older SoCs ? That would surely make hardware bring up easier .
