drivers: staging: unisys: add MODULE_DEVICE_TABLE and temporary MODULE_ALIAS lines to visornic
This patch adds an module alias and a MODULE_DEVICE_TABLE to autoload the visornic driver when an appropriate device is created by the visorbus. Note, the correct way of fixing this is adding functionality to scripts/mod/file2alias.c for the visorbus bus type. Signed-off-by: Prarit Bhargava <prarit@redhat.com> Signed-off-by: Benjamin Romer <benjamin.romer@unisys.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
This commit is contained in:
parent
beb1216708
commit
110a66be3a
|
@ -71,6 +71,15 @@ static struct visor_channeltype_descriptor visornic_channel_types[] = {
|
|||
{ SPAR_VNIC_CHANNEL_PROTOCOL_UUID, "ultravnic" },
|
||||
{ NULL_UUID_LE, NULL }
|
||||
};
|
||||
MODULE_DEVICE_TABLE(visorbus, visornic_channel_types);
|
||||
/*
|
||||
* FIXME XXX: This next line of code must be fixed and removed before
|
||||
* acceptance into the 'normal' part of the kernel. It is only here as a place
|
||||
* holder to get module autoloading functionality working for visorbus. Code
|
||||
* must be added to scripts/mode/file2alias.c, etc., to get this working
|
||||
* properly.
|
||||
*/
|
||||
MODULE_ALIAS("visorbus:" SPAR_VNIC_CHANNEL_PROTOCOL_UUID_STR);
|
||||
|
||||
/* This is used to tell the visor bus driver which types of visor devices
|
||||
* we support, and what functions to call when a visor device that we support
|
||||
|
|
Loading…
Reference in a new issue