Re: [PATCH 1/2] arm: dts: bcm5301x: Add syscon based reboot in DT

2016-06-28 Thread Jon Mason
On Tue, Jun 28, 2016 at 6:13 PM, Scott Branden wrote: > > > On 16-06-28 03:10 PM, Jon Mason wrote: >> >> From: Jon Mason >> >> Add the ability to reboot via a reset of the processor. This is >> achieved via a write of 0x39 to the CRU Reset

Re: [PATCH 1/2] arm: dts: bcm5301x: Add syscon based reboot in DT

2016-06-28 Thread Jon Mason
On Tue, Jun 28, 2016 at 6:13 PM, Scott Branden wrote: > > > On 16-06-28 03:10 PM, Jon Mason wrote: >> >> From: Jon Mason >> >> Add the ability to reboot via a reset of the processor. This is >> achieved via a write of 0x39 to the CRU Reset Register. Unfortunately, >> this only resets the core

[PATCH 1/2] arm: dts: bcm5301x: Add syscon based reboot in DT

2016-06-28 Thread Jon Mason
From: Jon Mason Add the ability to reboot via a reset of the processor. This is achieved via a write of 0x39 to the CRU Reset Register. Unfortunately, this only resets the core and not the other IP blocks. So if possible, other methods should be used on the individual

[PATCH 1/2] arm: dts: bcm5301x: Add syscon based reboot in DT

2016-06-28 Thread Jon Mason
From: Jon Mason Add the ability to reboot via a reset of the processor. This is achieved via a write of 0x39 to the CRU Reset Register. Unfortunately, this only resets the core and not the other IP blocks. So if possible, other methods should be used on the individual boards. Signed-off-by:

Re: [PATCH 1/2] arm: dts: bcm5301x: Add syscon based reboot in DT

2016-06-28 Thread Scott Branden
On 16-06-28 03:10 PM, Jon Mason wrote: From: Jon Mason Add the ability to reboot via a reset of the processor. This is achieved via a write of 0x39 to the CRU Reset Register. Unfortunately, this only resets the core and not the other IP blocks. So if possible, other

Re: [PATCH 1/2] arm: dts: bcm5301x: Add syscon based reboot in DT

2016-06-28 Thread Scott Branden
On 16-06-28 03:10 PM, Jon Mason wrote: From: Jon Mason Add the ability to reboot via a reset of the processor. This is achieved via a write of 0x39 to the CRU Reset Register. Unfortunately, this only resets the core and not the other IP blocks. So if possible, other methods should be used