From: Michal Simek <michal.simek@xilinx.com>
To: Bjorn Helgaas <helgaas@kernel.org>,
Bharat Kumar Gogada <bharat.kumar.gogada@xilinx.com>
Cc: <linux-pci@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<devicetree@vger.kernel.org>, <lorenzo.pieralisi@arm.com>,
<bhelgaas@google.com>, <robh@kernel.org>
Subject: Re: [PATCH v4 2/2] PCI: xilinx-cpm: Add support for Versal CPM5 Root Port
Date: Thu, 9 Jun 2022 09:59:08 +0200 [thread overview]
Message-ID: <a403b92d-00f1-885f-7d1b-0fce82b50993@xilinx.com> (raw)
In-Reply-To: <20220608191437.GA411770@bhelgaas>
On 6/8/22 21:14, Bjorn Helgaas wrote:
> On Wed, Jun 08, 2022 at 10:10:46PM +0530, Bharat Kumar Gogada wrote:
>> Xilinx Versal Premium series has CPM5 block which supports Root Port
>> functioning at Gen5 speed.
>>
>> Xilinx Versal CPM5 has few changes with existing CPM block.
>> - CPM5 has dedicated register space for control and status registers.
>> - CPM5 legacy interrupt handling needs additional register bit
>> to enable and handle legacy interrupts.
>>
>> Signed-off-by: Bharat Kumar Gogada <bharat.kumar.gogada@xilinx.com>
>> ---
>> drivers/pci/controller/pcie-xilinx-cpm.c | 33 +++++++++++++++++++++++-
>> 1 file changed, 32 insertions(+), 1 deletion(-)
>
> Per MAINTAINERS, xilinx-cpm lacks a maintainer. Can we get one?
Bharat should become maintainer for this driver.
My fragment should cover xilinx things in general in case Bharat is not available.
Thanks,
Michal
next prev parent reply other threads:[~2022-06-09 7:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-08 16:40 [PATCH v4 0/2] Add support for Xilinx " Bharat Kumar Gogada
2022-06-08 16:40 ` [PATCH v4 1/2] dt-bindings: PCI: xilinx-cpm: Add " Bharat Kumar Gogada
2022-06-09 21:10 ` Rob Herring
2022-06-10 8:50 ` Bharat Kumar Gogada
2022-06-08 16:40 ` [PATCH v4 2/2] PCI: xilinx-cpm: Add support for " Bharat Kumar Gogada
2022-06-08 19:14 ` Bjorn Helgaas
2022-06-09 7:59 ` Michal Simek [this message]
2022-06-09 17:32 ` Bjorn Helgaas
2022-06-10 8:49 ` Bharat Kumar Gogada
2022-06-10 8:47 ` Bharat Kumar Gogada
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=a403b92d-00f1-885f-7d1b-0fce82b50993@xilinx.com \
--to=michal.simek@xilinx.com \
--cc=bharat.kumar.gogada@xilinx.com \
--cc=bhelgaas@google.com \
--cc=devicetree@vger.kernel.org \
--cc=helgaas@kernel.org \
--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
all inboxes | Powered by JetHome®