From: Ray Jui <rjui@broadcom.com>
To: Florian Fainelli <f.fainelli@gmail.com>,
Rob Herring <robh+dt@kernel.org>
Cc: Pawel Moll <pawel.moll@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
bcm-kernel-feedback-list@broadcom.com,
devicetree@vger.kernel.org
Subject: Re: [PATCH] Enable PCIe PHY support in Cygnus
Date: Tue, 1 Dec 2015 15:16:54 -0800 [thread overview]
Message-ID: <565E2A66.7050306@broadcom.com> (raw)
In-Reply-To: <565E2969.7000500@gmail.com>
On 12/1/2015 3:12 PM, Florian Fainelli wrote:
> On 24/11/15 16:12, Florian Fainelli wrote:
>> On 18/11/15 10:16, Ray Jui wrote:
>>> This patch enales PCIe PHY in device tree for Broadcom Cygnus based platforms
>>>
>>> This patch is developed based on v4.4-rc1 and available here:
>>> https://github.com/Broadcom/cygnus-linux/tree/cygnus-pcie-phy-dt-v1
>>>
>>> Ray Jui (1):
>>> ARM: dts: enable PCIe PHY support for Cygnus
>>
>> Applied to devicetree/next with Scott's Acked-by, thanks!
>
> This caused the DTC compiler to warn:
>
> Warning (reg_format): "reg" property in /axi/phy@0301d0a0/phy@0 has
> invalid length (4 bytes) (#address-cells == 2, #size-cells == 1)
> Warning (reg_format): "reg" property in /axi/phy@0301d0a0/phy@1 has
> invalid length (4 bytes) (#address-cells == 2, #size-cells == 1)
> Warning (avoid_default_addr_size): Relying on default #address-cells
> value for /axi/phy@0301d0a0/phy@0
> Warning (avoid_default_addr_size): Relying on default #size-cells value
> for /axi/phy@0301d0a0/phy@0
> Warning (avoid_default_addr_size): Relying on default #address-cells
> value for /axi/phy@0301d0a0/phy@1
> Warning (avoid_default_addr_size): Relying on default #size-cells value
> for /axi/phy@0301d0a0/phy@1
> CC drivers/base/power/runtime.o
> DTC arch/arm/boot/dts/bcm911360k.dtb
> CC lib/bitmap.o
>
> I added an #address-cells = <0> and #size-cells = <1> to fix this, since
> your reg property is a single digit.
>
Sorry I missed that. Both are required properties.
Thanks!
Ray
next prev parent reply other threads:[~2015-12-01 23:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-18 18:16 [PATCH] Enable PCIe PHY support in Cygnus Ray Jui
2015-11-18 18:16 ` [PATCH] ARM: dts: enable PCIe PHY support for Cygnus Ray Jui
[not found] ` <1447870619-2828-2-git-send-email-rjui-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>
2015-11-23 18:50 ` Ray Jui
2015-11-23 18:57 ` Scott Branden
[not found] ` <1447870619-2828-1-git-send-email-rjui-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>
2015-11-25 0:12 ` [PATCH] Enable PCIe PHY support in Cygnus Florian Fainelli
2015-12-01 23:12 ` Florian Fainelli
2015-12-01 23:16 ` Ray Jui [this message]
[not found] ` <565E2969.7000500-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-12-01 23:18 ` Arnd Bergmann
2015-12-01 23:20 ` Florian Fainelli
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=565E2A66.7050306@broadcom.com \
--to=rjui@broadcom.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pawel.moll@arm.com \
--cc=robh+dt@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).