LX2160A SEC version / backward compatibility

[dmitri_lechtchinski]

Hello,

In T2080 reference manual I can see that SEC version is 5.2, however I can't find this information for LX2160A.

1. What is the version of SEC in LX2160A?
2. Should a SEC driver working on T2080 be compatible with LX2160A, assuming it uses only the job ring interface and some minimal SEC registers accesses?
3. Same question as 2 for RTIC functionality

Thanks,
Dmitri

[bpe]

What is the version of SEC in LX2160A?

SEC 7

Should a SEC driver working on T2080 be compatible with LX2160A, assuming it
uses only the job ring interface and some minimal SEC registers accesses?
Same question as 2 for RTIC functionality

T2080 and LX2160A have different GPP core architectures. There is no binary
compatibility between them. Everything else depends on the driver design.
There is a single CAAM driver for PowerPC and ARM based SoCs in Linux. Customers
designing a platform-independent code for SEC are advised to re-use Linux CAAM
driver as much as possible.

Best Regards,
Platon

[dmitri_lechtchinski]

Thanks Platon,

The question was more regarding registers interface compatibility (not binary compatibility):

Are the registers blocks for job ring interface and for RTIC remain the same between T2080 and LX2160A so that code which operates both can be considered "similar"?

Does the CAAM driver you mentioned implements interfaces to both these blocks?

[bpe · Accepted solution]

Well, you are trying to compare processors built around totally different
cores and having several SEC generations between them. If you want a document
that would give you a summary of their differences, none exists.
SECs on T2080 and LX2160 are different, including the programming model.
For RTIC, it is not covered by Linux driver, but it is not
a very much sophisticated module, so it should not be too difficult to compare
the egister descriptions directly, based on their respective
Manuals, especially if your application utilizes a small subset of their
functions. For the rest, you can refer to the Linux driver code.

Best Regards,
Platon