> -----邮件原件----- > 发件人: Marek Vasut <ma...@denx.de> > 发送时间: 2025年4月1日 20:53 > 收件人: Alice Guo (OSS) <alice....@oss.nxp.com>; Fabio Estevam > <feste...@gmail.com>; Tom Rini <tr...@konsulko.com> > 抄送: Lukasz Majewski <lu...@denx.de>; Sean Anderson > <sean...@gmail.com>; Simon Glass <s...@chromium.org>; Peng Fan > <peng....@nxp.com>; dl-uboot-imx <uboot-...@nxp.com>; Alper Nebi Yasak > <alpernebiya...@gmail.com>; Alice Guo <alice....@nxp.com>; Lothar > Waßmann <l...@karo-electronics.de>; u-boot@lists.denx.de; Ranjani > Vaidyanathan <ranjani.vaidyanat...@nxp.com>; Ye Li <ye...@nxp.com>; Peng > Fan (OSS) <peng....@oss.nxp.com> > 主题: Re: 回复: [PATCH v8 02/19] pinctrl: nxp: add a pin controller driver > based on SCMI pin control protocol > > On 4/1/25 12:57 PM, Alice Guo (OSS) wrote: > > Hello Alice, > > >>>>> Both use same ID 0x19. > >>>>> > >>>>> It is fine to use below, if it is fine to you. > >>>>> SCMI_PROTOCOL_ID_PINCTRL_IMX = 0x19. > >>>> How does the kernel discern which driver it should use to > >>>> communicate with the SCMI provider if both drivers are compiled into > the kernel ? > >>> > >>> There is a check in drivers probe. Only one will succeed. > >> > >> I have to admit, this is just ... uhhh :( > >> > >> But I think now, we should also have a driver-side check and two > >> separate drivers, similar to this patch: > >> > >> [PATCH] power: regulator: scmi: Move regulator subnode hack to > >> scmi_regulator > > > > Hi Marek, > > > > When will this patch "[PATCH] power: regulator: scmi: Move regulator > subnode hack to scmi_regulator" be applied to the uboot next branch? I have > already made the next version patch set based on this patch. > Fabio/Tom ?
U-Boot source code I used is cloned by git clone https://source.denx.de/u-boot/u-boot.git
