mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Hannah Peuckmann <hannah.peuckmann@canonical.com>
To: linux-riscv@lists.infradead.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Cc: Emil Renner Berthing <kernel@esmil.dk>,
	Conor Dooley <conor@kernel.org>, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Paul Walmsley <paul.walmsley@sifive.com>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	Albert Ou <aou@eecs.berkeley.edu>,
	Walker Chen <walker.chen@starfivetech.com>,
	Hal Feng <hal.feng@starfivetech.com>,
	Xingyu Wu <xingyu.wu@starfivetech.com>
Subject: [PATCH v1 0/2] riscv: dts: starfive: visionfive 2: Remove non-existing hardware
Date: Mon, 15 Apr 2024 14:50:31 +0200	[thread overview]
Message-ID: <20240415125033.86909-1-hannah.peuckmann@canonical.com> (raw)

This series fixes the device tree for the VisionFive 2 which has nodes for
non-existing hardware which should have been left to overlays. It also results
in error on boot when both both the TDM and I2S drivers tries to claim GPIO 44.

Hannah Peuckmann (2):
  riscv: dts: starfive: visionfive 2: Remove non-existing TDM hardware
  riscv: dts: starfive: visionfive 2: Remove non-existing I2S hardware

 .../jh7110-starfive-visionfive-2.dtsi         | 98 -------------------
 1 file changed, 98 deletions(-)

-- 
2.40.1


             reply	other threads:[~2024-04-15 12:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-15 12:50 Hannah Peuckmann [this message]
2024-04-15 12:50 ` [PATCH v1 1/2] riscv: dts: starfive: visionfive 2: Remove non-existing TDM hardware Hannah Peuckmann
2024-04-15 12:50 ` [PATCH v1 2/2] riscv: dts: starfive: visionfive 2: Remove non-existing I2S hardware Hannah Peuckmann
2024-04-15 15:06 ` [PATCH v1 0/2] riscv: dts: starfive: visionfive 2: Remove non-existing hardware Emil Renner Berthing
2024-04-15 15:31 ` 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=20240415125033.86909-1-hannah.peuckmann@canonical.com \
    --to=hannah.peuckmann@canonical.com \
    --cc=aou@eecs.berkeley.edu \
    --cc=conor@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=hal.feng@starfivetech.com \
    --cc=kernel@esmil.dk \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=robh@kernel.org \
    --cc=walker.chen@starfivetech.com \
    --cc=xingyu.wu@starfivetech.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

all inboxes | Powered by JetHome®