From: Randy Dunlap <rdunlap@infradead.org>
To: trix@redhat.com, hao.wu@intel.com, mdf@kernel.org, corbet@lwn.net
Cc: linux-fpga@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFC 1/1] fpga: dfl: RFC PCI config
Date: Tue, 30 Jun 2020 10:26:19 -0700 [thread overview]
Message-ID: <67f7f2b8-3567-aadd-30d6-4cfbc0bc8ce5@infradead.org> (raw)
In-Reply-To: <20200630171656.20151-2-trix@redhat.com>
On 6/30/20 10:16 AM, trix@redhat.com wrote:
> From: Tom Rix <trix@redhat.com>
>
> Create some top level configs the map to dfl pci cards.
>
> Autoselect the parts of fpga that are needed to run these cards
> as well as the other subsystem configs to the card's subdevices.
>
> Signed-off-by: Tom Rix <trix@redhat.com>
> ---
> Documentation/fpga/dfl.rst | 33 +++++++++++++++++++++++++++++++++
> drivers/fpga/Kconfig | 28 ++++++++++++++++++++++++++++
> 2 files changed, 61 insertions(+)
>
> diff --git a/Documentation/fpga/dfl.rst b/Documentation/fpga/dfl.rst
> index d7648d7c7eee..3a872bc8e3d3 100644
> --- a/Documentation/fpga/dfl.rst
> +++ b/Documentation/fpga/dfl.rst
> @@ -500,6 +500,39 @@ Developer only needs to provide a sub feature driver with matched feature id.
> FME Partial Reconfiguration Sub Feature driver (see drivers/fpga/dfl-fme-pr.c)
> could be a reference.
>
> +Kernel configuration
> +====================
> +
> +While it is possible to manually setup a configuration to match your device,
> +there are some top level configurations that collect configuations for
configurations
> +some reference pci cards. Below descibes these configuration as well as
PCI describes
> +what other kernel configs are needed for proper configuration.
> +
> +FPGA_DFL_PAC10
> +Intel Arria 10 GX PCI card, PCI id 0X09C4
> +Depends on
> + SPI_ALTERA
> + MFD_INTEL_M10_BMC
> + MFD_INTEL_M10_BMC_SECURE
> + SENSORS_INTEL_M10_BMC_HWMON
> +
> +FPGA_DFL_D5005
> +Intel Stratix 10, D5005 PCI card, PCI id 0X0B2B
> +Depends on
> + SPI_ALTERA
> + MFD_INTEL_M10_BMC
> + MFD_INTEL_M10_BMC_SECURE
> + SENSORS_INTEL_M10_BMC_HWMON
> + INTEL_S10_PHY
> +
> +FPGA_DFL_N3000
> +Intel Network Accelerator, N3000 PCI card, PCI id 0X0B30
> +Depends on
> + SPI_ALTERA
> + MFD_INTEL_M10_BMC
> + MFD_INTEL_M10_BMC_SECURE
> + SENSORS_INTEL_M10_BMC_HWMON
> + INTEL_LL_10G_MAC
>
> Open discussion
> ===============
> diff --git a/drivers/fpga/Kconfig b/drivers/fpga/Kconfig
> index 9d53bd9094e2..b657de20bc98 100644
> --- a/drivers/fpga/Kconfig
> +++ b/drivers/fpga/Kconfig
> @@ -138,6 +138,34 @@ config OF_FPGA_REGION
> Support for loading FPGA images by applying a Device Tree
> overlay.
>
> +config FPGA_DFL_PAC10
> + tristate "Intel Arria 10 GX PCI card"
> + select SPI_ALTERA
above kconfig symbol:
depends on SPI_MASTER
> + select MFD_INTEL_M10_BMC
> + select MFD_INTEL_M10_BMC_SECURE
> + select SENSORS_INTEL_M10_BMC_HWMON
I haven't tested this, but in general it's not safe to select something like
SENSORS* or HWMON* unless you first check that CONFIG_HWMON is enabled.
Otherwise this would usually cause kconfig warning(s).
But don't add things like
select HWMON
select SPI
select SPI_MASTER
because we don't enable subsystems (like HWMON or SPI) just inside one
driver's kconfig entry.
The driver(s) should instead depend on HWMON, SPI, SPI_MASTER etc.
> + select FPGA_DFL
> + select FPGA_DFL_FME
> + select FPGA_DFL_FME_MGR
> + select FPGA_DFL_FME_BRIDGE
> + select FPGA_DFL_FME_REGION
> + select FPGA_DFL_AFU
> + select FPGA_DFL_SPI_ALTERA
> + select FPGA_DFL_PCI
> + select IFPGA_SEC_MGR
> +
> +config FPGA_DFL_D5005
> + tristate "Intel Stratix 10, D5005 PCI card"
> + select FPGA_DFL_PAC10
> + select INTEL_S10_PHY
> + select FPGA_DFl_HSSI
> +
> +config FPGA_DFL_N3000
> + tristate "Intel Network Accelerator, N3000 PCI card"
> + select FPGA_DFL_PAC10
> + select INTEL_LL_10G_MAC
> + select FPGA_DFL_N3000_NIOS
> +
> config FPGA_DFL
> tristate "FPGA Device Feature List (DFL) support"
> select FPGA_BRIDGE
>
--
~Randy
next prev parent reply other threads:[~2020-06-30 17:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-30 17:16 [RFC 0/1] fpga: dfl: RFC PCI config trix
2020-06-30 17:16 ` [RFC 1/1] " trix
2020-06-30 17:26 ` Randy Dunlap [this message]
2020-06-30 18:44 ` Tom Rix
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=67f7f2b8-3567-aadd-30d6-4cfbc0bc8ce5@infradead.org \
--to=rdunlap@infradead.org \
--cc=corbet@lwn.net \
--cc=hao.wu@intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fpga@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mdf@kernel.org \
--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).