/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Chassis/ |
H A D | README.md | 1 # Chassis Power Control 5 Chassis Power Control service exposes D-Bus methods for chassis power operations 7 ### Power Button Interface 9 Power button interface `xyz.openbmc_project.Chassis.Buttons.Power` provides 14 - simPress - To emulate physical power button press. 15 - simLongPress - To emulate physical power button long press. 19 - Released - Power button released signal. 20 - Pressed - Power button pressed signal. 21 - PressedLong - Power button long pressed signal. 23 ### ID Button Interface [all …]
|
/openbmc/docs/designs/ |
H A D | multihost-phosphor-buttons.md | 1 # Multi-host front panel phosphor buttons interface 12 Phosphor buttons module has currently option to monitor gpio events of power and 13 reset buttons and trigger power event handlers. 15 phosphor-buttons currently only support push type buttons.support for different 18 additional input types in phosphor button interfaces and event handling. 21 (power and reset).There may be cases where we need to create button interface 22 which monitors non gpio events and triggers button actions for example events 27 This feature is needed to support additional phosphor button interfaces 29 available in the front panel apart from existing power and reset button 34 The front panel of bmc has buttons like power button, reset button in general [all …]
|
/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Chassis/Buttons/ |
H A D | Power.interface.yaml | 2 Power button control service 4 - name: simPress 6 Emulate power button press. 8 - xyz.openbmc_project.Chassis.Common.Error.UnsupportedCommand 9 - xyz.openbmc_project.Chassis.Common.Error.IOError 10 - name: simLongPress 12 Emulate power button long press. 14 - xyz.openbmc_project.Chassis.Common.Error.UnsupportedCommand 15 - xyz.openbmc_project.Chassis.Common.Error.IOError 18 - name: Enabled [all …]
|
/openbmc/openbmc-test-automation/gui/test/server_control/ |
H A D | test_obmc_gui_server_power_operations.robot | 3 Documentation Test OpenBMC GUI "Server power operation" sub-menu of 13 ${xpath_power_indicator_bar} //*[@id='power-indicator-bar'] 14 ${xpath_shutdown_button} //button[contains(text(), "Shut down")] 15 ${xpath_reboot_button} //button[contains(text(), "Reboot")] 16 ${xpath_power_on_button} //button[contains(text(), "Power on")] 17 ${xpath_tpm_toggle_switch} //label[@for="toggle__switch-round"] 18 ${xpath_select_boot_override} //select[@id="boot-selected"] 19 ${xpath_select_one_time_boot} //label[@id="one-time-label"] 23 Verify System State At Power Off 24 [Documentation] Verify system state at power off. [all …]
|
/openbmc/phosphor-buttons/ |
H A D | README.md | 1 # phosphor-buttons 3 Phosphor-buttons has a collection of IO event handler interfaces for physical 6 It defines an individual dbus interface object for each physical button/switch 7 inputs such as power button, reset button etc. Each button interface monitors 8 its associated IO for event changes and emits signals that the button-handler 11 ## Button Behavior 13 ### Power Button 15 All events occur when the button is released. 17 If the power is off, power on the host. 19 If the power is on, it depends on how long the press was and which options are [all …]
|
/openbmc/phosphor-buttons/inc/ |
H A D | host_then_chassis_poweroff.hpp | 11 namespace phosphor::button namespace 17 * A custom power button handler that will do the following: 19 * If power is off: 20 * - A button press will power on as long as the BMC is 23 * If power is on: 24 * - A button press less than 4s won't do anything. 25 * - At 4s, issue a host power off and start a 10s timer. 26 * - If the button is released within that 10s and not pressed 27 * again, continue with the host power off. 28 * - If the button is released within that 10s and also [all …]
|
H A D | button_handler.hpp | 16 namespace button namespace 43 * it detects button presses. 45 * There are 3 buttons supported - Power, ID, and Reset. 46 * As not all systems may implement each button, this class will 47 * check for that button on D-Bus before listening for its signals. 62 * @param[in] bus - sdbusplus connection object 68 * @brief The handler for a power button press 70 * It will do power action according to the pressing duration. 72 * @param[in] msg - sdbusplus message from signal 77 * @brief The handler for an ID button press [all …]
|
/openbmc/openbmc-test-automation/gui/data/ |
H A D | resource_variables.py | 19 xpath_submit_button = '//button[@type="submit"]' 20 xpath_button_profile_settings = '//a[@href="#/profile-settings"]' 22 xpath_button_user_action = "//button[@id='user-actions']" 23 xpath_button_logout = '//button[text()="Log out"]' 24 xpath_yes_button = "//button[text()='Yes']" 25 xpath_power_indicator = "//*[@id='power-indicator-bar']" 26 xpath_select_button_power_on = "//*[@id='power__power-on']" 27 xpath_cancel_button = "//button[contains(text(),'Cancel')]" 28 xpath_save_setting_button = "//button[contains(text(),'Save settings')]" 29 xpath_save_button = "//button[contains(text(),'Save')]" [all …]
|
H A D | gui_variables.py | 15 xpath_login_username_input = "//*[@data-test-id='login-input-username']" 16 xpath_login_password_input = "//*[@data-test-id='login-input-password']" 17 xpath_login_button = "//*[@data-test-id='login-button-submit']" 18 xpath_logout_button = "//*[@data-test-id='appHeader-link-logout']" 21 xpath_overview_menu = "//*[@data-test-id='nav-item-overview']" 24 xpath_root_button_menu = "//*[@data-test-id='appHeader-container-user']" 25 xpath_profile_settings = "//*[@data-test-id='appHeader-link-profile']" 27 "//*[@data-test-id='appHeader-container-health']" 30 "//*[@data-test-id='appHeader-container-power']" 32 xpath_refresh_button = "//*[@data-test-id='appHeader-button-refresh']" [all …]
|
/openbmc/openbmc/meta-facebook/meta-harma/recipes-phosphor/gpio/ |
H A D | phosphor-gpio-monitor_%.bbappend | 3 inherit obmc-phosphor-systemd systemd 5 SRC_URI += "file://assert-gpio-log@.service \ 6 file://assert-post-end \ 7 file://assert-post-end.service \ 8 file://assert-power-good \ 9 file://assert-power-good.service \ 10 file://assert-reset-button \ 11 file://assert-reset-button.service \ 12 file://deassert-gpio-log@.service \ 13 file://deassert-post-end \ [all …]
|
/openbmc/phosphor-buttons/src/ |
H A D | button_handler.cpp | 7 #include <phosphor-logging/lg2.hpp> 8 #include <xyz/openbmc_project/Chassis/Buttons/Power/server.hpp> 18 namespace button namespace 26 {"chassis-on", Chassis::Transition::On}, 27 {"chassis-off", Chassis::Transition::Off}, 28 {"chassis-cycle", Chassis::Transition::PowerCycle}}; 32 constexpr auto powerButtonIface = "xyz.openbmc_project.Chassis.Buttons.Power"; 40 "xyz.openbmc_project.Chassis.Buttons.Button"; 53 /* So far, there are two modes for multi-host power control in Handler() 54 - host select button mode, e.g.: Yosemite V2 in Handler() [all …]
|
H A D | host_then_chassis_poweroff.cpp | 6 #include <phosphor-logging/lg2.hpp> 10 namespace phosphor::button namespace 42 lg2::info("Power button pressed"); in pressed() 46 // If power not on - power on in pressed() 51 lg2::error("BMC not at ready state yet, cannot power on"); in pressed() 63 "Exception while processing power button press. Cannot continue"); in pressed() 67 // Power is on ... in pressed() 71 lg2::info("Starting countdown to power off"); in pressed() 77 // Button press during host off to chassis off window. in pressed() 78 // Causes a chassis power off. in pressed() [all …]
|
/openbmc/linux/drivers/input/misc/ |
H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only 21 reporting power button status. 31 reporting power button status. 40 Say Y here to use the PowerOn Key for ST-Ericsson's AB8500 41 Mix-Sig PMIC. 44 will be called ab8500-ponkey. 64 module will be called ad714x-i2c. 74 module will be called ad714x-spi. 77 tristate "Dell Wyse 3020 Power Button Driver" 81 Say Y to enable support for reporting power button status on [all …]
|
H A D | palmas-pwrbutton.c | 1 // SPDX-License-Identifier: GPL-2.0-only 3 * Texas Instruments' Palmas Power Button Input Driver 5 * Copyright (C) 2012-2014 Texas Instruments Incorporated - http://www.ti.com/ 26 * struct palmas_pwron - Palmas power on data 40 * struct palmas_pwron_config - configuration of palmas power on 42 * @pwron_debounce_val: value for debounce of power button 50 * palmas_power_button_work() - Detects the button release event 51 * @work: work item to detect button release 58 struct input_dev *input_dev = pwron->input_dev; in palmas_power_button_work() 62 error = palmas_read(pwron->palmas, PALMAS_INTERRUPT_BASE, in palmas_power_button_work() [all …]
|
/openbmc/openbmc-test-automation/gui/gui_test/operations_menu/ |
H A D | test_server_power_operations_sub_menu.robot | 3 Documentation Test OpenBMC GUI "Server power operations" sub-menu of "Operations". 8 Test Setup Run Keywords Launch Browser And Login GUI AND Navigate to Server Power Operation… 15 ${xpath_server_power_heading} //h1[text()="Server power operations"] 16 ${xpath_enable_onetime_boot_checkbox} //*[contains(@class,'custom-checkbox')] 17 ${xpath_boot_option_select} //*[@id='boot-option'] 18 ${xpath_shutdown_button} //*[@data-test-id='serverPowerOperations-button-shutDown… 19 ${xpath_reboot_button} //*[@data-test-id='serverPowerOperations-button-reboot'] 20 ${xpath_poweron_button} //*[@data-test-id='serverPowerOperations-button-powerOn'] 21 ${xpath_save_button} //button[contains(text(),'Save')] 22 ${xpath_shutdown_orderly_radio} //*[@data-test-id='serverPowerOperations-radio-shutdownO… [all …]
|
/openbmc/openbmc/meta-facebook/meta-harma/recipes-phosphor/gpio/phosphor-gpio-monitor/ |
H A D | plat-phosphor-multi-gpio-monitor.json | 3 "Name": "reset-cause-platrst", 8 "RISING": ["deassert-gpio-log@0_reset-cause-platrst.service"], 9 "FALLING": ["assert-gpio-log@0_reset-cause-platrst.service"] 14 "Name": "power-hsc-good", 20 "deassert-gpio-log@0_power-hsc-good.service", 21 "host-power-on.service", 22 "device-reinitial.service" 25 "assert-gpio-log@0_power-hsc-good.service", 26 "host-power-off.service" 32 "Name": "power-button", [all …]
|
/openbmc/openbmc-test-automation/gui/gui_test/overview_menu/ |
H A D | test_overview_menu.robot | 27 ${xpath_launch_host_console} //*[@data-test-id='overviewQuickLinks-button-solCo… 28 ${xpath_led_button} //*[@data-test-id='overviewInventory-checkbox-iden… 30 ${xpath_critical_logs_count} //dt[contains(text(),'Critical')]/following-siblin… 31 ${xpath_warning_logs_count} //dt[contains(text(),'Warning')]/following-sibling… 32 ${xpath_asset_tag} //dt[contains(text(),'Asset tag')]/following-sibli… 33 ${xpath_operating_mode} //dt[contains(text(),'Operating mode')]/following-… 34 ${xpath_machine_model} //dt[contains(text(),'Model')]/following-sibling::… 35 ${xpath_serial_number} //dt[contains(text(),'Serial number')]/following-s… 47 Page Should Contain Power information 96 Verify Edit Network Setting Button [all …]
|
/openbmc/linux/Documentation/devicetree/bindings/input/ |
H A D | ti,palmas-pwrbutton.txt | 1 Texas Instruments Palmas family power button module 7 This module provides a simple power button event via an Interrupt. 10 - compatible: should be one of the following 11 - "ti,palmas-pwrbutton": For Palmas compatible power on button 12 - interrupts: Interrupt number of power button submodule on device. 16 - ti,palmas-long-press-seconds: Duration in seconds which the power 17 button should be kept pressed for Palmas to power off automatically. 20 - ti,palmas-pwron-debounce-milli-seconds: Duration in milliseconds 21 which the power button should be kept pressed for Palmas to register 29 compatible = "ti,palmas-pwrbutton"; [all …]
|
/openbmc/openbmc/meta-hpe/meta-rl300-g11/recipes-hpe/power-sequencing/ |
H A D | power-sequencing.bb | 1 inherit obmc-phosphor-systemd 2 SUMMARY = "Power Sequencing for HPE RL300 Gen11" 4 SYSTEMD_SERVICE:${PN} = "monitor-ipmi-power-transition.service power-sequencing.service gpiosdown.s… 5 …-ipmi-power-transition.service file://ipmi-power-button-monitoring.sh file://rl300Start.sh file://… 7 LICENSE = "Apache-2.0" 8 LIC_FILES_CHKSUM = "file://${COREBASE}/meta/files/common-licenses/Apache-2.0;md5=89aea4e17d99a7cacd… 11 IMAGE_INSTALL += "power-sequencing " 16 install -d ${D}${sysconfdir}/system/ 17 install -d ${D}/usr/share/gpios 18 install -d ${D}/usr/bin [all …]
|
/openbmc/openbmc/meta-hpe/meta-dl360-g11/recipes-hpe/power-sequencing/ |
H A D | power-sequencing.bb | 1 inherit obmc-phosphor-systemd 2 SUMMARY = "Power Sequencing for HPE DL360 Gen11" 4 SYSTEMD_SERVICE:${PN} = "monitor-ipmi-power-transition.service power-sequencing.service gpiosdown.s… 5 …-ipmi-power-transition.service file://ipmi-power-button-monitoring.sh file://dl360Start.sh file://… 7 LICENSE = "Apache-2.0" 8 LIC_FILES_CHKSUM = "file://${COREBASE}/meta/files/common-licenses/Apache-2.0;md5=89aea4e17d99a7cacd… 11 IMAGE_INSTALL += "power-sequencing " 16 install -d ${D}${sysconfdir}/system/ 17 install -d ${D}/usr/share/gpios 18 install -d ${D}/usr/bin [all …]
|
/openbmc/linux/Documentation/input/devices/ |
H A D | joystick-parport.rst | 3 .. _joystick-parport: 9 :Copyright: |copy| 1998-2000 Vojtech Pavlik <vojtech@ucw.cz> 10 :Copyright: |copy| 1998 Andree Borrmann <a.borrmann@tu-bs.de> 18 Any information in this file is provided as-is, without any guarantee that 36 Many console and 8-bit computer gamepads and joysticks are supported. The 40 ------------ 57 The main problem with PC parallel ports is that they don't have +5V power 58 source on any of their pins. So, if you want a reliable source of power 59 for your pads, use either keyboard or joystick port, and make a pass-through 60 cable. You can also pull the power directly from the power supply (the red [all …]
|
/openbmc/phosphor-webui/app/server-control/controllers/ |
H A D | power-usage-controller.html | 2 <div id="power-usage" class="page"> 3 <h1 class="page-title">Manage Power Usage</h1> 4 <form class="power-usage__form" role="form" action=""> 6 <div class="section-header"> 7 <h2 class="section-title">Power information</h2> 9 <dl class="list-pair"> 10 <dt>Power Consumption</dt> 15 <div class="section-header"> 16 <h2 class="section-title"> 17 Server power cap setting [all …]
|
H A D | power-operations-controller.html | 2 <div id="power-operations" class="power-operations"> 4 <h1>Server power operations</h1> 5 <div class="power__current-status page-header"> 7 <div class="power__status-log inline float-right"> 8 Last power operation at 9 <span class="courier-bold">{{ powerTime | localeDate }}</span> 13 <!-- Power Indicator Bar --> 15 <div id="power-indicator-bar" class="power__indicator-bar" 16 ng-class="{'power__state-on': dataService.server_state == 'Running', 17 'power__state-off': dataService.server_state == 'Off', [all …]
|
/openbmc/openbmc-test-automation/gui/test/gui_header/ |
H A D | test_obmc_gui_ip_refresh_check.robot | 14 ${xpath_bmc_ip} //*[contains(@class, "header__server-ip")] 21 Verify Server Power Button 22 [Documentation] Verify server power page on clicking server power button. 27 Wait Until Page Contains Server power operations 29 Verify Server Health Button 30 [Documentation] Verify server health page on clicking server health button. 46 Verify Refresh Button 47 [Documentation] Verify Refresh Button in GUI header. 50 # Verify power is on after refresh button. 55 GUI Power On [all …]
|
/openbmc/openbmc-test-automation/gui/lib/ |
H A D | resource.robot | 3 ... user-defined keywords which are available to all gui modules 88 # (e.g. https://openbmc-test.mybluemix.net/#/login). 143 ... Run Keywords Power On OpenBMC AND 146 ... Run Keywords Redfish.Login AND Redfish Power Off AND Redfish.Logout 149 Power On OpenBMC 150 [Documentation] Power on the OBMC system. 152 Log To Console Power On OpenBMC... 154 Click Button ${xpath_select_button_power_on } 162 Click Button ${xpath_select_button_orderly_shutdown} 163 Click Yes Button ${xpath_select_button_orderly_shutdown_yes} [all …]
|