conf.d: add *_ARCH keys for legacy targets and extend schema

[quic-vkatoch]

Legacy targets (db820c, db845c, qcs615-ride) do not implement the ARCH_VER capability on the DSP, so fastrpc cannot auto-detect the Hexagon version at runtime. This adds explicit *_ARCH keys in the per-machine YAML configs so fastrpc can resolve the correct DSP library search path (e.g. /usr/share/qcom/hexagon/v<XY>/).

YAML changes:

• db410c: ADSP_ARCH=v5
• db820c: ADSP_ARCH=v60, SDSP_ARCH=v60
• db845c: ADSP_ARCH=v65, CDSP_ARCH=v65, SDSP_ARCH=v65
• qcs615-ride: ADSP_ARCH=v66, CDSP_ARCH=v66

Schema changes (conf.d/schema.json):

• Register all *_ARCH keys as optional properties: ADSP_ARCH, MDSP_ARCH, SDSP_ARCH, CDSP_ARCH
• Pattern ^v[0-9a-f]+$ allows hex-digit version strings (e.g. v60, v65, v6a)

Depends on qualcomm/fastrpc#328

[lumag]

Does RB5 (SM8250) implement ARCH_VER?
How do we handle db410c (MSM8916)? Do we need to add an empty dir for the sake of ARCH_VER configuration?

Also, please split this into sepate, logical commits.

[quic-vkatoch]

Does RB5 (SM8250) implement ARCH_VER?

Yes

How do we handle db410c (MSM8916)? Do we need to add an empty dir for the sake of ARCH_VER configuration?

FastRPC lib gracefully handles cases where ARCH_VER capability is not supported by either falling back to yaml configuration or returning meaningful error code. However, how do you expect us to handle targets that are not enabled in the hexagon-dsp-binaries project?

Also, please split this into sepate, logical commits.

Sure

[lumag]

However, how do you expect us to handle targets that are not enabled in the hexagon-dsp-binaries project?

That's what I've asked. Do we need to add a config file for it just to let FastRPC library resolve Hexagon arch on that platform?

[quic-vkatoch]

However, how do you expect us to handle targets that are not enabled in the hexagon-dsp-binaries project?

That's what I've asked. Do we need to add a config file for it just to let FastRPC library resolve Hexagon arch on that platform?

Yes, we can do that adding a config file for the target should allow the library to correctly resolve the Hexagon arch path. I'll update the PR, let me know if it looks correct.

[lumag]

Also please explain, why we are shipping this config file, but not the actual binaries

[quic-vkatoch]

Also please explain, why we are shipping this config file, but not the actual binaries

@vkasinat, @quic-psaddam, could you please comment on whether we have binaries for db410c? If not, we can drop the config file.

[vkasinat]

@quic-vkatoch there are no binaries for db410c.

[lumag]

Is it just v5, without any v51 or v55?

[lumag]

@quic-vkatoch there are no binaries for db410c.

I can see FastCV and other DSP binaries going back to msm8974. If there were no separate fastrpc_shell and other system libs, then we need to provide a conf file here to let users load those DSP libs.