Re: [PATCH 01/29] ARM: orion5x: fix target ID for crypto SRAM window

2014-04-16 Thread Jason Cooper
On Sun, Apr 13, 2014 at 04:39:38PM +0200, Thomas Petazzoni wrote: > In commit 4ca2c04085a1caa903e92a5fc0da25362150aac2 ('ARM: orion5x: > Move to ID based window creation'), the mach-orion5x code was changed > to use the new mvebu-mbus API. However, in the process, a mistake was > made on the crypto

Re: [PATCH 01/29] ARM: orion5x: fix target ID for crypto SRAM window

2014-04-14 Thread Sebastian Hesselbarth
On 04/13/2014 04:39 PM, Thomas Petazzoni wrote: In commit 4ca2c04085a1caa903e92a5fc0da25362150aac2 ('ARM: orion5x: Move to ID based window creation'), the mach-orion5x code was changed to use the new mvebu-mbus API. However, in the process, a mistake was made on the crypto SRAM window target ID:

[PATCH 01/29] ARM: orion5x: fix target ID for crypto SRAM window

2014-04-13 Thread Thomas Petazzoni
In commit 4ca2c04085a1caa903e92a5fc0da25362150aac2 ('ARM: orion5x: Move to ID based window creation'), the mach-orion5x code was changed to use the new mvebu-mbus API. However, in the process, a mistake was made on the crypto SRAM window target ID: it should have been 0x9 (verified in the datasheet