public inbox for linux-pci@vger.kernel.org
 help / color / mirror / Atom feed
From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: "Bjorn Helgaas" <bhelgaas@google.com>,
	linux-pci@vger.kernel.org,
	"Lorenzo Pieralisi" <lorenzo.pieralisi@arm.com>,
	"Rob Herring" <robh@kernel.org>,
	"Krzysztof Wilczyński" <kw@linux.com>,
	"Jonathan Cameron" <Jonathan.Cameron@huawei.com>
Cc: linux-kernel@vger.kernel.org,
	"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Subject: [PATCH 0/7] PCI: Use FIELD_GET/PREP() & other reg field cleanups
Date: Wed, 18 Oct 2023 14:32:47 +0300	[thread overview]
Message-ID: <20231018113254.17616-1-ilpo.jarvinen@linux.intel.com> (raw)

Hi,

Here's what I think should cover most of the remaining FIELD_GET/PREP()
conversions under drivers/pci/.

The patch from Bjorn is from
  https://lore.kernel.org/linux-pci/20231010204436.1000644-7-helgaas@kernel.org/
But has been adjusted to better blend in with the other DPC changes.
I've preserved Bjorn as the main From/SoB, and added myself before his
name instead (since I modified it but my main contribution was to
remove stuff he had made to it).

Bjorn Helgaas (1):
  PCI/DPC: Use FIELD_GET()

Ilpo Järvinen (6):
  PCI: cadence: Use FIELD_GET()
  PCI: dwc: Use FIELD_GET/PREP()
  PCI: hotplug: Use FIELD_GET/PREP()
  PCI/DPC: Use defined fields with DPC_CTL register
  PCI/DPC: Use defines with DPC reason fields
  PCI/MSI: Use FIELD_GET/PREP()

 .../pci/controller/cadence/pcie-cadence-ep.c  |  9 ++--
 .../pci/controller/dwc/pcie-designware-ep.c   |  7 ++--
 drivers/pci/controller/dwc/pcie-tegra194.c    |  5 +--
 drivers/pci/hotplug/pciehp_core.c             |  3 +-
 drivers/pci/hotplug/pciehp_hpc.c              |  5 ++-
 drivers/pci/hotplug/pnv_php.c                 |  3 +-
 drivers/pci/msi/msi.c                         | 10 +++--
 drivers/pci/pcie/dpc.c                        | 42 ++++++++++++-------
 drivers/pci/quirks.c                          |  2 +-
 include/uapi/linux/pci_regs.h                 |  9 ++++
 10 files changed, 61 insertions(+), 34 deletions(-)

-- 
2.30.2


             reply	other threads:[~2023-10-18 11:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-18 11:32 Ilpo Järvinen [this message]
2023-10-18 11:32 ` [PATCH 1/7] PCI: cadence: Use FIELD_GET() Ilpo Järvinen
2023-10-18 11:32 ` [PATCH 2/7] PCI: dwc: Use FIELD_GET/PREP() Ilpo Järvinen
2023-10-18 11:58   ` Serge Semin
2023-10-18 14:16     ` Ilpo Järvinen
2023-10-18 11:32 ` [PATCH 3/7] PCI: hotplug: " Ilpo Järvinen
2023-10-18 11:32 ` [PATCH 4/7] PCI/DPC: Use FIELD_GET() Ilpo Järvinen
2023-10-18 11:32 ` [PATCH 5/7] PCI/DPC: Use defined fields with DPC_CTL register Ilpo Järvinen
2023-10-18 11:32 ` [PATCH 6/7] PCI/DPC: Use defines with DPC reason fields Ilpo Järvinen
2023-10-18 11:32 ` [PATCH 7/7] PCI/MSI: Use FIELD_GET/PREP() Ilpo Järvinen
2023-10-18 16:23 ` [PATCH 0/7] PCI: Use FIELD_GET/PREP() & other reg field cleanups Bjorn Helgaas

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=20231018113254.17616-1-ilpo.jarvinen@linux.intel.com \
    --to=ilpo.jarvinen@linux.intel.com \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=bhelgaas@google.com \
    --cc=kw@linux.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lorenzo.pieralisi@arm.com \
    --cc=robh@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