Re: [RFC PATCH 0/3] watchdog servicing during decompression

2019-10-17 Thread Russell King - ARM Linux admin
On Thu, Oct 17, 2019 at 02:34:52PM +0200, Rasmus Villemoes wrote: > On 17/10/2019 14.03, Russell King - ARM Linux admin wrote: > > We used to have this on ARM - it was called from the decompressor > > code via an arch_decomp_wdog() hook. > > > > That code got removed because it is entirely

Re: [RFC PATCH 0/3] watchdog servicing during decompression

2019-10-17 Thread Rasmus Villemoes
On 17/10/2019 14.03, Russell King - ARM Linux admin wrote: > We used to have this on ARM - it was called from the decompressor > code via an arch_decomp_wdog() hook. > > That code got removed because it is entirely unsuitable for a multi- > platform kernel. This looks like it takes an address

Re: [RFC PATCH 0/3] watchdog servicing during decompression

2019-10-17 Thread Russell King - ARM Linux admin
We used to have this on ARM - it was called from the decompressor code via an arch_decomp_wdog() hook. That code got removed because it is entirely unsuitable for a multi- platform kernel. This looks like it takes an address for the watchdog from the Kconfig, and builds that into the

[RFC PATCH 0/3] watchdog servicing during decompression

2019-10-17 Thread Rasmus Villemoes
Many custom boards have an always-running external watchdog circuit. When the timeout of that watchdog is small, one cannot boot a compressed kernel since the board gets reset before it even starts booting the kernel proper. One way around that is to do the decompression in a bootloader which