From: Helen Koike <helen.koike@collabora.com>
To: devicetree@vger.kernel.org, linux-media@vger.kernel.org,
linux-rockchip@lists.infradead.org
Cc: linux-kernel@vger.kernel.org, devel@driverdev.osuosl.org,
robh+dt@kernel.org, heiko@sntech.de, hverkuil-cisco@xs4all.nl,
kernel@collabora.com, dafna.hirschfeld@collabora.com,
ezequiel@collabora.com, mark.rutland@arm.com,
karthik.poduval@gmail.com, jbx6244@gmail.com, kishon@ti.com,
tfiga@chromium.org, eddie.cai.linux@gmail.com,
zhengsq@rock-chips.com
Subject: [PATCH v3 4/9] media: staging: dt-bindings: rkisp1: fix "no reg" error in parent node
Date: Thu, 2 Jul 2020 13:54:05 -0300 [thread overview]
Message-ID: <20200702165410.2583375-5-helen.koike@collabora.com> (raw)
In-Reply-To: <20200702165410.2583375-1-helen.koike@collabora.com>
Fix the following error found with make ARCH=arm64 dt_binding_check:
Documentation/devicetree/bindings/media/rockchip-isp1.example.dts:24.27-101.11:
Warning (unit_address_vs_reg): /example-0/parent@0: node has a unit name, but no reg or ranges property
Reported-by: Johan Jonker <jbx6244@gmail.com>
Signed-off-by: Helen Koike <helen.koike@collabora.com>
---
V3:
- this is a new patch in the series
---
.../Documentation/devicetree/bindings/media/rockchip-isp1.yaml | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/staging/media/rkisp1/Documentation/devicetree/bindings/media/rockchip-isp1.yaml b/drivers/staging/media/rkisp1/Documentation/devicetree/bindings/media/rockchip-isp1.yaml
index e5b9c0574e352..4d111ef2e89c7 100644
--- a/drivers/staging/media/rkisp1/Documentation/devicetree/bindings/media/rockchip-isp1.yaml
+++ b/drivers/staging/media/rkisp1/Documentation/devicetree/bindings/media/rockchip-isp1.yaml
@@ -126,6 +126,7 @@ examples:
#include <dt-bindings/power/rk3399-power.h>
parent0: parent@0 {
+ reg = <0 0>;
#address-cells = <2>;
#size-cells = <2>;
--
2.26.0
next prev parent reply other threads:[~2020-07-02 16:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-02 16:54 [PATCH v3 0/9] move Rockchip ISP bindings out of staging / add Helen Koike
2020-07-02 16:54 ` [PATCH v3 1/9] media: staging: dt-bindings: rkisp1: add missing required nodes Helen Koike
2020-07-02 16:54 ` [PATCH v3 2/9] media: staging: dt-bindings: rkisp1: add required items in i2c example Helen Koike
2020-07-02 16:54 ` [PATCH v3 3/9] media: staging: dt-bindings: rkisp1: re-order properties Helen Koike
2020-07-02 16:54 ` Helen Koike [this message]
2020-07-02 16:54 ` [PATCH v3 5/9] media: staging: rkisp1: remove unecessary clocks Helen Koike
2020-07-02 17:01 ` Helen Koike
2020-07-02 16:54 ` [PATCH v3 6/9] dt-bindings: media: rkisp1: move rockchip-isp1 bindings out of staging Helen Koike
2020-07-02 16:54 ` [PATCH v3 7/9] media: MAINTAINERS: rkisp1: add path to dt-bindings Helen Koike
2020-07-02 16:54 ` [PATCH v3 8/9] arm64: dts: rockchip: add isp0 node for rk3399 Helen Koike
2020-07-02 16:54 ` [PATCH v3 9/9] arm64: dts: rockchip: add isp and sensors for Scarlet Helen Koike
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=20200702165410.2583375-5-helen.koike@collabora.com \
--to=helen.koike@collabora.com \
--cc=dafna.hirschfeld@collabora.com \
--cc=devel@driverdev.osuosl.org \
--cc=devicetree@vger.kernel.org \
--cc=eddie.cai.linux@gmail.com \
--cc=ezequiel@collabora.com \
--cc=heiko@sntech.de \
--cc=hverkuil-cisco@xs4all.nl \
--cc=jbx6244@gmail.com \
--cc=karthik.poduval@gmail.com \
--cc=kernel@collabora.com \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=tfiga@chromium.org \
--cc=zhengsq@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;
as well as URLs for NNTP newsgroup(s).