Re: 回复: 回复: 回复: 回复: [PATCH v4 04/20] firmware: scmi: add pin control protocol support to SCMI agent

Marek Vasut marex at denx.de
Mon Mar 10 01:09:44 CET 2025


On 3/5/25 2:36 PM, Alice Guo (OSS) wrote:

Hello Alice,

>> - Basically duplicate the mechanism in 7940a93eb977 ("net: phy: Iterate over
>> both registered PHYs and struct phy_driver linker list"), call it e.g.
>> U_BOOT_SCMI_DRIVER()
>> - Switch SCMI drivers to use U_BOOT_SCMI_DRIVER , have each one list a
>> protocol ID (instead of the PHY IDs), and then use the scmi_agent-uclass.c to
>> iterate over all the linker lists
>>
>> About the MX95 specifics and handling those, it is possible to have two drivers
>> which support the same hardware compiled into U-Boot and have them decide
>> at bind time which driver should bind and which not, look at
>> drivers/mtd/renesas_rpc_hf.c rpc_hf_probe() and drivers/spi/renesas_rpc_spi.c
>> rpc_spi_bind() for example of doing this.
>>
>> I hope this helps untangle the SCMI implementation.
> 
> Thank you for providing the example. Please review my patch set.
> https://patchwork.ozlabs.org/project/uboot/patch/20250305-imx95-v1-2-286d15acbb8a@oss.nxp.com/
> https://patchwork.ozlabs.org/project/uboot/patch/20250305-imx95-v1-3-286d15acbb8a@oss.nxp.com/

I will try to review this this week, I apologize for the delayed replies.


More information about the U-Boot mailing list