~ [ source navigation ] ~ [ diff markup ] ~ [ identifier search ] ~

TOMOYO Linux Cross Reference
Linux/Documentation/userspace-api/dcdbas.rst

Version: ~ [ linux-6.12-rc7 ] ~ [ linux-6.11.7 ] ~ [ linux-6.10.14 ] ~ [ linux-6.9.12 ] ~ [ linux-6.8.12 ] ~ [ linux-6.7.12 ] ~ [ linux-6.6.60 ] ~ [ linux-6.5.13 ] ~ [ linux-6.4.16 ] ~ [ linux-6.3.13 ] ~ [ linux-6.2.16 ] ~ [ linux-6.1.116 ] ~ [ linux-6.0.19 ] ~ [ linux-5.19.17 ] ~ [ linux-5.18.19 ] ~ [ linux-5.17.15 ] ~ [ linux-5.16.20 ] ~ [ linux-5.15.171 ] ~ [ linux-5.14.21 ] ~ [ linux-5.13.19 ] ~ [ linux-5.12.19 ] ~ [ linux-5.11.22 ] ~ [ linux-5.10.229 ] ~ [ linux-5.9.16 ] ~ [ linux-5.8.18 ] ~ [ linux-5.7.19 ] ~ [ linux-5.6.19 ] ~ [ linux-5.5.19 ] ~ [ linux-5.4.285 ] ~ [ linux-5.3.18 ] ~ [ linux-5.2.21 ] ~ [ linux-5.1.21 ] ~ [ linux-5.0.21 ] ~ [ linux-4.20.17 ] ~ [ linux-4.19.323 ] ~ [ linux-4.18.20 ] ~ [ linux-4.17.19 ] ~ [ linux-4.16.18 ] ~ [ linux-4.15.18 ] ~ [ linux-4.14.336 ] ~ [ linux-4.13.16 ] ~ [ linux-4.12.14 ] ~ [ linux-4.11.12 ] ~ [ linux-4.10.17 ] ~ [ linux-4.9.337 ] ~ [ linux-4.4.302 ] ~ [ linux-3.10.108 ] ~ [ linux-2.6.32.71 ] ~ [ linux-2.6.0 ] ~ [ linux-2.4.37.11 ] ~ [ unix-v6-master ] ~ [ ccs-tools-1.8.12 ] ~ [ policy-sample ] ~
Architecture: ~ [ i386 ] ~ [ alpha ] ~ [ m68k ] ~ [ mips ] ~ [ ppc ] ~ [ sparc ] ~ [ sparc64 ] ~

Diff markup

Differences between /Documentation/userspace-api/dcdbas.rst (Architecture alpha) and /Documentation/userspace-api/dcdbas.rst (Architecture ppc)


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

~ [ source navigation ] ~ [ diff markup ] ~ [ identifier search ] ~

kernel.org | git.kernel.org | LWN.net | Project Home | SVN repository | Mail admin

Linux® is a registered trademark of Linus Torvalds in the United States and other countries.
TOMOYO® is a registered trademark of NTT DATA CORPORATION.

sflogo.php