mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Damien Le Moal <dlemoal@kernel.org>
To: Arnd Bergmann <arnd@arndb.de>, Niklas Cassel <cassel@kernel.org>,
	Arnd Bergmann <arnd@kernel.org>
Cc: "Manivannan Sadhasivam" <mani@kernel.org>,
	"Krzysztof Wilczyński" <kwilczynski@kernel.org>,
	"Bjorn Helgaas" <bhelgaas@google.com>,
	"Frank Li" <Frank.Li@nxp.com>,
	"Kishon Vijay Abraham I" <kishon@kernel.org>,
	linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] PCI: endpoint: pci-epf-test: select configfs
Date: Fri, 13 Feb 2026 08:39:34 +0900	[thread overview]
Message-ID: <554897dc-1cd6-461d-9248-cc491b984a9e@kernel.org> (raw)
In-Reply-To: <8db96e1b-2559-4966-87d9-171854c6ce19@app.fastmail.com>

On 2/11/26 18:37, Arnd Bergmann wrote:
> On Wed, Feb 11, 2026, at 10:05, Niklas Cassel wrote:
>> On Wed, Feb 11, 2026 at 08:07:40AM +0100, Arnd Bergmann wrote:
>>
>> However, I remember that you Arnd was one of the main reasons why Kishon
>> decided to use configfs to configure a PCI endpoint controller and to
>> bind a PCI endpoint function driver with a PCI endpoint controller.
>>
>> I don't know of any other way than configfs to bind a PCI endpoint function
>> driver with a PCI endpoint controller.
>>
>> To me, it seems a bit silly to be able to build PCI_ENDPOINT without
>> configfs. What should a user do with a library that they cannot bind to
>> a PCI endpoint controller?
>>
>> Why shouldn't we just do something like:
>>
>> diff --git a/drivers/pci/endpoint/Kconfig b/drivers/pci/endpoint/Kconfig
>> index 8dad291be8b8..d6f898094509 100644
>> --- a/drivers/pci/endpoint/Kconfig
>> +++ b/drivers/pci/endpoint/Kconfig
>> @@ -8,6 +8,7 @@ menu "PCI Endpoint"
>>  config PCI_ENDPOINT
>>  	bool "PCI Endpoint Support"
>>  	depends on HAVE_PCI
>> +	select PCI_ENDPOINT_CONFIGFS
>>  	help
>>  	   Enable this configuration option to support configurable PCI
>>  	   endpoint. This should be enabled if the platform has a PCI
> 
> 
> I think at that point we would instead drop PCI_ENDPOINT_CONFIGFS
> as a Kconfig option, since it is never user selectable. Otherwise
> this is probably a sensible solution as well.

+1. That option is mandatory, so it is not an option at all :)
If PCI_ENDPOINT is set, we must have configfs.

> 
>      Arnd


-- 
Damien Le Moal
Western Digital Research

  reply	other threads:[~2026-02-12 23:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-11  7:07 Arnd Bergmann
2026-02-11  8:43 ` Damien Le Moal
2026-02-11  9:05 ` Niklas Cassel
2026-02-11  9:37   ` Arnd Bergmann
2026-02-12 23:39     ` Damien Le Moal [this message]
2026-02-13  9:35       ` Niklas Cassel
2026-02-18 18:00         ` Bjorn Helgaas
2026-02-19  9:02           ` Niklas Cassel
2026-02-19 13:04             ` Niklas Cassel
2026-02-19 16:13               ` Bjorn Helgaas
2026-02-19 19:14                 ` Niklas Cassel
2026-02-19 16:00             ` Bjorn Helgaas
2026-02-18 18:00 ` Bjorn Helgaas

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=554897dc-1cd6-461d-9248-cc491b984a9e@kernel.org \
    --to=dlemoal@kernel.org \
    --cc=Frank.Li@nxp.com \
    --cc=arnd@arndb.de \
    --cc=arnd@kernel.org \
    --cc=bhelgaas@google.com \
    --cc=cassel@kernel.org \
    --cc=kishon@kernel.org \
    --cc=kwilczynski@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=mani@kernel.org \
    /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

Powered by JetHome