From: Conor Dooley <conor@kernel.org>
To: Conor Dooley <conor.dooley@microchip.com>
Cc: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Daire McNamara <daire.mcnamara@microchip.com>,
Shravan Chippa <shravan.chippa@microchip.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Cyril Jean <Cyril.Jean@microchip.com>,
Lewis Hanly <lewis.hanly@microchip.com>,
Vattipalli Praveen <praveen.kumar@microchip.com>,
Wolfgang Grandegger <wg@aries-embedded.de>,
Hugh Breslin <hugh.breslin@microchip.com>,
devicetree@vger.kernel.org, linux-riscv@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 00/10] New PolarFire SoC devkit devicetrees & 22.09 reference design updates
Date: Mon, 19 Sep 2022 19:22:26 +0100 [thread overview]
Message-ID: <YyizYqHFG3vKrKFU@spud> (raw)
In-Reply-To: <20220916112645.567794-1-conor.dooley@microchip.com>
On Fri, Sep 16, 2022 at 12:26:36PM +0100, Conor Dooley wrote:
> Hey all,
>
> Some 6.1 targeted changes here.
> Firstly, two new dev kits (one first-party & one from Aries Embedded).
> They've been sitting in our vendor tree, so are being sent where they
> belong.
>
> Secondly, another release of our reference design for the Icicle kit
> is due in September. Usually these do not really change much for the
> devicetree, but this time around a pair of changes impact the memory
> map.
>
> The first of these is adding dma-ranges to the pcie controller. The
> controller had some issues to begin with & with the current reference
> design (v2022.05) would not work with mainline Linux nor has it since
> reference design v2021.08. A combination of the property, a change
> to the FPGA design & a small fix to the driver will get it working
> with mainline again. The other non-backwards compatible change to the
> reference design is moves of the peripherals instantiated in the
> fabric. Currently they are fairly spread out & a common complaint has
> been that this leaves little room in the fic3 section of the memory map
> for custom peripherals without removing the existing ones.
>
> This series depends on [0] so as not to add dtbs_check warnings. The
> fabric clock support is added by [1].
I've pushed this series to dt-for-next:
https://git.kernel.org/pub/scm/linux/kernel/git/conor/linux.git/log/?h=dt-for-next
There's a minor conflict with dt-fixes as that branch deletes a property
from the pcie dt node which is moved in this series. I deleted the
property as I moved it in this series so the fix will be to take the
version in dt-for-next instead.
>
> Thanks,
> Conor.
>
> Changes since v4:
> - fix the incompatible interrupts on m100pfsevp
>
> Changes since v3:
> - add an extra patch reducing the fic3 clock rate
>
> Changes since v2:
> - drop the sd & emmc versions of the aries devicetree
> - remove a extra newline
>
> Changes since v1:
> - made the polarberry part of an enum in patch 1
>
> 0 - https://lore.kernel.org/linux-gpio/20220825143522.3102546-1-conor.dooley@microchip.com/
> 1 - https://lore.kernel.org/linux-clk/20220824093342.187844-1-conor.dooley@microchip.com/
>
> Conor Dooley (8):
> dt-bindings: riscv: microchip: document icicle reference design
> dt-bindings: riscv: microchip: document the aries m100pfsevp
> riscv: dts: microchip: add pci dma ranges for the icicle kit
> riscv: dts: microchip: move the mpfs' pci node to -fabric.dtsi
> riscv: dts: microchip: icicle: update pci address properties
> riscv: dts: microchip: icicle: re-jig fabric peripheral addresses
> riscv: dts: microchip: reduce the fic3 clock rate
> riscv: dts: microchip: add a devicetree for aries' m100pfsevp
>
> Shravan Chippa (1):
> dt-bindings: riscv: microchip: document the sev kit
>
> Vattipalli Praveen (1):
> riscv: dts: microchip: add sevkit device tree
>
> .../devicetree/bindings/riscv/microchip.yaml | 20 +-
> arch/riscv/boot/dts/microchip/Makefile | 2 +
> .../dts/microchip/mpfs-icicle-kit-fabric.dtsi | 44 ++++-
> .../boot/dts/microchip/mpfs-icicle-kit.dts | 3 +-
> .../dts/microchip/mpfs-m100pfs-fabric.dtsi | 45 +++++
> .../boot/dts/microchip/mpfs-m100pfsevp.dts | 179 ++++++++++++++++++
> .../dts/microchip/mpfs-polarberry-fabric.dtsi | 29 +++
> .../dts/microchip/mpfs-sev-kit-fabric.dtsi | 45 +++++
> .../riscv/boot/dts/microchip/mpfs-sev-kit.dts | 145 ++++++++++++++
> arch/riscv/boot/dts/microchip/mpfs.dtsi | 29 ---
> 10 files changed, 499 insertions(+), 42 deletions(-)
> create mode 100644 arch/riscv/boot/dts/microchip/mpfs-m100pfs-fabric.dtsi
> create mode 100644 arch/riscv/boot/dts/microchip/mpfs-m100pfsevp.dts
> create mode 100644 arch/riscv/boot/dts/microchip/mpfs-sev-kit-fabric.dtsi
> create mode 100644 arch/riscv/boot/dts/microchip/mpfs-sev-kit.dts
>
> --
> 2.36.1
>
prev parent reply other threads:[~2022-09-19 18:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-16 11:26 [PATCH v5 00/10] New PolarFire SoC devkit devicetrees & 22.09 reference design updates Conor Dooley
2022-09-16 11:26 ` [PATCH v5 01/10] dt-bindings: riscv: microchip: document icicle reference design Conor Dooley
2022-09-16 11:26 ` [PATCH v5 02/10] dt-bindings: riscv: microchip: document the aries m100pfsevp Conor Dooley
2022-09-16 11:26 ` [PATCH v5 03/10] dt-bindings: riscv: microchip: document the sev kit Conor Dooley
2022-09-16 11:26 ` [PATCH v5 04/10] riscv: dts: microchip: add pci dma ranges for the icicle kit Conor Dooley
2022-09-16 11:26 ` [PATCH v5 05/10] riscv: dts: microchip: move the mpfs' pci node to -fabric.dtsi Conor Dooley
2022-09-16 11:26 ` [PATCH v5 06/10] riscv: dts: microchip: icicle: update pci address properties Conor Dooley
2022-09-16 11:26 ` [PATCH v5 07/10] riscv: dts: microchip: icicle: re-jig fabric peripheral addresses Conor Dooley
2022-09-16 11:26 ` [PATCH v5 08/10] riscv: dts: microchip: reduce the fic3 clock rate Conor Dooley
2022-09-16 11:26 ` [PATCH v5 09/10] riscv: dts: microchip: add sevkit device tree Conor Dooley
2022-09-16 11:26 ` [PATCH v5 10/10] riscv: dts: microchip: add a devicetree for aries' m100pfsevp Conor Dooley
2022-09-19 18:22 ` Conor Dooley [this message]
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=YyizYqHFG3vKrKFU@spud \
--to=conor@kernel.org \
--cc=Cyril.Jean@microchip.com \
--cc=aou@eecs.berkeley.edu \
--cc=conor.dooley@microchip.com \
--cc=daire.mcnamara@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=hugh.breslin@microchip.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lewis.hanly@microchip.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=praveen.kumar@microchip.com \
--cc=robh+dt@kernel.org \
--cc=shravan.chippa@microchip.com \
--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).