From: Frank Rowand <frowand.list@gmail.com>
To: Saravana Kannan <saravanak@google.com>
Cc: Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>, LKML <linux-kernel@vger.kernel.org>,
David Collins <collinsd@codeaurora.org>,
Android Kernel Team <kernel-team@android.com>
Subject: Re: [PATCH v7 1/7] driver core: Add support for linking devices during device addition
Date: Wed, 21 Aug 2019 08:36:37 -0700 [thread overview]
Message-ID: <915b49b5-5511-afa2-d3d6-e4ede94d40be@gmail.com> (raw)
In-Reply-To: <CAGETcx-J7+d3pcArMZvO5zQbUhAhRW+1=FUf7C1fV9-QhkckBw@mail.gmail.com>
On 8/20/19 3:10 PM, Saravana Kannan wrote:
> On Mon, Aug 19, 2019 at 9:25 PM Frank Rowand <frowand.list@gmail.com> wrote:
>>
>> On 8/19/19 5:00 PM, Saravana Kannan wrote:
>>> On Sun, Aug 18, 2019 at 8:38 PM Frank Rowand <frowand.list@gmail.com> wrote:
>>>>
< snip >
>>>
>>> 3. The supplier info doesn't always need to come from a firmware. So I
>>> don't want to limit it to that?
>>
>> If you can find another source of topology info, then I would expect
>> that another set of fwnode_operations functions would be created
>> for the info source.
>
> The other source could just be C files in the kernel. Using fwnodes
> for that would be hacky. But let's sort (1) and (2) out first.
>
< snip >
Just a piece of trivia. I got curious enough about this to search.
There is a third type of fwnode, software nodes.
See commit 59abd83672f70cac4b6bf9b237506c5bc6837606 for a description.
-Frank
next prev parent reply other threads:[~2019-08-21 15:36 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-24 0:10 [PATCH v7 0/7] Solve postboot supplier cleanup and optimize probe ordering Saravana Kannan
2019-07-24 0:10 ` [PATCH v7 1/7] driver core: Add support for linking devices during device addition Saravana Kannan
2019-08-08 2:04 ` Frank Rowand
2019-08-16 1:50 ` Saravana Kannan
2019-08-19 3:38 ` Frank Rowand
2019-08-20 0:00 ` Saravana Kannan
2019-08-20 4:25 ` Frank Rowand
2019-08-20 22:10 ` Saravana Kannan
2019-08-21 1:06 ` Frank Rowand
2019-08-21 1:56 ` Greg Kroah-Hartman
2019-08-21 2:04 ` Saravana Kannan
[not found] ` <CAGETcx8eVfJ0mn08E6pTDytjVE+RFcj_gOt_enide4E6G1NAWw@mail.gmail.com>
2019-08-21 4:24 ` Frank Rowand
2019-08-21 2:22 ` Saravana Kannan
2019-08-21 15:36 ` Frank Rowand [this message]
2019-07-24 0:10 ` [PATCH v7 2/7] driver core: Add edit_links() callback for drivers Saravana Kannan
2019-08-08 2:05 ` Frank Rowand
2019-08-16 1:50 ` Saravana Kannan
2019-07-24 0:10 ` [PATCH v7 3/7] of/platform: Add functional dependency link from DT bindings Saravana Kannan
2019-08-08 2:06 ` Frank Rowand
2019-08-16 1:50 ` Saravana Kannan
2019-08-19 17:16 ` Frank Rowand
2019-08-19 20:49 ` Saravana Kannan
2019-08-19 21:30 ` Frank Rowand
2019-08-20 0:09 ` Saravana Kannan
2019-08-20 4:26 ` Frank Rowand
2019-08-20 22:09 ` Saravana Kannan
2019-08-21 16:39 ` Frank Rowand
2019-07-24 0:10 ` [PATCH v7 4/7] driver core: Add sync_state driver/bus callback Saravana Kannan
2019-07-24 0:10 ` [PATCH v7 5/7] of/platform: Pause/resume sync state during init and of_platform_populate() Saravana Kannan
2019-07-24 0:10 ` [PATCH v7 6/7] of/platform: Create device links for all child-supplier depencencies Saravana Kannan
2019-07-24 0:11 ` [PATCH v7 7/7] of/platform: Don't create device links for default busses Saravana Kannan
2019-07-25 13:42 ` [PATCH v7 0/7] Solve postboot supplier cleanup and optimize probe ordering Greg Kroah-Hartman
2019-07-25 21:04 ` Frank Rowand
2019-07-26 14:32 ` Greg Kroah-Hartman
2019-07-31 2:22 ` Frank Rowand
2019-08-08 2:02 ` Frank Rowand
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=915b49b5-5511-afa2-d3d6-e4ede94d40be@gmail.com \
--to=frowand.list@gmail.com \
--cc=collinsd@codeaurora.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=rafael@kernel.org \
--cc=robh+dt@kernel.org \
--cc=saravanak@google.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).