[U-Boot] [PATCH 1/2] SECURE BOOT: add version info for ISBC

[aneesh.bansal at freescale.com]

>>
>> >               CONFIG_SYS_FSL_SINGLE_SOURCE_CLK
>> >               Single Source Clock is clocking mode present in some of FSL SoC's.
>> >               In this mode, a single differential clock is used to supply
>>
>> You already have all relevant information present in the current
>> configuration.  There is no need to add yet another CONFIG_SYS_
>> option; the information can easily be derived from the existing data.
>...
>
>> ISBC (Internal Secure Boot Code) is an IP which has different versions on different SOC's. >The major difference which this CONFIG represents is whether CAAM block is being used >for cryptographic operations or not. I will be adding more details in the de
>> scription IN README and resend the patch.
>>
>> The only other way that this can be derived is by doing SoC specific checking which >would become a little messy.
>
>But this is what I had in mind.  It appears to be a simple 1:1 mapping
>from SoC to ISBC version to me, or am I wrong here?
>
>Best regards,
>
>Wolfgang Denk
>
>--
>DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
>HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
>Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
>When the ax entered the forest, the trees said, "The handle is one of
>us!"                                               -- Turkish proverb

Yes, it is a 1:1 mapping from SoC to ISBC version but we have multiple SoC's having the same ISBC version. So using the SoC names would result in having a long list of SoC's wherever we are doing some stuff specific to the ISBC version.
Also in future, we might have new versions of ISBC with more features.
SO having multiple SoC specific checks inside the code would lead to confusion.

Regards,
Aneesh Bansal