B12.1.2.1 SEE related industry standards for each device class implemented on the multi-function device
See B1.0 and B2.0.
WHQL Test Specification References:
Chapter 1: Introduction to HCT Test Specifications
Chapter 22: Driver Quality Test Specification
Plus technology-specific test specifications
B12.1.3.1 - B12.1.3.4 SEE B12.1.4.2
See B1.3.
Windows XP: See “Multifunction” in the HCT documentation.
B12.1.4 Multifunction Devices - Windows Experience
Design Guideline References:
PC 2001 System Design Guide: SYS-0032
Hardware Design Guide 3.0 for Windows 2000 Server, Chapter 3
B12.1.4.1 Separate drivers are required for separate functions with no start order dependencies between separate function drivers
[SYS-0032; SDG3:13]
The operating system must be able to configure and manage functions in any order, so no function on a multifunction device can depend on another function to be started before the function can be started by the operating system.
B12.1.4.2 MFP devices correctly implement driver and Plug and Play support
[SYS-0032]
-
Functional units on a multifunction device do not have start-order dependencies.
-
Resource requirements of one functional unit are not expressed in terms of another functional unit.
-
Operation of one functional unit do not affect or interfere with the operation of another functional unit on the multifunction device or on the system as a whole.
-
Each functional unit is enumerated and its resource requirements communicated to the operating system, so Windows can load the necessary drivers and assign resources to the different units in any order.
B12.1.4.3 Each independent function can be used concurrently, with no hidden dependencies
[SYS-0032]
Separate functional units must be able to operate concurrently, without interfering with each other or with other devices on the system.
B12.1.4.4 Each function can be power managed independently
[SYS-0032]
Each functional unit in a multifunction device must separately meet the power management device class specifications for its device class and be independently power managed. Each functional unit must be able to successfully complete a system sleep/wake transition (where the unit transitions from D0 to D3 to D0) without losing functionality and without requiring user intervention to restore functionality. All functional units on PCI devices that support wakeup capabilities must correctly support wake from D3cold.
|
