From: Bjorn Helgaas <helgaas@kernel.org>
To: David Daney <ddaney@caviumnetworks.com>
Cc: Omer Khaliq <okhaliq@caviumnetworks.com>,
linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
linux-crypto@vger.kernel.org, linux-arm-kernel@vger.kernel.org,
bhelgaas@google.com, mpm@selenic.com,
herbert@gondor.apana.org.au, Ananth.Jasty@cavium.com,
david.daney@cavium.com
Subject: Re: [PATCH 1/2] PCI/IOV: Add function to allow Function Dependency Link override.
Date: Mon, 22 Aug 2016 11:14:54 -0500 [thread overview]
Message-ID: <20160822161454.GA23221@localhost> (raw)
In-Reply-To: <57BB10E5.1050506@caviumnetworks.com>
On Mon, Aug 22, 2016 at 07:49:09AM -0700, David Daney wrote:
> On 08/22/2016 07:36 AM, Bjorn Helgaas wrote:
> >Hi David & Omer,
> >
> >On Fri, Aug 19, 2016 at 03:32:12PM -0700, Omer Khaliq wrote:
> >>From: David Daney <david.daney@cavium.com>
> >>
> >>Some hardware presents an incorrect SR-IOV Function Dependency Link,
> >>add a function to allow this to be overridden in the PF driver for
> >>such devices.
> >>
> >>Signed-off-by: David Daney <david.daney@cavium.com>
> >>Signed-off-by: Omer Khaliq <okhaliq@caviumnetworks.com>
> >>---
> >> drivers/pci/iov.c | 14 ++++++++++++++
> >> include/linux/pci.h | 1 +
> >> 2 files changed, 15 insertions(+)
> >>
> >>diff --git a/drivers/pci/iov.c b/drivers/pci/iov.c
> >>index 2194b44..81f0672 100644
> >>--- a/drivers/pci/iov.c
> >>+++ b/drivers/pci/iov.c
> >>@@ -640,6 +640,20 @@ int pci_enable_sriov(struct pci_dev *dev, int nr_virtfn)
> >> EXPORT_SYMBOL_GPL(pci_enable_sriov);
> >>
> >> /**
> >>+ * pci_sriov_fdl_override - fix incorrect Function Dependency Link
> >>+ * @dev: the PCI device
> >>+ * @fdl: the corrected Function Dependency Link value
> >>+ *
> >>+ * For hardware presenting an incorrect Function Dependency Link in
> >>+ * the SR-IOV Extended Capability, allow a driver to override it.
> >>+ */
> >>+void pci_sriov_fdl_override(struct pci_dev *dev, u8 fdl)
> >>+{
> >>+ dev->sriov->link = fdl;
> >>+}
> >>+EXPORT_SYMBOL_GPL(pci_sriov_fdl_override);
> >
> >We usually use quirks to work around problems in config space. That's
> >a nice mechanism because we don't have to add new PCI core interfaces
> >and it makes it clear that we're working around a hardware problem.
> >
> >Can you use a quirk here? We allocate dev->sriov in the
> >pci_init_capabilities() path, so it looks like a pci_fixup_final quirk
> >should work.
> >
>
> The struct pci_sriov definition is private to drivers/pci, so in
> order to use a quirk to fix this, we would have to put it in
> drivers/pci/quirks.c. I was trying to keep this very device
> specific code in the driver, which requires an accessor to be able
> to manipulate the dev->sriov->link field.
>
> If you prefer a quirk in drivers/pci/quirks.c, we can certainly do
> that instead.
Oh, I didn't notice that pci_sriov was declared in drivers/pci/pci.h
instead of linux/pci.h. I do think I would prefer a quirk, and I
think it's fine to put it in drivers/pci/quirks.c.
Bjorn
next prev parent reply other threads:[~2016-08-22 16:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-19 22:32 [PATCH 0/2] hwrng/PCI/IOV: Add driver for Cavium Thunder RNG Omer Khaliq
2016-08-19 22:32 ` [PATCH 1/2] PCI/IOV: Add function to allow Function Dependency Link override Omer Khaliq
2016-08-22 14:36 ` Bjorn Helgaas
2016-08-22 14:49 ` David Daney
2016-08-22 16:14 ` Bjorn Helgaas [this message]
2016-08-19 22:32 ` [PATCH 2/2] hwrng: thunderx: Add Cavium HWRNG driver for ThunderX SoC Omer Khaliq
2016-08-20 5:41 ` Corentin LABBE
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=20160822161454.GA23221@localhost \
--to=helgaas@kernel.org \
--cc=Ananth.Jasty@cavium.com \
--cc=bhelgaas@google.com \
--cc=david.daney@cavium.com \
--cc=ddaney@caviumnetworks.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-arm-kernel@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mpm@selenic.com \
--cc=okhaliq@caviumnetworks.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).