linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yinghai Lu <yinghai@kernel.org>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
	Yinghai Lu <yinghai@kernel.org>
Subject: [PATCH -v2 00/11] PCI: quirk related clean up
Date: Thu, 23 Feb 2012 23:46:48 -0800	[thread overview]
Message-ID: <1330069619-14446-1-git-send-email-yinghai@kernel.org> (raw)

After commit:
| commit 3209874a1da2c51c7325e601d9634189ee178ad6
| Author: Arjan van de Ven <arjan@infradead.org>
| Date:   Mon Jan 30 20:52:07 2012 -0800
|
|    PCI: Annotate PCI quirks in initcall_debug style

will have lots of print out for quirks when initcall_debug is specified.

It turns out most of them are not really called for the devices because
quirks itself will check class id and bail out early.

Try to put class into quirk declaration. So we could avoid dive into these
quirks.

could be found at:

        git://git.kernel.org/pub/scm/linux/kernel/git/yinghai/linux-yinghai.git for-pci5

4ace9ad: PCI: Use class for quirk for usb host controller fixup
cc60c7c: PCI: Use class for quirk for ti816x class fixup
85fa49c: PCI: Use class for quirk for intel e100 interrupt fixup
8e4b35b: PCI: Use class for quirk for netmos class fixup
7c4b5d6: PCI: Use class for quirk for legacy ATA NO_D3
176e7df: PCI: Use class for quirk for cardbus_legacy
c2c7107: PCI: Use class for quirk for host bridge mmio_always_on
6924d3b: PCI: Use class for quirk for pci_fixup_video
7133c84: PCI: Use class quirk for intel fix_transparent_bridge
bf9f6e6: PCI: Use class for quirk for via_no_dac
d2e6e88: PCI: Add class support in quirk handling


-v2: separate to small patches for different quirk according to Jesse.

Thanks

Yinghai

 arch/x86/kernel/pci-dma.c     |    5 ++-
 arch/x86/pci/fixup.c          |   12 +++----
 drivers/pci/quirks.c          |   61 +++++++++++++++++++++------------------
 drivers/usb/host/pci-quirks.c |    3 +-
 include/linux/pci.h           |   63 +++++++++++++++++++++++++++++++++-------
 5 files changed, 95 insertions(+), 49 deletions(-)


             reply	other threads:[~2012-02-24  7:47 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-24  7:46 Yinghai Lu [this message]
2012-02-24  7:46 ` [PATCH 01/11] PCI: Add class support in quirk handling Yinghai Lu
2012-02-24 22:35   ` Jesse Barnes
2012-02-24  7:46 ` [PATCH 02/11] PCI: Use class for quirk for via_no_dac Yinghai Lu
2012-02-24  7:46 ` [PATCH 03/11] PCI: Use class quirk for intel fix_transparent_bridge Yinghai Lu
2012-02-24  7:46 ` [PATCH 04/11] PCI: Use class for quirk for pci_fixup_video Yinghai Lu
2012-02-24  7:46 ` [PATCH 05/11] PCI: Use class for quirk for host bridge mmio_always_on Yinghai Lu
2012-02-24  7:46 ` [PATCH 06/11] PCI: Use class for quirk for cardbus_legacy Yinghai Lu
2012-02-24  7:46 ` [PATCH 07/11] PCI: Use class for quirk for legacy ATA NO_D3 Yinghai Lu
2012-02-24  7:46 ` [PATCH 08/11] PCI: Use class for quirk for netmos class fixup Yinghai Lu
2012-02-24  7:46 ` [PATCH 09/11] PCI: Use class for quirk for intel e100 interrupt fixup Yinghai Lu
2012-02-24  7:46 ` [PATCH 10/11] PCI: Use class for quirk for ti816x class fixup Yinghai Lu
2012-02-24  7:46 ` [PATCH 11/11] PCI: Use class for quirk for usb host controller fixup Yinghai Lu

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=1330069619-14446-1-git-send-email-yinghai@kernel.org \
    --to=yinghai@kernel.org \
    --cc=jbarnes@virtuousgeek.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.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;
as well as URLs for NNTP newsgroup(s).