dcdbas.txt 3.6 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273747576777879808182838485868788899091
  1. Overview
  2. The Dell Systems Management Base Driver provides a sysfs interface for
  3. systems management software such as Dell OpenManage to perform system
  4. management interrupts and host control actions (system power cycle or
  5. power off after OS shutdown) on certain Dell systems.
  6. Dell OpenManage requires this driver on the following Dell PowerEdge systems:
  7. 300, 1300, 1400, 400SC, 500SC, 1500SC, 1550, 600SC, 1600SC, 650, 1655MC,
  8. 700, and 750. Other Dell software such as the open source libsmbios project
  9. is expected to make use of this driver, and it may include the use of this
  10. driver on other Dell systems.
  11. The Dell libsmbios project aims towards providing access to as much BIOS
  12. information as possible. See http://linux.dell.com/libsmbios/main/ for
  13. more information about the libsmbios project.
  14. System Management Interrupt
  15. On some Dell systems, systems management software must access certain
  16. management information via a system management interrupt (SMI). The SMI data
  17. buffer must reside in 32-bit address space, and the physical address of the
  18. buffer is required for the SMI. The driver maintains the memory required for
  19. the SMI and provides a way for the application to generate the SMI.
  20. The driver creates the following sysfs entries for systems management
  21. software to perform these system management interrupts:
  22. /sys/devices/platform/dcdbas/smi_data
  23. /sys/devices/platform/dcdbas/smi_data_buf_phys_addr
  24. /sys/devices/platform/dcdbas/smi_data_buf_size
  25. /sys/devices/platform/dcdbas/smi_request
  26. Systems management software must perform the following steps to execute
  27. a SMI using this driver:
  28. 1) Lock smi_data.
  29. 2) Write system management command to smi_data.
  30. 3) Write "1" to smi_request to generate a calling interface SMI or
  31. "2" to generate a raw SMI.
  32. 4) Read system management command response from smi_data.
  33. 5) Unlock smi_data.
  34. Host Control Action
  35. Dell OpenManage supports a host control feature that allows the administrator
  36. to perform a power cycle or power off of the system after the OS has finished
  37. shutting down. On some Dell systems, this host control feature requires that
  38. a driver perform a SMI after the OS has finished shutting down.
  39. The driver creates the following sysfs entries for systems management software
  40. to schedule the driver to perform a power cycle or power off host control
  41. action after the system has finished shutting down:
  42. /sys/devices/platform/dcdbas/host_control_action
  43. /sys/devices/platform/dcdbas/host_control_smi_type
  44. /sys/devices/platform/dcdbas/host_control_on_shutdown
  45. Dell OpenManage performs the following steps to execute a power cycle or
  46. power off host control action using this driver:
  47. 1) Write host control action to be performed to host_control_action.
  48. 2) Write type of SMI that driver needs to perform to host_control_smi_type.
  49. 3) Write "1" to host_control_on_shutdown to enable host control action.
  50. 4) Initiate OS shutdown.
  51. (Driver will perform host control SMI when it is notified that the OS
  52. has finished shutting down.)
  53. Host Control SMI Type
  54. The following table shows the value to write to host_control_smi_type to
  55. perform a power cycle or power off host control action:
  56. PowerEdge System Host Control SMI Type
  57. ---------------- ---------------------
  58. 300 HC_SMITYPE_TYPE1
  59. 1300 HC_SMITYPE_TYPE1
  60. 1400 HC_SMITYPE_TYPE2
  61. 500SC HC_SMITYPE_TYPE2
  62. 1500SC HC_SMITYPE_TYPE2
  63. 1550 HC_SMITYPE_TYPE2
  64. 600SC HC_SMITYPE_TYPE2
  65. 1600SC HC_SMITYPE_TYPE2
  66. 650 HC_SMITYPE_TYPE2
  67. 1655MC HC_SMITYPE_TYPE2
  68. 700 HC_SMITYPE_TYPE3
  69. 750 HC_SMITYPE_TYPE3