[PATCH v1 3/3] KEYS: trusted: Introduce support for NXP CAAM-based trusted keys
richard at nod.at
Wed Mar 17 08:07:39 UTC 2021
----- Ursprüngliche Mail -----
>> > module_param_named(source, trusted_key_source, charp, 0);
>> > -MODULE_PARM_DESC(source, "Select trusted keys source (tpm or tee)");
>> > +MODULE_PARM_DESC(source, "Select trusted keys source (tpm, tee or caam)");
>> I didn't closely follow the previous discussions, but is a module
>> parameter really the right approach?
>> Is there also a way to set it via something like device tree?
> It's there to support a platform which possesses multiple trusted keys
> backends. So that a user is able to select during boot which one to
> use as a backend.
I understand the use case, my question was whether it makes actually sense to
have a module parameter for it, or additionally another way to define the
More information about the Linux-security-module-archive