devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Fabio Estevam <festevam@gmail.com>
Cc: Fabio Estevam <festevam@denx.de>,
	linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
	Conor Dooley <conor.dooley@microchip.com>,
	conor+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
	robh+dt@kernel.org, broonie@kernel.org, shawnguo@kernel.org
Subject: Re: [PATCH v2 1/3] dt-bindings: pfuze100.yaml: Add an entry for interrupts
Date: Tue, 30 May 2023 14:59:09 +0200	[thread overview]
Message-ID: <1ea23f76-58c2-402a-2831-ac496ef41b11@linaro.org> (raw)
In-Reply-To: <20230530125758.ke7isykxf3bg4efu@krzk-bin>

On 30/05/2023 14:57, Krzysztof Kozlowski wrote:
> On Sat, 27 May 2023 17:50:46 -0300, Fabio Estevam wrote:
>> 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(+)
>>
> 
> Running 'make dtbs_check' with the schema in this patch gives the
> following warnings. Consider if they are expected or the schema is
> incorrect. These may not be new warnings.
> 
> Note that it is not yet a requirement to have 0 warnings for dtbs_check.
> This will change in the future.
> 
> Full log is available here: https://patchwork.ozlabs.org/patch/1786770
> 
> 
> pf0100@8: $nodename:0: 'pf0100@8' does not match '^pmic@[0-9]$'
> 	arch/arm/boot/dts/imx6dl-riotboard.dtb
> 
> pfuze100@8: $nodename:0: 'pfuze100@8' does not match '^pmic@[0-9]$'

It seems you fix all these.

Best regards,
Krzysztof


  reply	other threads:[~2023-05-30 12:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-27 20:50 [PATCH v2 1/3] dt-bindings: pfuze100.yaml: Add an entry for interrupts Fabio Estevam
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 [this message]
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=1ea23f76-58c2-402a-2831-ac496ef41b11@linaro.org \
    --to=krzysztof.kozlowski@linaro.org \
    --cc=broonie@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=conor.dooley@microchip.com \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@denx.de \
    --cc=festevam@gmail.com \
    --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).