From: Johan Jonker <jbx6244@gmail.com>
To: Rob Herring <robh@kernel.org>,
thierry.reding@gmail.com, u.kleine-koenig@pengutronix.de
Cc: linux-rockchip@lists.infradead.org, philipp.tomsich@vrull.eu,
linux-arm-kernel@lists.infradead.org,
krzysztof.kozlowski+dt@linaro.org, robh+dt@kernel.org,
devicetree@vger.kernel.org, linux-pwm@vger.kernel.org,
kever.yang@rock-chips.com, zhangqing@rock-chips.com,
linux-kernel@vger.kernel.org, heiko@sntech.de
Subject: Re: [PATCH v1 03/11] dt-bindings: pwm: rockchip: add rockchip,rk3128-pwm
Date: Sat, 10 Sep 2022 21:48:04 +0200 [thread overview]
Message-ID: <1c13181b-8421-69d8-21ee-9742dd5f55dd@gmail.com> (raw)
In-Reply-To: <1662821635.180247.34700.nullmailer@robh.at.kernel.org>
Reduced CC.
Hi Rob,
The rk3328 and rv1108 PWM interrupt is chaired between blocks I think.
For rv1108 the same interrupt is used for all PWM nodes.
For rk3328 only added to one PWM node.
Currently not in use in a Linux drivers??
No consensus yet...on removing or parent node, so it stays as it is...
Maybe if you have ideas things will change. ;)
Johan
===
See discussion:
https://lore.kernel.org/linux-rockchip/20b7c702-9412-93b4-3174-e8633bc413d7@gmail.com/
On 9/10/22 16:53, Rob Herring wrote:
> On Sat, 10 Sep 2022 00:02:22 +0200, Johan Jonker wrote:
>> Add rockchip,rk3128-pwm compatible string.
>>
>> Signed-off-by: Johan Jonker <jbx6244@gmail.com>
>> ---
>> Documentation/devicetree/bindings/pwm/pwm-rockchip.yaml | 1 +
>> 1 file changed, 1 insertion(+)
>>
>
> 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/
>
>
> pwm@10280000: 'interrupts' does not match any of the regexes: 'pinctrl-[0-9]+'
> arch/arm/boot/dts/rv1108-elgin-r1.dtb
> arch/arm/boot/dts/rv1108-evb.dtb
>
> pwm@10280010: 'interrupts' does not match any of the regexes: 'pinctrl-[0-9]+'
> arch/arm/boot/dts/rv1108-elgin-r1.dtb
> arch/arm/boot/dts/rv1108-evb.dtb
>
> pwm@10280020: 'interrupts' does not match any of the regexes: 'pinctrl-[0-9]+'
> arch/arm/boot/dts/rv1108-elgin-r1.dtb
> arch/arm/boot/dts/rv1108-evb.dtb
>
> pwm@10280030: 'interrupts' does not match any of the regexes: 'pinctrl-[0-9]+'
> arch/arm/boot/dts/rv1108-elgin-r1.dtb
> arch/arm/boot/dts/rv1108-evb.dtb
>
> pwm@20040000: 'interrupts' does not match any of the regexes: 'pinctrl-[0-9]+'
> arch/arm/boot/dts/rv1108-elgin-r1.dtb
> arch/arm/boot/dts/rv1108-evb.dtb
>
> pwm@20040010: 'interrupts' does not match any of the regexes: 'pinctrl-[0-9]+'
> arch/arm/boot/dts/rv1108-elgin-r1.dtb
> arch/arm/boot/dts/rv1108-evb.dtb
>
> pwm@20040020: 'interrupts' does not match any of the regexes: 'pinctrl-[0-9]+'
> arch/arm/boot/dts/rv1108-elgin-r1.dtb
> arch/arm/boot/dts/rv1108-evb.dtb
>
> pwm@20040030: 'interrupts' does not match any of the regexes: 'pinctrl-[0-9]+'
> arch/arm/boot/dts/rv1108-elgin-r1.dtb
> arch/arm/boot/dts/rv1108-evb.dtb
>
> pwm@ff1b0030: 'interrupts' does not match any of the regexes: 'pinctrl-[0-9]+'
> arch/arm64/boot/dts/rockchip/rk3318-a95x-z2.dtb
> arch/arm64/boot/dts/rockchip/rk3328-a1.dtb
> arch/arm64/boot/dts/rockchip/rk3328-evb.dtb
> arch/arm64/boot/dts/rockchip/rk3328-nanopi-r2s.dtb
> arch/arm64/boot/dts/rockchip/rk3328-roc-cc.dtb
> arch/arm64/boot/dts/rockchip/rk3328-rock64.dtb
> arch/arm64/boot/dts/rockchip/rk3328-rock-pi-e.dtb
> arch/arm64/boot/dts/rockchip/rk3328-roc-pc.dtb
>
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2022-09-10 19:55 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220909212543.17428-1-jbx6244@gmail.com>
2022-09-09 22:01 ` [PATCH v1 11/11] dt-bindings: mtd: rockchip: add rockchip,rk3128-nfc Johan Jonker
2022-09-10 7:46 ` Krzysztof Kozlowski
2022-09-09 22:01 ` [PATCH v1 01/11] dt-bindings: serial: rockchip: add rockchip,rk3128-uart Johan Jonker
2022-09-10 15:42 ` (subset) " Mark Brown
2022-09-13 14:05 ` Rob Herring
2022-09-13 14:37 ` Jamie Iles
2022-09-14 8:52 ` (subset) " Heiko Stuebner
2022-09-09 22:01 ` [PATCH v1 10/11] dt-bindings: soc: rockchip: grf: add rockchip,rk3128-grf Johan Jonker
2022-09-13 14:06 ` Rob Herring
2022-09-09 22:01 ` [PATCH v1 09/11] dt-bindings: phy: phy-rockchip-inno-usb2: add rockchip,rk3128-usb2phy Johan Jonker
2022-09-13 14:06 ` Rob Herring
2022-09-13 16:42 ` Vinod Koul
2022-09-09 22:01 ` [PATCH v1 08/11] dt-bindings: arm: rockchip: pmu: add rockchip,rk3128-pmu Johan Jonker
2022-09-13 14:06 ` Rob Herring
2022-09-09 22:01 ` [PATCH v1 07/11] dt-bindings: watchdog: rockchip: add rockchip,rk3128-wdt Johan Jonker
2022-09-10 14:30 ` Guenter Roeck
2022-09-13 14:06 ` Rob Herring
2022-09-09 22:02 ` [PATCH v1 06/11] dt-bindings: usb: dwc2: rockchip: add rockchip,rk3128-usb Johan Jonker
2022-09-13 14:06 ` Rob Herring
2022-09-09 22:02 ` [PATCH v1 05/11] dt-bindings: spi: rockchip: add rockchip,rk3128-spi Johan Jonker
2022-09-10 14:53 ` Rob Herring
2022-09-09 22:02 ` [PATCH v1 04/11] dt-bindings: mmc: rockchip: add rockchip,rk3128-dw-mshc Johan Jonker
2022-09-13 14:15 ` Rob Herring
2022-09-14 14:00 ` Ulf Hansson
2022-09-09 22:02 ` [PATCH v1 03/11] dt-bindings: pwm: rockchip: add rockchip,rk3128-pwm Johan Jonker
2022-09-10 14:53 ` Rob Herring
2022-09-10 19:48 ` Johan Jonker [this message]
2022-09-12 16:21 ` Rob Herring
2022-09-13 14:38 ` Johan Jonker
2022-09-28 11:59 ` Thierry Reding
2022-09-29 10:26 ` Johan Jonker
2022-09-29 15:41 ` Robin Murphy
2022-09-30 6:13 ` Biju Das
2022-09-12 8:35 ` Uwe Kleine-König
2022-09-13 14:26 ` Rob Herring
2022-09-20 6:21 ` Uwe Kleine-König
2022-09-23 10:22 ` Heiko Stuebner
2022-09-09 22:02 ` [PATCH v1 02/11] dt-bindings: i2c: rockchip: add rockchip,rk3128-i2c Johan Jonker
2022-09-13 14:26 ` Rob Herring
2022-09-16 19:57 ` 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=1c13181b-8421-69d8-21ee-9742dd5f55dd@gmail.com \
--to=jbx6244@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=kever.yang@rock-chips.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=philipp.tomsich@vrull.eu \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.org \
--cc=thierry.reding@gmail.com \
--cc=u.kleine-koenig@pengutronix.de \
--cc=zhangqing@rock-chips.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