Philippe,
On 1/2/23 13:30, Cédric Le Goater wrote:
On 12/31/22 23:43, Dong, Eddie wrote:
Avoid confusing two different things:
- the WDT I/O region size ('iosize')
- at which offset the SoC map the WDT ('offset') While it is often the same, we
can map smaller region sizes at larger offsets.
On Fri, Dec 30, 2022 at 12:34:54PM +0100, Philippe Mathieu-Daudé wrote:
> Avoid confusing two different things:
> - the WDT I/O region size ('iosize')
> - at which offset the SoC map the WDT ('offset')
> While it is often the same, we can map smaller region sizes
> at larger offsets.
>
> Here we
On 12/31/22 23:43, Dong, Eddie wrote:
Avoid confusing two different things:
- the WDT I/O region size ('iosize')
- at which offset the SoC map the WDT ('offset') While it is often the same, we
can map smaller region sizes at larger offsets.
Here we are interested in the I/O region size, so
>
> Avoid confusing two different things:
> - the WDT I/O region size ('iosize')
> - at which offset the SoC map the WDT ('offset') While it is often the same,
> we
> can map smaller region sizes at larger offsets.
>
> Here we are interested in the I/O region size, so rename as 'iosize'.
>
>
Avoid confusing two different things:
- the WDT I/O region size ('iosize')
- at which offset the SoC map the WDT ('offset')
While it is often the same, we can map smaller region sizes
at larger offsets.
Here we are interested in the I/O region size, so rename as
'iosize'.
Reviewed-by: Peter
