From: Tom Rix <trix@redhat.com>
To: Xu Yilun <yilun.xu@intel.com>
Cc: hao.wu@intel.com, mdf@kernel.org, linux-fpga@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fpga: dfl: pci: generalize find_dfls_by_vsec()
Date: Mon, 15 Nov 2021 10:28:32 -0800 [thread overview]
Message-ID: <f645abbe-230c-b3b8-de6c-6b8a605535f4@redhat.com> (raw)
In-Reply-To: <20211115012516.GA288162@yilunxu-OptiPlex-7050>
On 11/14/21 5:25 PM, Xu Yilun wrote:
> On Sat, Nov 13, 2021 at 02:12:52PM -0800, trix@redhat.com wrote:
>> From: Tom Rix <trix@redhat.com>
>>
>> find_dfls_by_vsec() is a general dfl function.
>> Although dfl has multiple vendors, only Intel is supported.
>> Move vsec and vendor id to an array variable.
>> Other vendors can append the array to enable their support.
> As Hao mentioned, DVSEC could be a better solution if DFL should be
> present in components by a variety of vendors. This is not finally
> determined, but I think we should not add new features for VSEC now.
Can you expand what you mean by this ?
I am considering the n5010 usecase, the vendor is not intel and will go
through this dfl function and always fail.
This is broken.
Either the function should be generalized or moved to an intel specific
call.
Tom
>
> Thanks,
> Yilun
>
>> Signed-off-by: Tom Rix <trix@redhat.com>
>> ---
>> drivers/fpga/dfl-pci.c | 31 ++++++++++++++++++++++++-------
>> 1 file changed, 24 insertions(+), 7 deletions(-)
>>
>> diff --git a/drivers/fpga/dfl-pci.c b/drivers/fpga/dfl-pci.c
>> index 4d68719e608f..9dc0815c8274 100644
>> --- a/drivers/fpga/dfl-pci.c
>> +++ b/drivers/fpga/dfl-pci.c
>> @@ -136,19 +136,36 @@ static int *cci_pci_create_irq_table(struct pci_dev *pcidev, unsigned int nvec)
>> return table;
>> }
>>
>> -static int find_dfls_by_vsec(struct pci_dev *pcidev, struct dfl_fpga_enum_info *info)
>> +struct dfl_vsec {
>> + u16 vendor;
>> + u16 id;
>> +};
>> +
>> +static struct dfl_vsec vsecs[] = {
>> + { PCI_VENDOR_ID_INTEL, PCI_VSEC_ID_INTEL_DFLS },
>> +};
>> +
>> +static int find_dfls_by_vsec(struct pci_dev *pcidev,
>> + struct dfl_fpga_enum_info *info)
>> {
>> u32 bir, offset, vndr_hdr, dfl_cnt, dfl_res;
>> int dfl_res_off, i, bars, voff = 0;
>> resource_size_t start, len;
>>
>> - while ((voff = pci_find_next_ext_capability(pcidev, voff, PCI_EXT_CAP_ID_VNDR))) {
>> - vndr_hdr = 0;
>> - pci_read_config_dword(pcidev, voff + PCI_VNDR_HEADER, &vndr_hdr);
>> + for (i = 0; i < ARRAY_SIZE(vsecs); i++) {
>> + if (pcidev->vendor != vsecs[i].vendor)
>> + continue;
>> +
>> + while ((voff =
>> + pci_find_next_ext_capability(pcidev, voff,
>> + PCI_EXT_CAP_ID_VNDR))) {
>> + vndr_hdr = 0;
>> + pci_read_config_dword(pcidev, voff + PCI_VNDR_HEADER,
>> + &vndr_hdr);
>>
>> - if (PCI_VNDR_HEADER_ID(vndr_hdr) == PCI_VSEC_ID_INTEL_DFLS &&
>> - pcidev->vendor == PCI_VENDOR_ID_INTEL)
>> - break;
>> + if (PCI_VNDR_HEADER_ID(vndr_hdr) == vsecs[i].id)
>> + break;
>> + }
>> }
>>
>> if (!voff) {
>> --
>> 2.26.3
next prev parent reply other threads:[~2021-11-16 1:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-13 22:12 [PATCH] fpga: dfl: pci: generalize find_dfls_by_vsec() trix
2021-11-15 1:25 ` Xu Yilun
2021-11-15 18:28 ` Tom Rix [this message]
2021-11-16 2:01 ` Xu Yilun
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=f645abbe-230c-b3b8-de6c-6b8a605535f4@redhat.com \
--to=trix@redhat.com \
--cc=hao.wu@intel.com \
--cc=linux-fpga@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mdf@kernel.org \
--cc=yilun.xu@intel.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).