Received: by 10.223.185.116 with SMTP id b49csp1651678wrg; Sat, 24 Feb 2018 01:07:53 -0800 (PST) X-Google-Smtp-Source: AH8x2266nmQuaZoZUfWXXe9l1EjfQFAA7XtLtCgrGce15cVNxQjUOFj4H45grO62j35mvlpWua0a X-Received: by 2002:a17:902:b787:: with SMTP id e7-v6mr4400347pls.317.1519463272965; Sat, 24 Feb 2018 01:07:52 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1519463272; cv=none; d=google.com; s=arc-20160816; b=KvVveCZyadzCiyFYJjyNeGIFtBcLfmwEnoDb18p3N01EAPR4MKIVjenCGprtXDswlz 4cOK43T1/R/u6UvA21sLtkhvMgWJBNQtwRQf4af/z6upziK8TPT5GnI0yNWdDQCl5TRA 4KWmPAMA8N3qEbwpII/GM9/Nir/N1Fpc3IqKrNpyup6PEVXkHc2wJQf8mk2XMyN+rAKE 6ZxT1q5ha5QUye+ETtdJUE9AnMh1fPOiVQt1Snzzbf1GmWUpEm4YdmABAnyCcFGyVfh4 UDPlsihGZ347CKbhrpb/KNIxTNf78LT/log/G+NlOSfPgWZRaJkYgEuqSRD0gzDGYzXo zGjg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:content-transfer-encoding :content-disposition:mime-version:message-id:subject:cc:to:from:date :dkim-signature:arc-authentication-results; bh=LP5vT9cCpg6YzGH1eTt5FVOkzN8tYUfBCFV3S0vjEsA=; b=kY3ivH30BRi8Ibj0F0wZaeNCYX6Euz10ExPyoSuATZ7fJVGtAgwiI9+uNmINV+6vqS 6CRLPLJpdqytXtLANCbNxevfPhLG1y2qRF/JnnNaw8cGxFPijVUm4Mb3wrEiufeQ6HT9 nIiCkoPLZE/I5FzweGyMZPQIXgdlHhl6lpWBAgELcQmdmkxPs/sPYaR65TqpSAjbwaaN VWYTySgWf99ed1/0eW01Mk+G7mmx2a/ID7a2K/AvUgVw4WViDCVAu0pdVPdumoJr1xuw MSmFjcqzfSmB1hcP8dBvNPIWOAwkvEWvX5uhwDL6jccawyuQyP7gpYFsfwfPBmgTZwjs 6IiQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=jd11Bfx8; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id d67si1788497pfe.49.2018.02.24.01.07.38; Sat, 24 Feb 2018 01:07:52 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=jd11Bfx8; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751370AbeBXJG4 (ORCPT + 99 others); Sat, 24 Feb 2018 04:06:56 -0500 Received: from mail-pl0-f66.google.com ([209.85.160.66]:40074 "EHLO mail-pl0-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750751AbeBXJGv (ORCPT ); Sat, 24 Feb 2018 04:06:51 -0500 Received: by mail-pl0-f66.google.com with SMTP id i6so6334759plt.7 for ; Sat, 24 Feb 2018 01:06:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:mime-version:content-disposition :content-transfer-encoding:user-agent; bh=LP5vT9cCpg6YzGH1eTt5FVOkzN8tYUfBCFV3S0vjEsA=; b=jd11Bfx8CdU8phlHcDxh0iKrnB7zasm38ter1xHnMudlfrwG2vk56lTcaEh072+85p hdQRq2sj3XqJGtVNafDxjebuczIaKm2KV2lIBpzTOmKnI2W+VYt+SW5Z0Q5QIfLfaD7F 2c51FWZJED60JzzqB5MyC2XkZxftEiEFZYwt7k+cokuL1N7XcvcLbPBdv5gJp/spR2/e His8OYISSZRv5yOZiPzKT/j1f8xJdgOES9qUTmuINm06u3BzjssUohfWXUZFwD5akfQi 5prUkxMjEvCsgCOzV2EvCi2+gUwOkfS4UCfzoVeQ0pvKOc+kvsW+QKnU4JDnYqCzxPx1 ohsQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:mime-version :content-disposition:content-transfer-encoding:user-agent; bh=LP5vT9cCpg6YzGH1eTt5FVOkzN8tYUfBCFV3S0vjEsA=; b=ljTqsm4W8O7xqBhfVlhuhb11mN9l7es/R4oxSn85FDqh6JDWvY1TEBZyVZdBZXjUMR +3M6c1b4s/pUvSCAqCuu6kzZhSsBzz++jabU4Ats/oUUAPW7VmBd5fyFur1RtBDVbmi0 jsZnNF7uMA66ke4yPjLoC/hhB2noFNkVGoa4izX2Ie50WthRMF36D6mnMy8yeG12Rl8f 106nbZ5c7nGWGOB4a6gT4BBbTjlwoJKjTXR/yrde9oLCU6TM7wyBgRml07+XP77HSkFm 12r93sU9Fk+X3ORWaz51TgLMVY0B4iBn+b3ya28i6Iaz2yYejD+Hbz5i5eKBS9kxf7Im vdyA== X-Gm-Message-State: APf1xPBV4h35R5EGHFJC+eDp4UcCKR1BB9ZeJsofKhOuujHPAxjfEW6Q aLpRDMDL8skWFfgTpcOnJmM= X-Received: by 2002:a17:902:28e3:: with SMTP id f90-v6mr4337922plb.355.1519463211121; Sat, 24 Feb 2018 01:06:51 -0800 (PST) Received: from mordor.localdomain ([183.82.19.191]) by smtp.gmail.com with ESMTPSA id i1sm10078522pfi.116.2018.02.24.01.06.47 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Sat, 24 Feb 2018 01:06:50 -0800 (PST) Date: Sat, 24 Feb 2018 14:36:45 +0530 From: Aishwarya Pant To: Corey Minyard , Arnd Bergmann , Greg Kroah-Hartman , openipmi-developer@lists.sourceforge.net, linux-kernel@vger.kernel.org, Jonathan Corbet Cc: Julia Lawall Subject: [PATCH] char/ipmi: add documentation for sysfs interface Message-ID: <20180224090645.GA15344@mordor.localdomain> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.9.3 (2018-01-21) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org This is an attempt to document the sysfs interface for the IPMI drivers. Descriptions were collected from v2.0 of the IPMI specification and from code comments. Signed-off-by: Aishwarya Pant --- .../ABI/testing/sysfs-devices-platform-ipmi | 238 +++++++++++++++++++++ 1 file changed, 238 insertions(+) create mode 100644 Documentation/ABI/testing/sysfs-devices-platform-ipmi diff --git a/Documentation/ABI/testing/sysfs-devices-platform-ipmi b/Documentation/ABI/testing/sysfs-devices-platform-ipmi new file mode 100644 index 000000000000..2a781e7513b7 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-devices-platform-ipmi @@ -0,0 +1,238 @@ +What: /sys/devices/platform/ipmi_bmc.*/firmware_revision +Date: Mar, 2006 +KernelVersion: v2.6.17 +Contact: openipmi-developer@lists.sourceforge.net +Description: + (RO) The major and minor revision of the firmware. + + +What: /sys/devices/platform/ipmi_bmc.*/aux_firmware_revision +Date: Mar, 2006 +KernelVersion: v2.6.17 +Contact: openipmi-developer@lists.sourceforge.net +Description: + (RO) Holds additional information about the firmware revision, + such as boot block or internal data structure version numbers. + The meanings of the numbers are specific to the vendor + identified by Manufacturer ID. + + +What: /sys/devices/platform/ipmi_bmc.*/revision +Date: Mar, 2006 +KernelVersion: v2.6.17 +Contact: openipmi-developer@lists.sourceforge.net +Description: + (RO) Device revision. Useful for identifying if significant + hardware changes have been made to the implementation of the + management controller. + + +What: /sys/devices/platform/ipmi_bmc.*/provides_device_sdrs +Date: Mar, 2006 +KernelVersion: v2.6.17 +Contact: openipmi-developer@lists.sourceforge.net +Description: + (RO) Indicates whether device provides device sensor data + records (1) or not (0). + + +What: /sys/devices/platform/ipmi_bmc.*/device_id +Date: Mar, 2006 +KernelVersion: v2.6.17 +Contact: openipmi-developer@lists.sourceforge.net +Description: + (RO) Device id is specified by the manufacturer identified by + the Manufacturer ID field. This field allows controller specific + software to identify the unique application command, OEM + fields, and functionality that are provided by the controller + + +What: /sys/devices/platform/ipmi_bmc.*/additional_device_support +Date: Mar, 2006 +KernelVersion: v2.6.17 +Contact: openipmi-developer@lists.sourceforge.net +Description: + (RO) Lists the IPMI ‘logical device’ commands and functions + that the controller supports that are in addition to the + mandatory IPM and Application commands. + + +What: /sys/devices/platform/ipmi_bmc.*/ipmi_version +Date: Mar, 2006 +KernelVersion: v2.6.17 +Contact: openipmi-developer@lists.sourceforge.net +Description: + (RO) Displays the IPMI Command Specification Version. + + +What: /sys/devices/platform/ipmi_bmc.*/manufacturer_id +Date: Mar, 2006 +KernelVersion: v2.6.17 +Contact: openipmi-developer@lists.sourceforge.net +Description: + (RO) Identifies the manufacturer responsible for the + specification of functionality of the vendor (OEM)-specific + commands, codes, and interfaces used in the controller. + + +What: /sys/devices/platform/ipmi_bmc.*/product_id +Date: Mar, 2006 +KernelVersion: v2.6.17 +Contact: openipmi-developer@lists.sourceforge.net +Description: + (RO) Displays a number that identifies a particular system, + module, add-in card, or board set. The number is specified + according to the manufacturer given by Manufacturer ID. + +For detailed definitions of the above attributes, refer to section 20.1 'Get +Device ID Command' of the IPMI specification v2.0. + + +What: /sys/devices/platform/ipmi_bmc.*/guid +Date: Mar, 2006 +KernelVersion: v2.6.17 +Contact: openipmi-developer@lists.sourceforge.net +Description: + (RO) A GUID (Globally Unique ID), also referred to as a UUID + (Universally Unique Identifier), for the management controller, + as described in section 20.8 'Get Device GUID Command' of the + IPMI specification v2.0. + + +What: /sys/devices/platform/ipmi_si.*/type +Date: Sep, 2017 +KernelVersion: v4.15 +Contact: openipmi-developer@lists.sourceforge.net +Description: + (RO) The device interface for IPMI "kcs", "smic", "bt" or + "invalid" + +What: /sys/devices/platform/ipmi_si.*/idles +What: /sys/devices/platform/ipmi_si.*/watchdog_pretimeouts +What: /sys/devices/platform/ipmi_si.*/complete_transactions +What: /sys/devices/platform/ipmi_si.*/events +What: /sys/devices/platform/ipmi_si.*/interrupts +What: /sys/devices/platform/ipmi_si.*/hosed_count +What: /sys/devices/platform/ipmi_si.*/long_timeouts +What: /sys/devices/platform/ipmi_si.*/flag_fetches +What: /sys/devices/platform/ipmi_si.*/attentions +What: /sys/devices/platform/ipmi_si.*/incoming_messages +What: /sys/devices/platform/ipmi_si.*/short_timeouts +Date: Sep, 2017 +KernelVersion: v4.15 +Contact: openipmi-developer@lists.sourceforge.net +Description: + + idles: (RO) Number of times the interface was + idle while being polled. + + watchdog_pretimeouts: (RO) Number of watchdog pretimeouts. + + complete_transactions: (RO) Number of completed messages. + + events: (RO) Number of IPMI events received from + the hardware. + + interrupts: (RO) Number of interrupts the driver + handled. + + hosed_count: (RO) Number of times the hardware didn't + follow the state machine. + + long_timeouts: (RO) Number of times the driver + requested a timer while nothing was in + progress. + + flag_fetches: (RO) Number of times the driver + requested flags from the hardware. + + attentions: (RO) Number of time the driver got an + ATTN from the hardware. + + incoming_messages: (RO) Number of asynchronous messages + received. + + short_timeouts: (RO) Number of times the driver + requested a timer while an operation was + in progress. + + +What: /sys/devices/platform/ipmi_si.*/interrupts_enabled +Date: Sep, 2017 +KernelVersion: v4.15 +Contact: openipmi-developer@lists.sourceforge.net +Description: + (RO) Indicates whether interrupts are enabled or not. The driver + disables interrupts when it gets into a situation where it + cannot handle messages due to lack of memory. Once that + situation clears up, it will re-enable interrupts. + + +What: /sys/devices/platform/ipmi_si.*/params +Date: Sep, 2017 +KernelVersion: v4.15 +Contact: openipmi-developer@lists.sourceforge.net +Description: + [to be documented] + + +What: /sys/devices/platform/dmi-ipmi-ssif.*/type +Date: Sep, 2017 +KernelVersion: v4.15 +Contact: openipmi-developer@lists.sourceforge.net +Description: + (RO) Shows the IMPI device interface type - "ssif" here. + + +What: /sys/devices/platform/dmi-ipmi-ssif.*/hosed +What: /sys/devices/platform/dmi-ipmi-ssif.*/alerts +What: /sys/devices/platform/dmi-ipmi-ssif.*/sent_messages +What: /sys/devices/platform/dmi-ipmi-ssif.*/sent_messages_parts +What: /sys/devices/platform/dmi-ipmi-ssif.*/received_messages +What: /sys/devices/platform/dmi-ipmi-ssif.*/received_message_parts +What: /sys/devices/platform/dmi-ipmi-ssif.*/events +What: /sys/devices/platform/dmi-ipmi-ssif.*/watchdog_pretimeouts +What: /sys/devices/platform/dmi-ipmi-ssif.*/flag_fetches +What: /sys/devices/platform/dmi-ipmi-ssif.*/send_retries +What: /sys/devices/platform/dmi-ipmi-ssif.*/receive_retries +What: /sys/devices/platform/dmi-ipmi-ssif.*/send_errors +What: /sys/devices/platform/dmi-ipmi-ssif.*/receive_errors +Date: Sep, 2017 +KernelVersion: v4.15 +Contact: openipmi-developer@lists.sourceforge.net +Description: + hosed: (RO) Number of times the hardware didn't + follow the state machine. + + alerts: (RO) Number of alerts received. + + sent_messages: (RO) Number of total messages sent. + + sent_message_parts: (RO) Number of message parts sent. + Messages may be broken into parts if + they are long. + + receieved_messages: (RO) Number of message responses + received. + + received_message_parts: (RO) Number of message fragments + received. + + events: (RO) Number of received events. + + watchdog_pretimeouts: (RO) Number of watchdog pretimeouts. + + flag_fetches: (RO) Number of times a flag fetch was + requested. + + send_retries: (RO) Number of time a message was + retried. + + receive_retries: (RO) Number of times the receive of a + message was retried. + + send_errors: (RO) Number of times the send of a + message failed. + + receive_errors: (RO) Number of errors in receiving + messages. -- 2.16.2