From: <daire.mcnamara@microchip.com>
To: <conor.dooley@microchip.com>
Cc: "Daire McNamara" <daire.mcnamara@microchip.com>,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Krzysztof Wilczyński" <kw@linux.com>,
"Rob Herring" <robh@kernel.org>,
"Bjorn Helgaas" <bhelgaas@google.com>,
linux-riscv@lists.infradead.org, linux-pci@vger.kernel.org
Subject: [PATCH v3 0/7] PCI: microchip: Fixes and clean-ups
Date: Fri, 28 Jul 2023 13:11:42 +0100 [thread overview]
Message-ID: <20230728121149.1606382-1-daire.mcnamara@microchip.com> (raw)
From: Daire McNamara <daire.mcnamara@microchip.com>
This patch series contains fixes and clean-ups for the Microchip PolarFire SoC PCIe driver
These patches are extracted from the link below to separate them from the outbound and inbound
range handling which is taking considerable time.
Link: https://lore.kernel.org/linux-riscv/20230111125323.1911373-1-daire.mcnamara@microchip.com/
These patches are regenerated on v6.5-rc4.
Main changes from v2:
- Reworked "Gather MSI information..." as suggested by Bjorn
- merged 'Gather MSI Information..." and "Rename and refactor" as suggested by Bjorn
- Re-generated on v6.5-rc4
Main Changes from v1:
- Dropped "Remove cast warning for devm_add_action_or_reset()". This
has been overtaken by a patch series from Krzysztof Wilczynski.
- Improved the comment for "Enable building driver as a module" to
clarify what enables building the driver as a module.
- Split "Gather MSI information from hardware config registers",
for clarity, into:
- "Gather MSI information from hardware config registers" purely
changing the of source of MSI-related information (Num MSIs and
MSI address) from #defines (which can be incorrect) to FPGA
configuration registers (which is the ultimate source of truth),
and a
- "Rename and refactor ..." patch as a function's code is now clearly
unrelated to its current name.
cc: Conor Dooley <conor.dooley@microchip.com>
cc: Lorenzo Pieralisi <lpieralisi@kernel.org>
cc: "Krzysztof Wilczyński" <kw@linux.com>
cc: Rob Herring <robh@kernel.org>
cc: Bjorn Helgaas <bhelgaas@google.com>
cc: linux-riscv@lists.infradead.org
cc: linux-pci@vger.kernel.org
Daire McNamara (8):
PCI: microchip: Correct the DED and SEC interrupt bit offsets
PCI: microchip: Enable building driver as a module
PCI: microchip: Align register, offset, and mask names with hw docs
PCI: microchip: Enable event handlers to access bridge and ctrl ptrs
PCI: microchip: Clean up initialisation of interrupts
PCI: microchip: Gather MSI information from hardware config registers
PCI: microchip: Re-partition code between probe() and init()
drivers/pci/controller/Kconfig | 2 +-
drivers/pci/controller/pcie-microchip-host.c | 393 +++++++++++--------
2 files changed, 233 insertions(+), 162 deletions(-)
base-commit: 6eaae198076080886b9e7d57f4ae06fa782f90ef
--
2.25.1
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next reply other threads:[~2023-07-28 12:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-28 12:11 daire.mcnamara [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-07-28 13:13 [PATCH v3 0/7] PCI: microchip: Fixes and clean-ups daire.mcnamara
2023-08-08 11:02 ` Lorenzo Pieralisi
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=20230728121149.1606382-1-daire.mcnamara@microchip.com \
--to=daire.mcnamara@microchip.com \
--cc=bhelgaas@google.com \
--cc=conor.dooley@microchip.com \
--cc=kw@linux.com \
--cc=linux-pci@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=lpieralisi@kernel.org \
--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