All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Pali Rohár" <pali@kernel.org>
To: "Martin Mares" <mj@ucw.cz>, "Bjorn Helgaas" <helgaas@kernel.org>,
	"Krzysztof Wilczyński" <kw@linux.com>,
	"Matthew Wilcox" <willy@infradead.org>,
	linux-pci@vger.kernel.org
Subject: [PATCH pciutils 1/4] libpci: Define new string property PCI_FILL_DRIVER
Date: Fri, 21 Jan 2022 15:03:48 +0100	[thread overview]
Message-ID: <20220121140351.27382-2-pali@kernel.org> (raw)
In-Reply-To: <20220121140351.27382-1-pali@kernel.org>

This change extends libpci library and allows providers to fill
PCI_FILL_DRIVER via native system APIs. As it is string property there is
no need to increase ABI version.

Intended usage in application is just:

  const char *driver = pci_get_string_property(d->dev, PCI_FILL_DRIVER);
---
 lib/pci.h | 1 +
 1 file changed, 1 insertion(+)

diff --git a/lib/pci.h b/lib/pci.h
index 8c3c11b9ebeb..c13387e2b4b1 100644
--- a/lib/pci.h
+++ b/lib/pci.h
@@ -216,6 +216,7 @@ char *pci_get_string_property(struct pci_dev *d, u32 prop) PCI_ABI;
 #define PCI_FILL_PROGIF		0x00020000
 #define PCI_FILL_REVID		0x00040000
 #define PCI_FILL_SUBSYS		0x00080000
+#define PCI_FILL_DRIVER		0x00100000
 
 void pci_setup_cache(struct pci_dev *, u8 *cache, int len) PCI_ABI;
 
-- 
2.20.1


  reply	other threads:[~2022-01-21 14:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-21 14:03 [PATCH pciutils 0/4] Support for PCI_FILL_DRIVER Pali Rohár
2022-01-21 14:03 ` Pali Rohár [this message]
2022-01-21 14:03 ` [PATCH pciutils 2/4] libpci: proc: Implement support " Pali Rohár
2022-01-21 14:03 ` [PATCH pciutils 3/4] libpci: sysfs: " Pali Rohár
2022-01-21 14:03 ` [PATCH pciutils 4/4] lspci: Replace find_driver() via libpci PCI_FILL_DRIVER Pali Rohár
2022-01-21 14:31 ` [PATCH pciutils 0/4] Support for PCI_FILL_DRIVER Martin Mareš
2022-01-21 14:40   ` Pali Rohár
2022-01-21 14:46     ` Martin Mareš

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=20220121140351.27382-2-pali@kernel.org \
    --to=pali@kernel.org \
    --cc=helgaas@kernel.org \
    --cc=kw@linux.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=mj@ucw.cz \
    --cc=willy@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.