linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: Martin Hicks <mort@bork.org>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] powerpc/fsl: Add empty ranges to etsec2 dts files
Date: Mon, 12 Jan 2015 15:31:54 -0600	[thread overview]
Message-ID: <1421098314.4961.109.camel@freescale.com> (raw)
In-Reply-To: <20150112152749.GA5450@darwin.bork.org>

On Mon, 2015-01-12 at 10:27 -0500, Martin Hicks wrote:
> 
> With an earlier change (746c9e9f - Fix PowerPC address parsing hack), ethernet
> has broken on Freescale boards such as the P1022.  All ranges used by the
> ethernet controllers are also covered by sub-devices that properly
> declared the used ranges.  The error shown is:
> 
> fsl-gianfar: probe of soc@ffe00000:ethernet@b0000 failed with error -12
> 
> Signed-off-by: Martin Hicks <mort@bork.org>
> ---
>  arch/powerpc/boot/dts/fsl/pq3-etsec2-0.dtsi |    1 +
>  arch/powerpc/boot/dts/fsl/pq3-etsec2-1.dtsi |    1 +
>  arch/powerpc/boot/dts/fsl/pq3-etsec2-2.dtsi |    1 +
>  3 files changed, 3 insertions(+)

http://patchwork.ozlabs.org/patch/422446/

> diff --git a/arch/powerpc/boot/dts/fsl/pq3-etsec2-0.dtsi b/arch/powerpc/boot/dts/fsl/pq3-etsec2-0.dtsi
> index 1382fec..d1a6c48 100644
> --- a/arch/powerpc/boot/dts/fsl/pq3-etsec2-0.dtsi
> +++ b/arch/powerpc/boot/dts/fsl/pq3-etsec2-0.dtsi
> @@ -43,6 +43,7 @@ mdio@24000 {
>  ethernet@b0000 {
>  	#address-cells = <1>;
>  	#size-cells = <1>;
> +	ranges = <>;

The " = <>" is usually omitted for empty properties.

-Scott

  reply	other threads:[~2015-01-12 21:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-12 15:27 [PATCH] powerpc/fsl: Add empty ranges to etsec2 dts files Martin Hicks
2015-01-12 21:31 ` Scott Wood [this message]
2015-01-14 18:36   ` Martin Hicks
2015-01-14 20:45     ` jeclark2006

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=1421098314.4961.109.camel@freescale.com \
    --to=scottwood@freescale.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mort@bork.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).