| commit | 837d37167dc446af8a91189108b363c04609e296 | |
| author | Markus Armbruster <armbru@redhat.com> | |
| Thu, 28 Nov 2013 16:26:55 +0000 (28 17:26 +0100) | ||
| committer | Andreas Färber <afaerber@suse.de> | |
| Sun, 22 Dec 2013 23:27:22 +0000 (23 00:27 +0100) | ||
| tree | c27d46dfca68603ff656476e139d2afc9c7ba260 | treesnapshot (tar.gz zip) |
| parent | efec3dd631d94160288392721a5f9c39e50fb2bc | commitdiff |
sysbus: Set cannot_instantiate_with_device_add_yet
device_add plugs devices into suitable bus. For "real" buses, that
actually connects the device. For sysbus, the connections need to be
made separately, and device_add can't do that. The device would be
left unconnected, and could not possibly work.
Quite a few, but not all sysbus devices already set
cannot_instantiate_with_device_add_yet in their class init function.
Set it in their abstract base's class init function
sysbus_device_class_init(), and remove the now redundant assignments
from device class init functions.
Signed-off-by: Markus Armbruster <armbru@redhat.com>
Reviewed-by: Marcel Apfelbaum <marcel.a@redhat.com>
Signed-off-by: Andreas Färber <afaerber@suse.de>
device_add plugs devices into suitable bus. For "real" buses, that
actually connects the device. For sysbus, the connections need to be
made separately, and device_add can't do that. The device would be
left unconnected, and could not possibly work.
Quite a few, but not all sysbus devices already set
cannot_instantiate_with_device_add_yet in their class init function.
Set it in their abstract base's class init function
sysbus_device_class_init(), and remove the now redundant assignments
from device class init functions.
Signed-off-by: Markus Armbruster <armbru@redhat.com>
Reviewed-by: Marcel Apfelbaum <marcel.a@redhat.com>
Signed-off-by: Andreas Färber <afaerber@suse.de>
28 files changed: