[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3aa3c8ad-4e6a-9b9b-be58-bd9da5a0fb0a@gmail.com>
Date: Mon, 22 Jun 2020 11:09:10 -0500
From: Frank Rowand <frowand.list@...il.com>
To: Lee Jones <lee.jones@...aro.org>, andy.shevchenko@...il.com,
michael@...le.cc, robh+dt@...nel.org, broonie@...nel.org,
devicetree@...r.kernel.org, linus.walleij@...aro.org,
linux@...ck-us.net, andriy.shevchenko@...ux.intel.com,
robin.murphy@....com, gregkh@...uxfoundation.org
Cc: linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 1/3] mfd: core: Make a best effort attempt to match
devices with the correct of_nodes
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.
-Frank
Powered by blists - more mailing lists