Lines Matching full:driver
5 to the driver entity. This protocol is mandatory for IDE controllers if the
6 IDE devices behind the controller are to be enumerated by a driver entity.
10 IDE controller. A driver entity that wishes to manage an IDE bus and possibly
48 /// The driver entity is about to begin enumerating the devices
54 /// The driver entity has completed enumerating the devices
60 /// The driver entity is about to reset the devices behind the
66 /// The driver entity has completed resetting the devices behind
72 /// The driver entity is about to detect the presence of devices
79 /// The driver entity is done with detecting the presence of
85 /// The IDE bus is requesting the IDE controller driver to
237 The driver entity uses this information during the enumeration process.
239 If Enabled is set to FALSE, the driver entity will not scan the channel. Note
240 that it will not prevent an operating system driver from scanning the channel.
249 bus driver is required to scan for the presence of port multipliers behind an SATA
259 @param[out] MaxDevices The maximum number of IDE devices that the bus driver
279 The notifications from the driver entity that it is about to enter a certain
282 This function can be used to notify the IDE controller driver to perform
311 Submits the device information to the IDE controller driver.
313 This function is used by the driver entity to pass detailed information about
314 a particular device to the IDE controller driver. The driver entity obtains
317 by the driver entity, and the IDE controller driver must make a local copy
324 The IDE controller driver may consult various fields of EFI_IDENTIFY_DATA to
326 timing information. For example, an implementation of the IDE controller driver
329 The driver entity may submit drive information in any order, as long as it
333 should be called with IdentifyData set to NULL. The IDE controller driver may
361 This function allows the driver entity or other drivers (such as platform
362 drivers) to reject certain timing modes and request the IDE controller driver
363 to recalculate modes. This function allows the driver entity and the IDE
364 controller driver to negotiate the timings on a per-device basis. This function
367 by the IDE controller driver based on the response to the Identify Drive command.
369 If the driver entity does not want to limit the ATA timing modes and leave that
370 decision to the IDE controller driver, it can either not call this function for
374 The driver entity may disqualify modes for a device in any order and any number
382 a higher transfer rate mode on a given channel. For example, a platform driver
383 may inform the IDE controller driver to not use second-generation (Gen2) speeds
410 This function is used by the driver entity to obtain the optimum ATA modes for
411 a specific device. The IDE controller driver takes into account the following
416 The driver entity is required to call EFI_IDE_CONTROLLER_INIT_PROTOCOL.SubmitData()
420 The IDE controller driver will use controller- and possibly platform-specific
423 may be called multiple times because the driver entity may renegotiate the mode
424 with the IDE controller driver using EFI_IDE_CONTROLLER_INIT_PROTOCOL.DisqualifyMode().
426 The driver entity may collect timing information for various devices in any
427 order. The driver entity is responsible for making sure that all the dependencies
438 The IDE controller driver for a Serial ATA (SATA) controller can use this
440 second-generation [Gen2]-capable hardware). The IDE controller driver can
441 also allow the driver entity to stay with the speed that has been negotiated
471 Commands the IDE controller driver to program the IDE controller hardware
474 This function is used by the driver entity to instruct the IDE controller
475 driver to program the IDE controller hardware to the specified modes. This
490 The driver entity should not use this device.
512 /// The notification that the driver entity is about to enter the