From: Frank Rowand <frowand.list@gmail.com>
To: Rob Herring <robh@kernel.org>, Lizhi Hou <lizhi.hou@amd.com>
Cc: linux-pci@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, helgaas@kernel.org,
clement.leger@bootlin.com, max.zhen@amd.com,
sonal.santan@amd.com, larry.liu@amd.com, brian.xu@amd.com,
stefano.stabellini@xilinx.com, trix@redhat.com
Subject: Re: [PATCH RFC 2/2] pci: create device tree node for selected devices
Date: Fri, 16 Sep 2022 18:20:52 -0500 [thread overview]
Message-ID: <1a4381ea-53a6-1ed0-100f-e622457ccc87@gmail.com> (raw)
In-Reply-To: <63c31198-ac4d-f3c7-9259-ea7dc6373b23@gmail.com>
On 9/13/22 02:03, Frank Rowand wrote:
> On 9/12/22 01:33, Frank Rowand wrote:
>> On 9/2/22 13:54, Rob Herring wrote:
>>> On Mon, Aug 29, 2022 at 02:43:37PM -0700, Lizhi Hou wrote:
>>>> The PCI endpoint device such as Xilinx Alveo PCI card maps the register
>>>> spaces from multiple hardware peripherals to its PCI BAR. Normally,
>>>> the PCI core discovers devices and BARs using the PCI enumeration process.
>>>> And the process does not provide a way to discover the hardware peripherals
>>>> been mapped to PCI BARs.
>>
>> < snip >
>>
>>>
>>> The above bits aren't really particular to PCI, so they probably
>>> belong in the DT core code. Frank will probably have thoughts on what
>>> this should look like.
>>
>> < snip >
>>
>> I will try to look through this patch series later today (Monday 9/12
>> USA time - I will not be in Dublin for the conferences this week.)
>>
>> -Frank
>
> I have collected nearly 500 emails on the history behind this patch and
> also another set of patch series that has been trying to achieve some
> somewhat similar functionality. Expect me to take a while to wade through
> all of this.
I'm still working at understanding the full picture of patch 2/2.
-Frank
>
> -Frank
next prev parent reply other threads:[~2022-09-16 23:20 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-29 21:43 [PATCH RFC 0/2] Generate device tree node for pci devices Lizhi Hou
2022-08-29 21:43 ` [PATCH RFC 1/2] of: dynamic: add of_node_alloc() Lizhi Hou
2022-09-16 23:15 ` Frank Rowand
2022-08-29 21:43 ` [PATCH RFC 2/2] pci: create device tree node for selected devices Lizhi Hou
2022-09-02 18:54 ` Rob Herring
2022-09-12 6:33 ` Frank Rowand
2022-09-13 7:03 ` Frank Rowand
2022-09-16 23:20 ` Frank Rowand [this message]
2022-09-13 5:49 ` Lizhi Hou
2022-09-02 20:43 ` [PATCH RFC 0/2] Generate device tree node for pci devices Bjorn Helgaas
2022-09-09 23:06 ` Lizhi Hou
2022-09-13 7:00 ` Frank Rowand
2022-09-13 17:10 ` Lizhi Hou
2022-09-13 17:41 ` Frank Rowand
2022-09-13 21:02 ` Lizhi Hou
2022-09-17 2:23 ` Frank Rowand
2022-09-17 18:36 ` Tom Rix
2022-09-20 3:12 ` Frank Rowand
2022-09-26 3:03 ` Sonal Santan
2022-10-14 21:25 ` Frank Rowand
2022-10-10 8:42 ` [PATCH RFC 0/2] Generate device tree node for pci devicesgain, Clément Léger
2022-10-13 6:05 ` Frank Rowand
2022-10-13 8:02 ` Clément Léger
2022-10-13 17:28 ` Frank Rowand
2022-10-14 17:33 ` Rob Herring
2022-10-14 18:52 ` Frank Rowand
2022-10-17 7:18 ` Clément Léger
2022-10-26 21:20 ` Sonal Santan
2022-09-14 13:35 ` [PATCH RFC 0/2] Generate device tree node for pci devices Jeremi Piotrowski
2022-09-14 18:08 ` Rob Herring
2022-09-16 23:15 ` Frank Rowand
2022-09-26 22:44 ` Rob Herring
2022-09-30 19:29 ` Sonal Santan
2022-10-06 15:10 ` Rob Herring
2022-10-07 22:45 ` Sonal Santan
2022-10-10 8:58 ` Clément Léger
2022-10-13 6:08 ` 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=1a4381ea-53a6-1ed0-100f-e622457ccc87@gmail.com \
--to=frowand.list@gmail.com \
--cc=brian.xu@amd.com \
--cc=clement.leger@bootlin.com \
--cc=devicetree@vger.kernel.org \
--cc=helgaas@kernel.org \
--cc=larry.liu@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lizhi.hou@amd.com \
--cc=max.zhen@amd.com \
--cc=robh@kernel.org \
--cc=sonal.santan@amd.com \
--cc=stefano.stabellini@xilinx.com \
--cc=trix@redhat.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).