mirror of
https://github.com/edk2-porting/linux-next.git
synced 2024-12-19 18:53:52 +08:00
979e93ca24
Just simply provide a device table containing an entry for sun4v cpus, the capability mask checks in the drivers themselves will take care of the rest. This makes the bootup logs on pre-T4 cpus slightly more verbose, with each driver indicating lack of support for the associated opcode(s). But this isn't too much of a real problem. I toyed with the idea of using explicit entries with compatability fields of "SPARC-T4", "SPARC-T5", etc. but all future cpus will have some subset of these opcodes available and this would just be one more pointless thing to do as each new cpu is released with a new string. Signed-off-by: David S. Miller <davem@davemloft.net>
15 lines
487 B
C
15 lines
487 B
C
#include <linux/module.h>
|
|
#include <linux/of_device.h>
|
|
|
|
/* This is a dummy device table linked into all of the crypto
|
|
* opcode drivers. It serves to trigger the module autoloading
|
|
* mechanisms in userspace which scan the OF device tree and
|
|
* load any modules which have device table entries that
|
|
* match OF device nodes.
|
|
*/
|
|
static const struct of_device_id crypto_opcode_match[] = {
|
|
{ .name = "cpu", .compatible = "sun4v", },
|
|
{},
|
|
};
|
|
MODULE_DEVICE_TABLE(of, crypto_opcode_match);
|