All of lore.kernel.org
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: linux-kernel@vger.kernel.org
Cc: conor@kernel.org, Conor Dooley <conor.dooley@microchip.com>,
	Daire McNamara <daire.mcnamara@microchip.com>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	linux-riscv@lists.infradead.org, devicetree@vger.kernel.org
Subject: [PATCH v3 0/3] Add support for Microchip PIC64GX Curiosity Kit
Date: Mon, 17 Nov 2025 16:53:21 +0000	[thread overview]
Message-ID: <20251117-paprika-tipping-e7bb3e211d6f@spud> (raw)

From: Conor Dooley <conor.dooley@microchip.com>

v3 of Pierre-Henry's stuff from over a year ago:
https://lore.kernel.org/all/20240930095449.1813195-1-pierre-henry.moussay@microchip.com/
In it he said "This will be fix in a V3 coming in due time", and I guess
that due time was ~14 months.

I've cut out all the binding patches, to hopefully make their
application process more obvious to subsystem maintainers.
The only real difference in these patches is that I went off and implemented
the clock rework that I was asked for on v3, because it ended up being a
requirement for hwmon and pinctrl work on the platform, as well as
blocking this series (although it was obviously not a technical problem
with the v2 of this series).

CC: Conor Dooley <conor.dooley@microchip.com>
CC: Daire McNamara <daire.mcnamara@microchip.com>
CC: Rob Herring <robh@kernel.org>
CC: Krzysztof Kozlowski <krzk+dt@kernel.org>
CC: linux-riscv@lists.infradead.org
CC: devicetree@vger.kernel.org
CC: linux-kernel@vger.kernel.org

Pierre-Henry Moussay (3):
  dt-bindings: riscv: microchip: document the PIC64GX curiosity kit
  riscv: dts: microchip: add pic64gx and its curiosity kit
  riscv: dts: microchip: remove POLARFIRE mention in Makefile

 .../devicetree/bindings/riscv/microchip.yaml  |   7 +-
 arch/riscv/boot/dts/microchip/Makefile        |  17 +-
 .../dts/microchip/pic64gx-curiosity-kit.dts   | 165 +++++
 .../boot/dts/microchip/pic64gx-pinctrl.dtsi   | 178 +++++
 arch/riscv/boot/dts/microchip/pic64gx.dtsi    | 630 ++++++++++++++++++
 5 files changed, 987 insertions(+), 10 deletions(-)
 create mode 100644 arch/riscv/boot/dts/microchip/pic64gx-curiosity-kit.dts
 create mode 100644 arch/riscv/boot/dts/microchip/pic64gx-pinctrl.dtsi
 create mode 100644 arch/riscv/boot/dts/microchip/pic64gx.dtsi

-- 
2.51.0


_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

WARNING: multiple messages have this Message-ID (diff)
From: Conor Dooley <conor@kernel.org>
To: linux-kernel@vger.kernel.org
Cc: conor@kernel.org, Conor Dooley <conor.dooley@microchip.com>,
	Daire McNamara <daire.mcnamara@microchip.com>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	linux-riscv@lists.infradead.org, devicetree@vger.kernel.org
Subject: [PATCH v3 0/3] Add support for Microchip PIC64GX Curiosity Kit
Date: Mon, 17 Nov 2025 16:53:21 +0000	[thread overview]
Message-ID: <20251117-paprika-tipping-e7bb3e211d6f@spud> (raw)

From: Conor Dooley <conor.dooley@microchip.com>

v3 of Pierre-Henry's stuff from over a year ago:
https://lore.kernel.org/all/20240930095449.1813195-1-pierre-henry.moussay@microchip.com/
In it he said "This will be fix in a V3 coming in due time", and I guess
that due time was ~14 months.

I've cut out all the binding patches, to hopefully make their
application process more obvious to subsystem maintainers.
The only real difference in these patches is that I went off and implemented
the clock rework that I was asked for on v3, because it ended up being a
requirement for hwmon and pinctrl work on the platform, as well as
blocking this series (although it was obviously not a technical problem
with the v2 of this series).

CC: Conor Dooley <conor.dooley@microchip.com>
CC: Daire McNamara <daire.mcnamara@microchip.com>
CC: Rob Herring <robh@kernel.org>
CC: Krzysztof Kozlowski <krzk+dt@kernel.org>
CC: linux-riscv@lists.infradead.org
CC: devicetree@vger.kernel.org
CC: linux-kernel@vger.kernel.org

Pierre-Henry Moussay (3):
  dt-bindings: riscv: microchip: document the PIC64GX curiosity kit
  riscv: dts: microchip: add pic64gx and its curiosity kit
  riscv: dts: microchip: remove POLARFIRE mention in Makefile

 .../devicetree/bindings/riscv/microchip.yaml  |   7 +-
 arch/riscv/boot/dts/microchip/Makefile        |  17 +-
 .../dts/microchip/pic64gx-curiosity-kit.dts   | 165 +++++
 .../boot/dts/microchip/pic64gx-pinctrl.dtsi   | 178 +++++
 arch/riscv/boot/dts/microchip/pic64gx.dtsi    | 630 ++++++++++++++++++
 5 files changed, 987 insertions(+), 10 deletions(-)
 create mode 100644 arch/riscv/boot/dts/microchip/pic64gx-curiosity-kit.dts
 create mode 100644 arch/riscv/boot/dts/microchip/pic64gx-pinctrl.dtsi
 create mode 100644 arch/riscv/boot/dts/microchip/pic64gx.dtsi

-- 
2.51.0


             reply	other threads:[~2025-11-17 16:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-17 16:53 Conor Dooley [this message]
2025-11-17 16:53 ` [PATCH v3 0/3] Add support for Microchip PIC64GX Curiosity Kit Conor Dooley
2025-11-17 16:53 ` [PATCH v3 1/3] dt-bindings: riscv: microchip: document the PIC64GX curiosity kit Conor Dooley
2025-11-17 16:53   ` Conor Dooley
2025-11-17 21:48   ` Rob Herring (Arm)
2025-11-17 21:48     ` Rob Herring (Arm)
2025-11-17 16:53 ` [PATCH v3 2/3] riscv: dts: microchip: add pic64gx and its " Conor Dooley
2025-11-17 16:53   ` Conor Dooley
2025-11-17 16:53 ` [PATCH v3 3/3] riscv: dts: microchip: remove POLARFIRE mention in Makefile Conor Dooley
2025-11-17 16:53   ` Conor Dooley
2026-03-03 17:16 ` [PATCH v3 0/3] Add support for Microchip PIC64GX Curiosity Kit Conor Dooley
2026-03-03 17:16   ` 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=20251117-paprika-tipping-e7bb3e211d6f@spud \
    --to=conor@kernel.org \
    --cc=conor.dooley@microchip.com \
    --cc=daire.mcnamara@microchip.com \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.