From: Mahesh Vaidya <mahesh.vaidya@altera.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: joyce.ooi@intel.com, lpieralisi@kernel.org,
kwilczynski@kernel.org, mani@kernel.org, robh@kernel.org,
bhelgaas@google.com, krzk+dt@kernel.org, conor+dt@kernel.org,
linux-pci@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, subhransu.sekhar.prusty@altera.com,
dinguyen@kernel.org
Subject: Re: [PATCH 1/3] dt-bindings: PCI: altera: add binding for Agilex 5
Date: Mon, 27 Apr 2026 18:13:22 +0530 [thread overview]
Message-ID: <87cb3c2d-ff99-444b-b95a-973f91606ff6@altera.com> (raw)
In-Reply-To: <20260425-witty-heron-of-perfection-cedddd@quoll>
On 25-04-2026 15:52, Krzysztof Kozlowski wrote:
> On Fri, Apr 24, 2026 at 02:49:11AM -0700, Mahesh Vaidya wrote:
>> enum:
>> - altr,pcie-root-port-1.0
>> @@ -25,20 +26,15 @@ properties:
>> - altr,pcie-root-port-3.0-f-tile
>> - altr,pcie-root-port-3.0-p-tile
>> - altr,pcie-root-port-3.0-r-tile
>> + - altr,pcie-root-port-4.0
>>
>> reg:
>> - items:
>> - - description: TX slave port region
>> - - description: Control register access region
>> - - description: Hard IP region
>
> I don't understand why you are removing this.
Yes, you are right. I will only keep the agilex5 enabling changes, rest
all are not required. Later I will post a patch separately adding more
documentation where ever required.
next prev parent reply other threads:[~2026-04-27 12:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-24 9:49 [PATCH 0/3] PCI: altera: Add Agilex 5 PCIe Root Port support Mahesh Vaidya
2026-04-24 9:49 ` [PATCH 1/3] dt-bindings: PCI: altera: add binding for Agilex 5 Mahesh Vaidya
2026-04-25 10:22 ` Krzysztof Kozlowski
2026-04-27 12:43 ` Mahesh Vaidya [this message]
2026-04-24 9:49 ` [PATCH 2/3] PCI: altera: fix resource leaks on probe failure Mahesh Vaidya
2026-04-24 12:42 ` Dinh Nguyen
2026-04-27 12:36 ` Mahesh Vaidya
2026-04-24 9:49 ` [PATCH 3/3] PCI: altera: add Agilex 5 support Mahesh Vaidya
2026-04-24 15:48 ` Bjorn Helgaas
2026-04-27 12:49 ` Mahesh Vaidya
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=87cb3c2d-ff99-444b-b95a-973f91606ff6@altera.com \
--to=mahesh.vaidya@altera.com \
--cc=bhelgaas@google.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dinguyen@kernel.org \
--cc=joyce.ooi@intel.com \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=kwilczynski@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=mani@kernel.org \
--cc=robh@kernel.org \
--cc=subhransu.sekhar.prusty@altera.com \
/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