diff options
| author |   Uwe Kleine-König <u.kleine-koenig@pengutronix.de> | 2024-04-05 23:42:28 +0200 |
|---|---|---|
| committer |   Shawn Guo <shawnguo@kernel.org> | 2024-04-28 15:56:15 +0800 |
| commit | e80729dbfbdc673914416e8e0aa926284278cecf (patch) | |
| tree | 0c52d2816cbbbcad474f1730f235a460a786edaa /tools/perf/scripts/python/call-graph-from-postgresql.py | |
| parent | ARM: dts: imx6sx-sdb: Use #pwm-cells = <3> for imx27-pwm device (diff) | |
| download | wireguard-linux-e80729dbfbdc673914416e8e0aa926284278cecf.tar.xz wireguard-linux-e80729dbfbdc673914416e8e0aa926284278cecf.zip | |
ARM: dts: imx6sx-softing-vining-2000: Use #pwm-cells = <3> for imx27-pwm device
The binding dictates using 3 pwm-cells. Adhere to that.
This fixes the following dtbs_check warnings:
arch/arm/boot/dts/nxp/imx/imx6sx-softing-vining-2000.dtb: pwm@2080000: #pwm-cells:0:0: 3 was expected
from schema : http://devicetree.org/schemas/pwm/imx-pwm.yaml#
arch/arm/boot/dts/nxp/imx/imx6sx-softing-vining-2000.dtb: pwm@2084000: #pwm-cells:0:0: 3 was expected
from schema : http://devicetree.org/schemas/pwm/imx-pwm.yaml#
arch/arm/boot/dts/nxp/imx/imx6sx-softing-vining-2000.dtb: pwm@22a8000: #pwm-cells:0:0: 3 was expected
from schema : http://devicetree.org/schemas/pwm/imx-pwm.yaml#
There is no need for an explicit status = "okay" in the pwm nodes as
the soc dtsi doesn't disable these devices. Drop these properties, too.
Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
Signed-off-by: Shawn Guo <shawnguo@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions