devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: <Conor.Dooley@microchip.com>
To: <ben.dooks@codethink.co.uk>
Cc: <paul.walmsley@sifive.com>, <krzysztof.kozlowski+dt@linaro.org>,
	<palmer@dabbelt.com>, <Shravan.Chippa@microchip.com>,
	<aou@eecs.berkeley.edu>, <Cyril.Jean@microchip.com>,
	<Lewis.Hanly@microchip.com>, <Praveen.Kumar@microchip.com>,
	<wg@aries-embedded.de>, <Hugh.Breslin@microchip.com>,
	<robh+dt@kernel.org>, <devicetree@vger.kernel.org>,
	<linux-riscv@lists.infradead.org>, <linux-kernel@vger.kernel.org>,
	<Daire.McNamara@microchip.com>
Subject: Re: [PATCH v2 6/9] riscv: dts: microchip: icicle: update pci address properties
Date: Tue, 30 Aug 2022 12:06:22 +0000	[thread overview]
Message-ID: <bbdb3953-eaaf-8efa-a55a-9ca083320af7@microchip.com> (raw)
In-Reply-To: <879a6823-6651-93cf-8500-661bedb050af@codethink.co.uk>

On 30/08/2022 11:44, Ben Dooks wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
> 
> On 30/08/2022 11:18, Conor Dooley wrote:
>> For the v2022.09 reference design the PCI root port's data region has
>> been moved to FIC1 from FIC0. This is a shorter path, allowing for
>> higher clock rates and improved through-put. As a result, the address at
>> which the PCIe's data region appears to the core complex has changed.
>> The config region's address is unchanged.
> 
> Did this also fix the 32bit address apperture issue which plagued
> getting pcie graphics cards sorted.

Eh, not this specific part of what is changing in v2022.09 - this will
just allow us to close timing using higher clock rates. But another
change that is landing in v2022.09 will (see patch 4/9). Performance is
not going to be great, but 32 bit devices will work again... We've got
some more stuff in the works that should help on the performance front,
so hopefully that makes life easier for pcie graphics cards.
soonTM on that one though ;)

Thanks,
Conor.



  reply	other threads:[~2022-08-30 12:07 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-30 10:17 [PATCH v2 0/9] New PolarFire SoC devkit devicetrees & 22.09 reference design updates Conor Dooley
2022-08-30 10:17 ` [PATCH v2 1/9] dt-bindings: riscv: microchip: document icicle reference design Conor Dooley
2022-08-30 10:17 ` [PATCH v2 2/9] dt-bindings: riscv: microchip: document the aries m100pfsevp Conor Dooley
2022-08-30 14:37   ` Krzysztof Kozlowski
2022-08-30 15:25     ` Conor.Dooley
2022-08-30 16:55       ` Krzysztof Kozlowski
2022-08-30 16:59         ` Conor.Dooley
2022-08-30 17:30           ` Krzysztof Kozlowski
2022-08-30 17:35             ` Conor.Dooley
2022-08-30 17:47               ` Krzysztof Kozlowski
2022-08-30 17:55                 ` Conor.Dooley
2022-08-30 10:17 ` [PATCH v2 3/9] dt-bindings: riscv: microchip: document the sev kit Conor Dooley
2022-08-30 10:17 ` [PATCH v2 4/9] riscv: dts: microchip: add pci dma ranges for the icicle kit Conor Dooley
2022-08-30 10:18 ` [PATCH v2 5/9] riscv: dts: microchip: move the mpfs' pci node to -fabric.dtsi Conor Dooley
2022-08-30 10:18 ` [PATCH v2 6/9] riscv: dts: microchip: icicle: update pci address properties Conor Dooley
2022-08-30 10:44   ` Ben Dooks
2022-08-30 12:06     ` Conor.Dooley [this message]
2022-08-30 10:18 ` [PATCH v2 7/9] riscv: dts: microchip: icicle: re-jig fabric peripheral addresses Conor Dooley
2022-08-30 10:18 ` [PATCH v2 8/9] riscv: dts: microchip: add sevkit device tree Conor Dooley
2022-08-30 10:18 ` [PATCH v2 9/9] riscv: dts: microchip: add a devicetree for aries' m100pfsevp Conor Dooley

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=bbdb3953-eaaf-8efa-a55a-9ca083320af7@microchip.com \
    --to=conor.dooley@microchip.com \
    --cc=Cyril.Jean@microchip.com \
    --cc=Daire.McNamara@microchip.com \
    --cc=Hugh.Breslin@microchip.com \
    --cc=Lewis.Hanly@microchip.com \
    --cc=Praveen.Kumar@microchip.com \
    --cc=Shravan.Chippa@microchip.com \
    --cc=aou@eecs.berkeley.edu \
    --cc=ben.dooks@codethink.co.uk \
    --cc=devicetree@vger.kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=robh+dt@kernel.org \
    --cc=wg@aries-embedded.de \
    /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).