linux/arch/sparc/crypto/crop_devid.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);
sparc64: Add auto-loading mechanism to crypto-opcode drivers. 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> 2012-09-16 00:46:25 +08:00			`#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);`