linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Frank Rowand <frowand.list@gmail.com>
To: Lee Jones <lee.jones@linaro.org>,
	andy.shevchenko@gmail.com, michael@walle.cc, robh+dt@kernel.org,
	broonie@kernel.org, devicetree@vger.kernel.org,
	linus.walleij@linaro.org, linux@roeck-us.net,
	andriy.shevchenko@linux.intel.com, robin.murphy@arm.com,
	gregkh@linuxfoundation.org
Cc: linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/3] mfd: core: Make a best effort attempt to match devices with the correct of_nodes
Date: Mon, 22 Jun 2020 11:09:10 -0500	[thread overview]
Message-ID: <3aa3c8ad-4e6a-9b9b-be58-bd9da5a0fb0a@gmail.com> (raw)
In-Reply-To: <20200622080913.GO954398@dell>

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

  reply	other threads:[~2020-06-22 16:09 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-11 19:10 [PATCH v2 1/3] mfd: core: Make a best effort attempt to match devices with the correct of_nodes Lee Jones
2020-06-11 19:10 ` [PATCH v2 2/3] mfd: core: Fix formatting of MFD helpers Lee Jones
2020-06-12 12:27   ` Frank Rowand
2020-06-11 19:10 ` [PATCH v2 3/3] mfd: core: Add OF_MFD_CELL_REG() helper Lee Jones
2020-06-12 12:28   ` Frank Rowand
2020-06-12 12:26 ` [PATCH v2 1/3] mfd: core: Make a best effort attempt to match devices with the correct of_nodes Frank Rowand
2020-06-15  1:19 ` Frank Rowand
2020-06-15  9:26   ` Lee Jones
2020-06-18 17:34     ` Frank Rowand
2020-06-22  8:50       ` Lee Jones
2020-06-22 14:32         ` Frank Rowand
2020-06-22 14:35           ` Frank Rowand
2020-06-22 15:10           ` Lee Jones
2020-06-22 18:01             ` Frank Rowand
2020-06-22 18:04               ` Frank Rowand
2020-06-22 19:11               ` Lee Jones
2020-06-22 22:23                 ` Frank Rowand
2020-06-23  1:17                   ` Frank Rowand
2020-06-23  1:37                     ` Frank Rowand
2020-06-23  6:47                   ` Lee Jones
2020-06-23 17:55                     ` Frank Rowand
2020-06-23 19:59                       ` Lee Jones
2020-06-23 22:33                         ` Frank Rowand
2020-06-24  7:46                           ` Lee Jones
2020-06-24 15:51                             ` Frank Rowand
2020-06-24 16:14                               ` Lee Jones
2020-06-24 16:25                                 ` Frank Rowand
2020-06-22  8:09 ` Lee Jones
2020-06-22 16:09   ` Frank Rowand [this message]
2020-06-22 16:53     ` Lee Jones
2020-06-23 22:21 ` Frank Rowand
2020-06-24  6:45   ` Lee Jones
2020-06-23 23:03 ` Frank Rowand
2020-06-24  6:41   ` Lee Jones
2020-06-24  7:47     ` Michael Walle
2020-06-24  8:23       ` Lee Jones
2020-06-24  9:19         ` Michael Walle
2020-06-24 11:24           ` Lee Jones
2020-06-11 19:12 Lee Jones

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3aa3c8ad-4e6a-9b9b-be58-bd9da5a0fb0a@gmail.com \
    --to=frowand.list@gmail.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=broonie@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=lee.jones@linaro.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=michael@walle.cc \
    --cc=robh+dt@kernel.org \
    --cc=robin.murphy@arm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).