tests: drivers: ipm: Fix drivers.ipc.mailbox

[golowanow]

Fix drivers.ipc.mailbox test suite to restore and improve its testing functionality:

• fix printf() redirection through IPM console.

• fix and check the dummy driver initialization.

• specify correct Twister harness type (Console) and use matching patterns to recognize the expected console output.

Before the fix: ./scripts/twister -p qemu_x86 -T tests/drivers/ipm

QEMU (2848302): Booting from ROM..                                                              
QEMU (2848302): unable to bind IPM console sender to 'ipm_dummy0'                               
QEMU (2848302): *** Booting Zephyr OS build v3.7.0-4704-g04dfd54eeb00 ***                       
QEMU (2848302): Running TESTSUITE test_ipm                                                      
QEMU (2848302): ===================================================================             
QEMU (2848302): ipm_console: 'everything is awesome'                                            
QEMU (2848302): TESTSUITE test_ipm succeeded                                                    
QEMU (2848302): ===================================================================             
QEMU (2848302): PROJECT EXECUTION SUCCESSFUL                                                    
not a ztest and no state for drivers.ipc.mailbox                                                

with the fix:

QEMU (2851700): Booting from ROM..
QEMU (2851700): *** Booting Zephyr OS build v4.0.0-rc2-103-g157180d515e6 ***
QEMU (2851700): Running TESTSUITE test_ipm
QEMU (2851700): ===================================================================
QEMU (2851700): ipm_console: 'everything is awesome'
QEMU (2851700): ipm_console: 'Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor '
QEMU (2851700): ipm_console: 'incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nost'
QEMU (2851700): ipm_console: 'rud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis '
QEMU (2851700): ipm_console: 'aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugi'
QEMU (2851700): ipm_console: 'at nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culp'
QEMU (2851700): ipm_console: 'a qui officia deserunt mollit anim id est laborum.'
QEMU (2851700): TESTSUITE test_ipm succeeded
QEMU (2851700): ===================================================================
QEMU (2851700): PROJECT EXECUTION SUCCESSFUL

[gmarull]

redundant init call

[nashif]

why PRE_KERNEL_2? I would avoid this and use PRE_KERNEL_1 if possible, PRE_KERNEL_2 is something that hopefully will go away soon.

[golowanow]

why PRE_KERNEL_2?

Looking at drivers/ipm where both are used, my choice was the closest to POST_KERNEL as it was here,
although there is no visible difference when this test runs on qemu-s.

PRE_KERNEL_2 is something that hopefully will go away soon.

interesting, I didn't come across this info in the sources or docs, eg.
https://github.com/zephyrproject-rtos/zephyr/blob/main/doc/kernel/drivers/index.rst#initialization-levels

[nashif]

it is being discussed, please move this to PRE_KERNEL_1 for now.

[golowanow]

ok, changed to PRE_KERNEL_1

[nashif]

did you consider switching this to ztest instead? Parsing output like this is not great and we do it mostly for samples only.

[golowanow]

did you consider switching this to ztest instead? Parsing output like this is not great and we do it mostly for samples only.

I thought about refactoring to ztest, but considered it would be too much for a quick fix of this particular test where the console harness works well.