[PATCH v2 5/5] arm: dts: am33xx, Add device node for cpsw-ctrl-macid

2014-03-15 Thread Markus Pargmann
Add cpsw-ctrl-macid to the am33xx dtsi file. It does not change the behaviour of boards with a provided mac-address, so it is safe to add it for all boards with this CPU. Signed-off-by: Markus Pargmann m...@pengutronix.de --- arch/arm/boot/dts/am33xx.dtsi | 9 + 1 file changed, 9

[PATCH v2 2/5] net: cpsw: make cpsw.h self-contained

2014-03-15 Thread Markus Pargmann
cpsw.h uses the symbol MII_BUS_ID_SIZE which is defined in linux/phy.h. Add the respective #include to not depend on users to include it themselves. Signed-off-by: Markus Pargmann m...@pengutronix.de --- drivers/net/ethernet/ti/cpsw.h | 1 + 1 file changed, 1 insertion(+) diff --git

[PATCH v2 0/5] net: cpsw: Support for am335x chip MACIDs

2014-03-15 Thread Markus Pargmann
Hi, This series introduces a driver to read and use the MACIDs stored in the am335x control module. These are read-only registers for a unique MACID. At the moment the MACIDs are generated randomly when the mac-address property is not a valid mac address. In v2 I changed the precedence of

[PATCH v2 1/5] net: cpsw: document mac-address being optional

2014-03-15 Thread Markus Pargmann
mac-address is an optional property. If no mac-address is set, a random mac-address will be generated. Signed-off-by: Markus Pargmann m...@pengutronix.de --- Documentation/devicetree/bindings/net/cpsw.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH v2 4/5] net: cpsw: Use cpsw-ctrl-macid driver

2014-03-15 Thread Markus Pargmann
Use ctrl-macid driver to obtain the macids stored in the processor. This is only done when defined in DT. The internal macid is not used if mac-address is given explicitly. So it does not change the behavior if the bootloader provides a mac address through the mac-address property Signed-off-by:

Re: [PATCHv4 4/7] hwspinlock/core: add common OF helpers

2014-03-15 Thread Ohad Ben-Cohen
On Fri, Mar 14, 2014 at 5:23 PM, Josh Cartwright jo...@codeaurora.org wrote: So, are you suggesting that because fatal errors should be extremely rare, a consuming driver should just assume that if NULL is returned from a hwspin_lock_request*() function that it was the device not yet probed

Re: [PATCH 1/5] iommu/omap: Use the cache cleaning API

2014-03-15 Thread Santosh Shilimkar
On Friday 14 March 2014 09:49 PM, Suman Anna wrote: Hi Santosh, Laurent, Russell, Arnd, On 03/14/2014 12:51 PM, Santosh Shilimkar wrote: On Friday 14 March 2014 12:38 PM, Laurent Pinchart wrote: Hi Santosh, On Friday 14 March 2014 12:15:11 Santosh Shilimkar wrote: + Russell, Arnd On