From: Frank Rowand <frowand.list@gmail.com>
To: "Clément Léger" <clement.leger@bootlin.com>
Cc: Lizhi Hou <lizhi.hou@amd.com>,
linux-pci@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, robh@kernel.org,
helgaas@kernel.org, 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 0/2] Generate device tree node for pci devicesgain,
Date: Thu, 13 Oct 2022 12:28:42 -0500 [thread overview]
Message-ID: <c427fd85-3746-bf26-e4a3-9b2aa53f6572@gmail.com> (raw)
In-Reply-To: <20221013100245.14c509ec@fixe.home>
On 10/13/22 03:02, Clément Léger wrote:
> Le Thu, 13 Oct 2022 01:05:26 -0500,
> Frank Rowand <frowand.list@gmail.com> a écrit :
>
>>> This would also require two different descriptions of the same card
>>> (for ACPI and device-tree) and would require the final user to create a
>>> specific overlay for its device based on the PCI slots the card is
>>> plugged in.
>>
>> One of the many missing pieces of overlay support. There have been several
>> discussion of how to describe a "socket" in a device tree that a device
>> could be plugged into, where a single device tree subtree .dtb could be
>> relocated to one or more different socket locations. Thus in this
>> case a single overlay could be relocated to various PCI slots.
>>
>> I don't expect be getting involved in any future efforts around sockets
>> (see my following comment for why).
>>
>>>
>>> The solution we proposed (Lizhi and I) allows to overcome these
>>> problems and is way easier to use. Fixing the potential bugs that might
>>> exists in the overlay layer seems a way better idea that just pushing
>>
>> It is not potential bugs. The current run time overlay implementation is
>> proof of concept quality and completeness. It is not production ready.
>>
>> I got an opportunity for early retirement a couple of weeks ago. My first
>> inclination was to continue the same level of device tree maintainership,
>> but I am quickly realizing that there are other activities that I would
>> like to devote my time and energy to. I will continue to support Rob with
>> minor patch reviews and testing, and potentially finishing up some
>> improvements to unittest. On the other hand, bringing run time overlay
>> support to product quality would be a major investment of my time that I
>> am not willing to continue.
>
> Hi Frank,
>
> This explains your position on the overlay support and I can
> certainly understand it ! Regarding the fact that it would enter
No, my position on the technical aspects of overlay support is totally
unchanged.
The only thing that has changed is that my time will not be available to
assist in future overlay related work. The burden for this will fall
more on Rob than it has in the past.
> "production", the devices we are talking about are not really
> widespread yet? This would be a good opportunity to gather feedback
> early and improve the support gradually. We could probably even be able
> to support improvements in the overlay code if needed I guess.
That is avoiding my point about the current implementation being
proof of concept.
-Frank
>
> Thanks for your honest answer,
>
> Clément
>
>>
>> So I am leaving major overlay issues in the capable hands of Rob. I may
>> chime in from time to time when I can do so without requiring too much of
>> my time.
>>
>> -Frank
>>
>>> that away to the bootloader level. Moreover, this kind of devices is
>>> likely to be more common with the increasing popularity of FPGA and a
>>> proper solution must be found.
>>>
>
>
>
next prev parent reply other threads:[~2022-10-13 17:28 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
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 [this message]
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=c427fd85-3746-bf26-e4a3-9b2aa53f6572@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).