devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: Rob Herring <robh@kernel.org>
Cc: Anup Patel <apatel@ventanamicro.com>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-riscv@lists.infradead.org,
	Saravana Kannan <saravanak@google.com>
Subject: Re: [PATCH] of: property: Fix fw_devlink handling of interrupt-map
Date: Wed, 29 May 2024 15:00:34 +0100	[thread overview]
Message-ID: <867cfcn2f1.wl-maz@kernel.org> (raw)
In-Reply-To: <CAL_JsqKOxYeNh026wmYH2JDYbR-FGjc=9gv-taB09pC4fyXKCA@mail.gmail.com>

On Wed, 29 May 2024 14:44:07 +0100,
Rob Herring <robh@kernel.org> wrote:
> 
> On Wed, May 29, 2024 at 1:33 AM Marc Zyngier <maz@kernel.org> wrote:
> >
> > On Wed, 29 May 2024 06:15:52 +0100,
> > Anup Patel <apatel@ventanamicro.com> wrote:
> > >
> > > This breaks for RISC-V because we don't have "#address-cells"
> > > property in interrupt controller DT node and of_bus_n_addr_cells()
> > > retrieves "#address-cells" from the parent of interrupt controller.
> >
> > That's a feature, not a bug. #address-cells, AFAICT, applies to all
> > child nodes until you set it otherwise.
> 
> That may be supported in some places, but only because of buggy DTs
> (we're talking 2000 era). Current dtc should warn if an interrupt
> controller node doesn't have #address-cells AND is referred to by
> interrupt-map.

Clearly that didn't deter the riscv folks from doing silly things, and
we're now stuck with more random hacks.

Anyhow, I vented enough about this, and I'm going back to doing
semi-useful stuff.

	M.

-- 
Without deviation from the norm, progress is not possible.

      reply	other threads:[~2024-05-29 14:00 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-28 16:41 [PATCH] of: property: Fix fw_devlink handling of interrupt-map Marc Zyngier
2024-05-28 17:14 ` Rob Herring (Arm)
2024-05-28 17:23 ` Saravana Kannan
2024-05-29  5:15 ` Anup Patel
2024-05-29  6:33   ` Marc Zyngier
2024-05-29 10:16     ` Anup Patel
2024-05-29 10:44       ` Marc Zyngier
2024-05-29 11:28         ` Anup Patel
2024-05-29 12:00           ` Marc Zyngier
2024-05-29 15:17             ` Conor Dooley
2024-05-29 16:37               ` Anup Patel
2024-05-29 13:51           ` Rob Herring
2024-05-29 16:46             ` Rob Herring
2024-05-29 13:44     ` Rob Herring
2024-05-29 14:00       ` Marc Zyngier [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=867cfcn2f1.wl-maz@kernel.org \
    --to=maz@kernel.org \
    --cc=apatel@ventanamicro.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=robh@kernel.org \
    --cc=saravanak@google.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;
as well as URLs for NNTP newsgroup(s).