Linux-RISC-V Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: linux-riscv@lists.infradead.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>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	Valentina.FernandezAlanis@microchip.com,
	Brian.Burke@microchip.com, cyril.jean@microchip.com
Subject: [PATCH v1 0/5] riscv: dts: minor beaglev-fire improvements
Date: Thu, 19 Mar 2026 16:31:14 +0000	[thread overview]
Message-ID: <20260319-outsell-hypnotic-94b480408ad4@spud> (raw)

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

Yo,

Some minor improvements etc for the BeagleV Fire, spotted while updating
our downstream stuff to the latest lts.

Produces errors at the moment, as it depends on changing the
interrupt-cells in the gpio binding.

Cheers,
Conor.

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
CC: Valentina.FernandezAlanis@microchip.com
CC: Brian.Burke@microchip.com
CC: cyril.jean@microchip.com

Conor Dooley (5):
  riscv: dts: microchip: gpio controllers on mpfs need 2 interrupt cells
  riscv: dts: microchip: remove gpio hogs from beaglev-fire
  riscv: dts: microchip: clean up beaglev-fire regulator node names
  riscv: dts: microchip: add adc interrupt on beaglev-fire
  riscv: dts: microchip: add gpio line names on beaglev-fire

 .../boot/dts/microchip/mpfs-beaglev-fire.dts  | 36 ++++++++++---------
 arch/riscv/boot/dts/microchip/mpfs.dtsi       |  6 ++--
 2 files changed, 22 insertions(+), 20 deletions(-)

-- 
2.51.0


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

             reply	other threads:[~2026-03-19 16:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-19 16:31 Conor Dooley [this message]
2026-03-19 16:31 ` [PATCH v1 1/5] riscv: dts: microchip: gpio controllers on mpfs need 2 interrupt cells Conor Dooley
2026-03-19 16:31 ` [PATCH v1 2/5] riscv: dts: microchip: remove gpio hogs from beaglev-fire Conor Dooley
2026-03-19 16:31 ` [PATCH v1 3/5] riscv: dts: microchip: clean up beaglev-fire regulator node names Conor Dooley
2026-03-19 16:31 ` [PATCH v1 4/5] riscv: dts: microchip: add adc interrupt on beaglev-fire Conor Dooley
2026-03-19 16:31 ` [PATCH v1 5/5] riscv: dts: microchip: add gpio line names " Conor Dooley
2026-05-05  9:47 ` [PATCH v1 0/5] riscv: dts: minor beaglev-fire improvements 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=20260319-outsell-hypnotic-94b480408ad4@spud \
    --to=conor@kernel.org \
    --cc=Brian.Burke@microchip.com \
    --cc=Valentina.FernandezAlanis@microchip.com \
    --cc=conor.dooley@microchip.com \
    --cc=cyril.jean@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox