On Mon, 22 Jun 2020, Frank Rowand wrote: > On 2020-06-22 03:09, Lee Jones wrote: > > On Thu, 11 Jun 2020, Lee Jones wrote: > > > >> Currently, when a child platform device (sometimes referred to as a > >> sub-device) is registered via the Multi-Functional Device (MFD) API, > >> the framework attempts to match the newly registered platform device > >> with its associated Device Tree (OF) node. Until now, the device has > >> been allocated the first node found with an identical OF compatible > >> string. Unfortunately, if there are, say for example '3' devices > >> which are to be handled by the same driver and therefore have the same > >> compatible string, each of them will be allocated a pointer to the > >> *first* node. > > > > Any more reviews/comments before I apply this? > > > > Yes, outstanding issues, so please do not apply. > > Shortly after you sent this email, you sent a reply to one of my > earlier emails in this thread. I have replied to that email, > so we still have an ongoing conversation where we are trying > to resolve my understanding of the problem and whether the > solution is appropriate. Happy to discuss whatever issues you're having. Looks like the ball is in your court. :) -- Lee Jones [李琼斯] Senior Technical Lead - Developer Services Linaro.org │ Open source software for Arm SoCs Follow Linaro: Facebook | Twitter | Blog
