Method for creation of device drivers and device objects for peripheral devices

• US 8,825,911 B1
• Filed: 10/02/2013
• Issued: 09/02/2014
• Est. Priority Date: 02/24/2010
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: Open Invention Network LLC
• Inventors: Wieland, Martin
• Primary Examiner(s): Mamo, Elias
• Application Number:
  US14/044,086
• Time in Patent Office: 335 Days
• Field of Search: None
• US Class Current: 710/8
• CPC Class Codes: G06F 13/102 where the programme performs an interfacing function, e.g. device driver G06F13/105 takes precedence; scheduling within device drivers G06F9/52; contention policies within device drivers G06F9/4881
• CPC Class Codes: G06F 13/105 where the programme performs an input/output emulation function
• CPC Class Codes: G06F 13/36 for access to common bus or bus system
• CPC Class Codes: G06F 13/385 for adaptation of a particular data processing system to different peripheral devices
• CPC Class Codes: G06F 13/4282 on a serial bus, e.g. I2C bus, SPI bus on daisy chain buses G06F13/4247
• CPC Class Codes: G06F 9/4411 Configuring for operating with peripheral devices; Loading of device drivers
• CPC Class Codes: G06F 9/4413 Plug-and-play [PnP]
• CPC Class Codes: G06F 9/44505 Configuring for program initiating, e.g. using registry, configuration files

Abstract

All steps required to create and operate a peripheral device of an electronic device can be performed without the need to plug in the peripheral device to the electronic device. Setup information for a peripheral device is extracted, modified and stored to fit to a physical existent peripheral device. The modified setup information is used to create a data structure that is passed to the peripheral bus driver. As the data structure contains a hot plug notification the reception causes the peripheral bus driver to initiate the setup process for the peripheral device. As the data structure is built from setup information that is available at the electronic device no additional user action is required. The invention also allows the creation of a device object for existing signed driver packets that may not be altered.

Claims

1. A method, comprising:

creating a data structure from existent setup information;

replacing a device identification (ID) in the data structure with a device ID of a peripheral device;

passing a request to a device driver of an interface of the peripheral device and a bus that initiates the installation of the peripheral device, wherein the peripheral device is not connected to the electronic device, wherein the request comprises a request to add the peripheral device, a class identifier of the peripheral device and the device ID of the peripheral device which cause a bus driver of the bus to receive the request and determine a new device is operating on the bus as a Plug and Play device; and

adding entries to provide Plug and Play functionality to the data structure generated from an existent setup information file that does not provide such functionality.

2. The method of claim 1, wherein a previously existent setup information is stored in a file.

3. The method of claim 1, wherein existent setup information is stored in a configuration memory of the electronic device.

4. The method of claim 1, further comprising storing the device ID of the peripheral device.

5. The method of claim 1, further comprising passing an instance ID to the driver of the peripheral interface or bus to identify an instance of the peripheral device.

6. The method according to claim 1, wherein the bus is an expansion bus.

7. The method according to claim 1, wherein the bus is a peripheral bus.

8. The method of claim 1, wherein the peripheral device supports the functionality of multiple devices and the operations of creation of setup information, initialization and performance of an installation are performed for each supported functionality of the multiple devices.

18. The method of claim 1, further comprising creating a device object of the electronic device and binding the device object to the peripheral device to provide a signed driver that is used during the installation of the peripheral device.

9. An apparatus, comprising:

a memory; and

a processor communicably coupled to the memory, the processor configured to;

create a data structure from existent setup information,

replace a device identification (ID) in the data structure with a device ID of a peripheral device;

pass a request to a device driver of an interface of the peripheral device and a bus that initiates the installation of the peripheral device, wherein the peripheral device is not connected to the apparatus, wherein the request comprises a request to add the peripheral device, a class identifier of the peripheral device and the device ID of the peripheral device which cause a bus driver of the bus to receive the request and determine a new device is operating on the bus as a Plug and Play device; and

add entries to provide Plug and Play functionality to the data structure generated from an existent setup information file that does not provide such functionality.

10. The apparatus of claim 9, wherein a previously existent setup information is stored in a file.

11. The apparatus of claim 9, wherein existent setup information is stored in a configuration memory of the apparatus.

12. The apparatus of claim 9, wherein the processor is further configured to pass an instance ID to the driver of the peripheral interface to identify an instance of the peripheral device.

13. The apparatus of claim 9, wherein the processor is further configured to pass an instance ID to the driver of the bus to identify an instance of the peripheral device.

14. The apparatus of claim 9, wherein the bus is an expansion bus.

15. The apparatus of claim 9, wherein the bus is a peripheral bus.

16. The apparatus of claim 9, wherein the peripheral device supports the functionality of multiple devices and the operations of creation of setup information, initialization and performance of an installation are performed for each supported functionality of the multiple devices.

19. The apparatus of claim 9, wherein the processor is further configured to create a device object of the apparatus and bind the device object to the peripheral device to provide a signed driver that is used during the installation of the peripheral device.

17. A non-transitory computer readable medium comprising a computer program that when executed causes a processor to perform:

creating a data structure from existent setup information;

replacing a device identification (ID) in the data structure with a device ID of a peripheral device;

passing a request to at least one of a device driver of an interface of the peripheral device and a bus that initiates the installation of the peripheral device, wherein the peripheral device is not connected to the electronic device, wherein the request comprises a request to add the peripheral device, a class identifier of the peripheral device and the device ID of the peripheral device which cause a bus driver of the bus to receive the request and determine a new device is operating on the bus as a Plug and Play device; and

adding entries to provide Plug and Play functionality to the data structure generated from an existent setup information file that does not provide such functionality.

20. The non-transitory computer readable medium of claim 17, wherein the processor is further configured to perform creating a device object of the electronic device and binding the device object to the peripheral device to provide a signed driver that is used during the installation of the peripheral device.