Re: [PATCH] tools/arm: Fix nr_spis handling v2

On Tue Mar 18, 2025 at 9:00 AM GMT, Michal Orzel wrote: > We are missing a way to detect whether a user provided a value for > nr_spis equal to 0 or did not provide any value (default is also 0) which > can cause issues when calculated nr_spis is > 0 and the value from domain > config is 0. Fix it

Re: [PATCH] tools/arm: Fix nr_spis handling v2

On Mon Mar 24, 2025 at 3:31 PM GMT, Michal Orzel wrote: > > > On 24/03/2025 16:22, Alejandro Vallejo wrote: > > > > > > On Mon Mar 24, 2025 at 1:08 PM GMT, Michal Orzel wrote: > >> > >> > >> On 19/03/2025 15:01, Alejandro Vallejo wrote: > >>> > >>> Doesn't this regenerate the golang bindings? > >

Re: [PATCH] tools/arm: Fix nr_spis handling v2

On 24/03/2025 16:22, Alejandro Vallejo wrote: > > > On Mon Mar 24, 2025 at 1:08 PM GMT, Michal Orzel wrote: >> >> >> On 19/03/2025 15:01, Alejandro Vallejo wrote: >>> >>> Doesn't this regenerate the golang bindings? >> FYI, it does not. The bindings are already there for NrSpis and default >>

Re: [PATCH] tools/arm: Fix nr_spis handling v2

On Mon Mar 24, 2025 at 1:08 PM GMT, Michal Orzel wrote: > > > On 19/03/2025 15:01, Alejandro Vallejo wrote: > > > > Doesn't this regenerate the golang bindings? > FYI, it does not. The bindings are already there for NrSpis and default value > is > does not result in a change (for verification I c

Re: [PATCH] tools/arm: Fix nr_spis handling v2

On 19/03/2025 15:01, Alejandro Vallejo wrote: > > > On Tue Mar 18, 2025 at 9:00 AM GMT, Michal Orzel wrote: >> We are missing a way to detect whether a user provided a value for >> nr_spis equal to 0 or did not provide any value (default is also 0) which >> can cause issues when calculated nr_

Re: [PATCH] tools/arm: Fix nr_spis handling v2

On 20/03/2025 17:46, Anthony PERARD wrote: > > > On Tue, Mar 18, 2025 at 10:00:13AM +0100, Michal Orzel wrote: >> We are missing a way to detect whether a user provided a value for >> nr_spis equal to 0 or did not provide any value (default is also 0) which >> can cause issues when calculated

Re: [PATCH] tools/arm: Fix nr_spis handling v2

On Tue, Mar 18, 2025 at 10:00:13AM +0100, Michal Orzel wrote: > We are missing a way to detect whether a user provided a value for > nr_spis equal to 0 or did not provide any value (default is also 0) which > can cause issues when calculated nr_spis is > 0 and the value from domain > config is 0. F

Re: [PATCH] tools/arm: Fix nr_spis handling v2

On Wed Mar 19, 2025 at 2:05 PM GMT, Andrew Cooper wrote: > On 19/03/2025 2:01 pm, Alejandro Vallejo wrote: > > On Tue Mar 18, 2025 at 9:00 AM GMT, Michal Orzel wrote: > >> We are missing a way to detect whether a user provided a value for > >> nr_spis equal to 0 or did not provide any value (defaul

Re: [PATCH] tools/arm: Fix nr_spis handling v2

On 19/03/2025 15:05, Andrew Cooper wrote: > > > On 19/03/2025 2:01 pm, Alejandro Vallejo wrote: >> On Tue Mar 18, 2025 at 9:00 AM GMT, Michal Orzel wrote: >>> We are missing a way to detect whether a user provided a value for >>> nr_spis equal to 0 or did not provide any value (default is also

Re: [PATCH] tools/arm: Fix nr_spis handling v2

On 19/03/2025 2:01 pm, Alejandro Vallejo wrote: > On Tue Mar 18, 2025 at 9:00 AM GMT, Michal Orzel wrote: >> We are missing a way to detect whether a user provided a value for >> nr_spis equal to 0 or did not provide any value (default is also 0) which >> can cause issues when calculated nr_spis is

Re: [PATCH] tools/arm: Fix nr_spis handling v2

Hi Michal, > On 18 Mar 2025, at 09:00, Michal Orzel wrote: > > We are missing a way to detect whether a user provided a value for > nr_spis equal to 0 or did not provide any value (default is also 0) which > can cause issues when calculated nr_spis is > 0 and the value from domain > config is 0.