devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: linux-renesas-soc@vger.kernel.org, Rob Herring <robh@kernel.org>
Cc: "Wolfram Sang" <wsa+renesas@sang-engineering.com>,
	"Andy Shevchenko" <andy@kernel.org>,
	"Conor Dooley" <conor+dt@kernel.org>,
	"David Lechner" <dlechner@baylibre.com>,
	devicetree@vger.kernel.org,
	"Geert Uytterhoeven" <geert+renesas@glider.be>,
	"Jonathan Cameron" <jic23@kernel.org>,
	"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
	"Lars-Peter Clausen" <lars@metafoo.de>,
	linux-iio@vger.kernel.org, "Magnus Damm" <magnus.damm@gmail.com>,
	"Michael Hennerich" <Michael.Hennerich@analog.com>,
	"Nuno Sá" <nuno.sa@analog.com>
Subject: [RFC PATCH 0/2] another 'interrupts-extended' replacement needed?
Date: Mon,  6 Oct 2025 19:21:16 +0200	[thread overview]
Message-ID: <20251006172119.2888-1-wsa+renesas@sang-engineering.com> (raw)

Hi Rob,

I want to fix the following 'dtbs_check' issue:

arch/arm/boot/dts/renesas/sh73a0-kzm9g.dtb: accelerometer@1d (adi,adxl345): interrupts-extended: [[18, 2, 4], [18, 3, 4]] is too long
	from schema $id: http://devicetree.org/schemas/iio/accel/adi,adxl345.yaml#

However, this series uncovers another place where 'interrupts-extended'
is not recognized as an alternative to 'interrupts'. Namely, when this
is part of a 'dependencies:' like in this binding:

arch/arm/boot/dts/renesas/sh73a0-kzm9g.dtb: accelerometer@1d (adi,adxl345): 'interrupts' is a dependency of 'interrupt-names'
	from schema $id: http://devicetree.org/schemas/iio/accel/adi,adxl345.yaml#

Now, I wonder if this also needs to be fixed in dtschema? Or do we need
another way to express the dependency?

Thanks for any pointers,

   Wolfram


Wolfram Sang (2):
  dt-bindings: iio: accel: adxl345: document second interrupt
  ARM: dts: renesas: kzm9g: name interrupts for accelerometer

 .../bindings/iio/accel/adi,adxl345.yaml          | 16 +++++++++++-----
 arch/arm/boot/dts/renesas/sh73a0-kzm9g.dts       |  1 +
 2 files changed, 12 insertions(+), 5 deletions(-)

-- 
2.47.2


             reply	other threads:[~2025-10-06 17:21 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-06 17:21 Wolfram Sang [this message]
2025-10-06 17:21 ` [RFC PATCH 1/2] dt-bindings: iio: accel: adxl345: document second interrupt Wolfram Sang
2025-10-08  9:51   ` Geert Uytterhoeven
2025-10-09 20:47   ` Rob Herring
2025-10-09 21:44     ` Wolfram Sang
2025-11-06  8:44       ` Geert Uytterhoeven
2025-10-10  7:55     ` Geert Uytterhoeven
2025-10-06 17:21 ` [RFC PATCH 2/2] ARM: dts: renesas: kzm9g: name interrupts for accelerometer Wolfram Sang
2025-10-08  9:51   ` Geert Uytterhoeven
2025-10-09 20:35 ` [RFC PATCH 0/2] another 'interrupts-extended' replacement needed? Rob Herring
2025-10-09 20:38   ` Rob Herring
2025-10-09 21:47     ` Wolfram Sang
2025-10-10  9:39       ` Wolfram Sang

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=20251006172119.2888-1-wsa+renesas@sang-engineering.com \
    --to=wsa+renesas@sang-engineering.com \
    --cc=Michael.Hennerich@analog.com \
    --cc=andy@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=geert+renesas@glider.be \
    --cc=jic23@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=nuno.sa@analog.com \
    --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;
as well as URLs for NNTP newsgroup(s).