On Fri, 17 Nov 2023 at 19:36, Sui Jingfeng <sui.jingfeng@xxxxxxxxx> wrote: > > Hi, > > > On 2023/11/17 17:03, Dmitry Baryshkov wrote: > > On Fri, 17 Nov 2023 at 06:24, Sui Jingfeng <sui.jingfeng@xxxxxxxxx> wrote: > >> Hi, > >> > >> On 2023/11/16 23:23, Dmitry Baryshkov wrote: > >>>>>> Then you will need some way (fwnode?) to > >>>>>> discover the bridge chain. And at the last point you will get into the > >>>>>> device data and/or properties business. > >>>>>> > >>>>> No, leave that chance to a more better programmer and forgive me please, > >>>>> too difficult, I'm afraid of not able to solve. Thanks a lot for the > >>>>> trust! > >>> From my point of view: no. > >> > >> I respect the fact that the community prefer generic mechanisms. > >> If our approach is not what the community want, can I switch back > >> to my previous solution? I can reduce the duplication of our > >> localized it66121 driver to a minimal, rewrite it until it meets > >> the community's requirement. I know our device looks weird and > >> our approach is not elegant. But at the very least, we could not > >> mess the community's design up by localize. Otherwise, I don't know > >> what is the better approach to solve such a problem. > >> > >> Can I switch back or any other ideas? > > I keep on repeating: create the i2c device from your root device > > driver, which parses BIOS data. > > > You didn't focus on solve the problem, You are focus on solving me. > How does the method that parsing BIOS data can be generic and applied > universally? Parsing BIOS data is unique to your platform (as well as your BIOS tables). However using and extending (instead of replacing it just for your platform) is a generic item. -- With best wishes Dmitry
