Hi Charles, > > > > Boot time tweaking of any attribute or any platform state changes via > > scripts is also possible as you mentioned. The configuration can be > > board specific and expressed in uboot environment scripts instead of > > compiled in driver code. > > Most people will want the later, i.e. compiled code.
It's an assumption and we should not assume what people will want. That's the thing with infra related support which can be used to cater in many forms. > > That doesn't mean you need to modify all the drivers being used on your > machine because U-Boot already has an abstraction layers for clocks, > power-domains, resets, and other which are relevant to RPMI. > > If you make a driver that implements the clock, power-domain, etc. API and > implement it so that it delegates to RPMI, you can leverage the existing > drivers and you don't have to add "mpxy" commands to your bootscript. Need > to use the network? you call "tftpboot" which calls your network device > driver which calls your clock driver which calls your RPMI driver. Need to > use the NOR? you call "mtd" and the same magic happens. > > I posted an implementation of this, please have a look at it: > > https://lore.kernel.org/all/[email protected]/ > > If you want, we can combine our two patchsets into something that takes > the best of both. I have no problem with that. > > I can take your patch that adds the "mpxy" command and add it to my > patchset with a few adjustments. Sure > > Thanks, > Charles
