From: Stefan Wahren <wahrenst@gmx.net>
To: Florian Fainelli <f.fainelli@gmail.com>,
linux-arm-kernel@lists.infradead.org
Cc: "Mark Rutland" <mark.rutland@arm.com>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
"Scott Branden" <sbranden@broadcom.com>,
"Ray Jui" <rjui@broadcom.com>, "Rafał Miłecki" <zajec5@gmail.com>,
"open list" <linux-kernel@vger.kernel.org>,
"Rob Herring" <robh+dt@kernel.org>,
"maintainer:BROADCOM IPROC ARM ARCHITECTURE"
<bcm-kernel-feedback-list@broadcom.com>,
"Gregory Fong" <gregory.0xf0@gmail.com>,
"Hauke Mehrtens" <hauke@hauke-m.de>,
"Brian Norris" <computersforpeace@gmail.com>
Subject: Re: [PATCH 0/7] ARM: dts: Broadcom: Fix W=1 DTC warnings
Date: Thu, 30 May 2019 12:12:42 +0200 [thread overview]
Message-ID: <070047b5-a101-e7b3-9ef3-7afc765921d9@gmx.net> (raw)
In-Reply-To: <20190528230134.27007-1-f.fainelli@gmail.com>
Hi Florian,
Am 29.05.19 um 01:01 schrieb Florian Fainelli:
> Hi all,
>
> This patch series attempts to fix the most obvious W=1 DTC warnings for
> Broadcom SoCs DTS files. Stefan, if you could do the same for all
> bcm283* that would be fantastic.
we tried to fix as much as possible in the past. So there are only those
left, which i don't know how to fix it properly (and without breaking
things):
arch/arm/boot/dts/bcm283x.dtsi:54.6-651.4: Warning
(unit_address_vs_reg): /soc: node has a reg or ranges property, but no
unit name
This from the SoC specific dtsi files which add values for the ranges /
dma-ranges.
soc {
ranges = <0x7e000000 0x20000000 0x02000000>;
dma-ranges = <0x40000000 0x00000000 0x20000000>;
};
arch/arm/boot/dts/bcm283x.dtsi:648.12-650.5: Warning (simple_bus_reg):
/soc/gpu: missing or empty reg/ranges property
This comes from the following simple bus child node:
vc4: gpu {
compatible = "brcm,bcm2835-vc4";
};
This issue should also exists in bcm-cygnus.dtsi. From the hardware side
the GPU is part of the SoC, but maybe we should move this node out of
the SoC simple bus?
Stefan
prev parent reply other threads:[~2019-05-30 10:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-28 23:01 Florian Fainelli
2019-05-28 23:01 ` [PATCH 1/7] ARM: dts: Fix BCM7445 " Florian Fainelli
2019-06-11 21:53 ` Florian Fainelli
2019-05-28 23:01 ` [PATCH 2/7] ARM: dts: Cygnus: Fix most DTC W=1 warnings Florian Fainelli
2019-06-11 21:54 ` Florian Fainelli
2019-05-28 23:01 ` [PATCH 3/7] ARM: dts: bcm-mobile: " Florian Fainelli
2019-06-11 21:54 ` Florian Fainelli
2019-05-28 23:01 ` [PATCH 4/7] ARM: dts: BCM53573: Fix " Florian Fainelli
2019-06-11 21:54 ` Florian Fainelli
2019-05-28 23:01 ` [PATCH 5/7] ARM: dts: BCM63xx: " Florian Fainelli
2019-06-11 21:56 ` Florian Fainelli
2019-05-28 23:01 ` [PATCH 6/7] ARM: dts: BCM5301X: Fix most " Florian Fainelli
2019-06-11 22:08 ` Florian Fainelli
2019-05-28 23:01 ` [PATCH 7/7] ARM: dts: NSP: Fix the bulk of W=1 DTC warnings Florian Fainelli
2019-06-11 21:58 ` Florian Fainelli
2019-05-30 10:12 ` Stefan Wahren [this message]
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=070047b5-a101-e7b3-9ef3-7afc765921d9@gmx.net \
--to=wahrenst@gmx.net \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=computersforpeace@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=gregory.0xf0@gmail.com \
--cc=hauke@hauke-m.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=rjui@broadcom.com \
--cc=robh+dt@kernel.org \
--cc=sbranden@broadcom.com \
--cc=zajec5@gmail.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
all inboxes | Powered by JetHome®