[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20151207193215.GI29051@jcartwri.amer.corp.natinst.com>
Date: Mon, 7 Dec 2015 13:32:15 -0600
From: Josh Cartwright <joshc@...com>
To: Neil Armstrong <narmstrong@...libre.com>
Cc: Nicolas Ferre <nicolas.ferre@...el.com>,
"David S. Miller" <davem@...emloft.net>,
Harini Katakam <harini.katakam@...inx.com>,
Boris BREZILLON <boris.brezillon@...e-electrons.com>,
Alexandre Belloni <alexandre.belloni@...e-electrons.com>,
linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
devicetree@...r.kernel.org
Subject: Re: [PATCH net 1/2] net: cadence: macb: Disable USRIO register on
some platforms
On Mon, Dec 07, 2015 at 11:58:33AM +0100, Neil Armstrong wrote:
> On some platforms, the macb integration does not use the USRIO
> register to configure the (R)MII port and clocks.
> When the register is not implemented and the MACB error signal
> is connected to the bus error, reading or writing to the USRIO
> register can trigger some Imprecise External Aborts on ARM platforms.
> ---
Does this make sense to even be a separate bool device tree property?
This sort of configuration is typically done by:
1. Creating a new 'caps' bit; relevant codepaths check that bit
2. Creating a new "compatible" string for your platform's macb
instance
3. Creating a new 'struct macb_config' instance for your platform,
setting any relevant caps bits when it is selected.
Josh
Download attachment "signature.asc" of type "application/pgp-signature" (474 bytes)
Powered by blists - more mailing lists