Re: [PATCH v3 0/1] Add support for custom compatible string via optional parameter

["Kavinaya S" <kavinaya@qti.qualcomm.com>]

Hi Ricardo,

I’ve implemented this change by adding a custom compatible string for one specific DTB in my machine.conf:
FIT_DTB_COMPATIBLE_OVERRIDE:qcs6490-rb3gen2-vision-mezzanine.dtb = "qcom,qcs6490-rb-subtype5"

For qcs6490-rb3gen2.dtb, I have not defined any override, so it continues to use the compatible string extracted from the DTB itself.
As a result, the ITS configuration section looks like this:
configurations {
    default = "conf-qcs6490-rb3gen2.dtb";
    conf-qcs6490-rb3gen2.dtb {
        description = "1 Linux kernel, FDT blob";
        kernel = "kernel-1";
        fdt = "fdt-qcs6490-rb3gen2.dtb";
        compatible = "qcom,qcs6490-rb3gen2", "qcom,qcm6490";
        hash-1 {
            algo = "sha256";
        };
    };

    conf-qcs6490-rb3gen2-vision-mezzanine.dtb {
        description = "0 Linux kernel, FDT blob";
        kernel = "kernel-1";
        fdt = "fdt-qcs6490-rb3gen2-vision-mezzanine.dtb";
        compatible = "qcom,qcs6490-rb-subtype5";
        hash-1 {
            algo = "sha256";
        };
    };
}

This demonstrates how the override works:

If an override is defined in machine.conf, the FIT generator uses that value.
If no override is provided, it falls back to the compatible string from the DTB.

Thanks,
Kavinaya