ipc3: helper: Do not silently accept unrecognized component type in IPC

[jsarha]

Return an error code from comp_specific_builder() if the component type is not recognized, instead of just silently ignoring the error.

[lgirdwood]

@wszypelt@lrudyX not expecting ipc3 fix to fail, good to merge ?

[lrudyX]

@wszypelt@lrudyX not expecting ipc3 fix to fail, good to merge ?

There was a problem with CI, several PRs are waiting for rerun.

[dbaluta]

@jsarha we get some problems with this patch when testing mixer on IPC3.

Looks like there is no case for mixer and it goes on default -EINVAL value. Please see comp_specific_builder.

We get this error:

[ 10468552.448600] ( 10468552.000000) c0 dma-trace src/trace/dma-trace.c:664 ERROR dtrace_add_event(): number of dropped logs = 13
[ 10495936.249596] ( 27383.800781) c0 dma-trace src/ipc/ipc3/helper.c:333 ERROR comp_new(): component type not recognized
[ 10496074.582923] ( 138.333328) c0 dma-trace src/ipc/ipc3/helper.c:660 ERROR ipc_comp_new(): component cd = NULL
[ 10496211.666251] ( 137.083328) c0 dma-trace src/ipc/ipc3/handler.c:1301 ERROR ipc: pipe 1 comp 0 creation failed -22

[lyakh]

@jsarha we get some problems with this patch when testing mixer on IPC3.

Looks like there is no case for mixer and it goes on default -EINVAL value. Please see comp_specific_builder.

@dbaluta would someone be submitting a PR to fix this?

[dbaluta]

@lyakh I am looking at this.

[dbaluta]

@lyakh sent this for review #7963