devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Fabio Estevam <festevam@gmail.com>
To: shawnguo@kernel.org
Cc: broonie@kernel.org, robh+dt@kernel.org,
	krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	Fabio Estevam <festevam@denx.de>,
	Conor Dooley <conor.dooley@microchip.com>
Subject: [PATCH v2 1/3] dt-bindings: pfuze100.yaml: Add an entry for interrupts
Date: Sat, 27 May 2023 17:50:46 -0300	[thread overview]
Message-ID: <20230527205048.418360-1-festevam@gmail.com> (raw)

From: Fabio Estevam <festevam@denx.de>

The PFUZE100 PMIC has an interrupt pin that can be connected to
the host SoC. Describe it in the dt-bindings to avoid warnings like:

imx6q-zii-rdu2.dtb: pmic@8: 'interrupt-parent', 'interrupts' do not match any of the regexes: 'pinctrl-[0-9]+'
From schema: Documentation/devicetree/bindings/regulator/pfuze100.yaml

Signed-off-by: Fabio Estevam <festevam@denx.de>
Reviewed-by: Conor Dooley <conor.dooley@microchip.com>
---
Changes since v1:
- None. Only collected Conor's Reviewed-by tag.

 Documentation/devicetree/bindings/regulator/pfuze100.yaml | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/Documentation/devicetree/bindings/regulator/pfuze100.yaml b/Documentation/devicetree/bindings/regulator/pfuze100.yaml
index 67a30b23b92c..e384e4953f0a 100644
--- a/Documentation/devicetree/bindings/regulator/pfuze100.yaml
+++ b/Documentation/devicetree/bindings/regulator/pfuze100.yaml
@@ -36,6 +36,9 @@ properties:
   reg:
     maxItems: 1
 
+  interrupts:
+    maxItems: 1
+
   fsl,pfuze-support-disable-sw:
     $ref: /schemas/types.yaml#/definitions/flag
     description: |
-- 
2.34.1


             reply	other threads:[~2023-05-27 20:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-27 20:50 Fabio Estevam [this message]
2023-05-27 20:50 ` [PATCH v2 2/3] ARM: dts: imx: Use 'pmic' as node name Fabio Estevam
2023-05-30 13:01   ` Krzysztof Kozlowski
2023-06-04 12:23   ` Shawn Guo
2023-05-27 20:50 ` [PATCH v2 3/3] ARM: dts: imx6ul-ccimx6ulsom: Fix the "coin" regulator name Fabio Estevam
2023-06-04 12:24   ` Shawn Guo
2023-05-30 12:57 ` [PATCH v2 1/3] dt-bindings: pfuze100.yaml: Add an entry for interrupts Krzysztof Kozlowski
2023-05-30 12:59   ` Krzysztof Kozlowski
2023-05-30 13:00     ` Fabio Estevam
2023-05-30 15:30 ` (subset) " Mark Brown

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=20230527205048.418360-1-festevam@gmail.com \
    --to=festevam@gmail.com \
    --cc=broonie@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=conor.dooley@microchip.com \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@denx.de \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=robh+dt@kernel.org \
    --cc=shawnguo@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).