[PATCH v2 1/9] bsps/leon3: Optional IRQ(A)MP timestamp support

[Martin Åberg]

OK

On 2023-09-21 17:19, Sebastian Huber wrote:
> This is necessary to run the tests on SIS with profiling enabled.
> 
> Update #4954.
> ---
>   bsps/include/bsp/fatal.h        | 1 -
>   bsps/sparc/leon3/clock/ckinit.c | 6 ++----
>   2 files changed, 2 insertions(+), 5 deletions(-)
> 
> diff --git a/bsps/include/bsp/fatal.h b/bsps/include/bsp/fatal.h
> index 4b7d0f6ced..1726bfea54 100644
> --- a/bsps/include/bsp/fatal.h
> +++ b/bsps/include/bsp/fatal.h
> @@ -91,7 +91,6 @@ typedef enum {
>     LEON3_FATAL_CLOCK_INITIALIZATION,
>     LEON3_FATAL_INVALID_CACHE_CONFIG_BOOT_PROCESSOR,
>     LEON3_FATAL_INVALID_CACHE_CONFIG_SECONDARY_PROCESSOR,
> -  LEON3_FATAL_CLOCK_NO_IRQMP_TIMESTAMP_SUPPORT,
>   
>     /* LPC24XX fatal codes */
>     LPC24XX_FATAL_PL111_SET_UP = BSP_FATAL_CODE_BLOCK(3),
> diff --git a/bsps/sparc/leon3/clock/ckinit.c b/bsps/sparc/leon3/clock/ckinit.c
> index c335652a56..cff2991e60 100644
> --- a/bsps/sparc/leon3/clock/ckinit.c
> +++ b/bsps/sparc/leon3/clock/ckinit.c
> @@ -196,11 +196,9 @@ static void leon3_clock_use_up_counter(struct timecounter *tc)
>     tc->tc_frequency = leon3_up_counter_frequency();
>   
>   #if defined(RTEMS_PROFILING)
> -  if (irqamp_get_timestamp_registers(LEON3_IrqCtrl_Regs) == NULL) {
> -    bsp_fatal(LEON3_FATAL_CLOCK_NO_IRQMP_TIMESTAMP_SUPPORT);
> +  if (irqamp_get_timestamp_registers(LEON3_IrqCtrl_Regs) != NULL) {
> +    leon3_tc_tick = leon3_tc_tick_irqmp_timestamp_init;
>     }
> -
> -  leon3_tc_tick = leon3_tc_tick_irqmp_timestamp_init;
>   #endif
>   
>     rtems_timecounter_install(tc);

-- 
Best regards,

Martin Åberg
Software Engineer
Frontgrade Gaisler
martin.aberg at gaisler.com

Frontgrade Gaisler AB, Kungsgatan 12, SE-411 19 GÖTEBORG, Sweden.
+46 (0) 31 775 8650, www.gaisler.com

This e-mail and any files transmitted with it ("E-mail") is intended 
solely for the addressee(s) and may contain information that is 
proprietary, privileged, company confidential and/or exempt from 
disclosure under applicable law. If you are not the intended 
addressee(s), any disclosure, reproduction, copying, distribution or 
other use of the E-mail is strictly prohibited. If you have received 
this E-mail in error, please delete it and destroy all copies of this 
E-mail and notify the sender immediately via telephone call or return 
e-mail.

Neither the company nor any subsidiary or affiliate or associated 
company nor any individual sending this E-mail accepts any liability in 
respect of the content (including errors and omissions) nor shall this 
e-mail be deemed to enter the company or any subsidiary or affiliate or 
associated company into a contract or to create any legally binding 
obligations unless expressly agreed to in writing under separate cover 
and timeliness of the E-mail which arise as a result of transmission. If 
verification is required, please request a hard copy version from the 
sender.