Received: by 10.223.185.116 with SMTP id b49csp3887101wrg; Mon, 26 Feb 2018 07:42:30 -0800 (PST) X-Google-Smtp-Source: AH8x227IPbNw1bhIrXTn7kEH2fLJw5IBEVBxuXNMwu/Jlwwb+zyd1swCFpxPcN1zkHSj0fzF6rf7 X-Received: by 2002:a17:902:4381:: with SMTP id j1-v6mr10888052pld.297.1519659749887; Mon, 26 Feb 2018 07:42:29 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1519659749; cv=none; d=google.com; s=arc-20160816; b=p3IyAEb5RayMhUMTh5Mf0muHGBL9kMLinophDX+NXHfm947Co5jF/GQmO6GBL/tj1G S1zmxf8+JdYLk6HcpsEs5MwWO7TaRzQDY77jxNDeYFMn9Us41BC4fMqlb6EgAD3lZPco tZNvL21qk5HwgnfPu7I7j6a/w94Iygav5Y4N4nz8dfnB+92je+hut8t3p+02g+4HD4WE YTPl7Rn39lF8bhJI2RWJfrRI683cK7FKJsvpBfqzAADjYa4jMWKNlKVEyRaMVbn1UgZC TbP8fc/gd15FhgFo8jOKdaW64Adlt1hPYSSumYLJKBtZaFXG9e/oNdRFvheU63tiXNjP fhsQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-language :content-transfer-encoding:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:reply-to:dkim-signature :arc-authentication-results; bh=wnGyO6AZTjLMJ3BoN46jD7dalcFsom6F0bs9fTcI9aQ=; b=qRC3acnKtC5+Zl6VlVN8z+krricpo5Of/k1MHk4cDDSfj2lxAwCreaf+t80RProJPp aTs1jWoSrCAUXpkOrFQ9JKFuvcFEjMb/yGT57TYq5v0Az0MzTXfebyeDByorS4u0E/MN +pUFBHCP1Fb4R68feoOl6zVz4TZ9C2a1EXF65e5GqbPDZ5SDmoU8wFQ5N+otjny3+x0b U5MhE5R7jPtuHyTJPd7yY6aKvNYV/grdXfaMtNjh7NHmw0OOaNK4LnSOHaJw9IJUslK/ wHKurvaV6T/HeUIaiB4Kb36q0h7qbc+U8+x3QzV1/9zeOAG+V3n8l7rc2301H6aa18fN TzHw== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@gmail.com header.s=20161025 header.b=Sq4vYbPC; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id u19si5627174pgv.195.2018.02.26.07.42.15; Mon, 26 Feb 2018 07:42:29 -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=fail header.i=@gmail.com header.s=20161025 header.b=Sq4vYbPC; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752017AbeBZPlO (ORCPT + 99 others); Mon, 26 Feb 2018 10:41:14 -0500 Received: from mail-oi0-f66.google.com ([209.85.218.66]:37240 "EHLO mail-oi0-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751991AbeBZPlM (ORCPT ); Mon, 26 Feb 2018 10:41:12 -0500 Received: by mail-oi0-f66.google.com with SMTP id f186so10925455oig.4 for ; Mon, 26 Feb 2018 07:41:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:reply-to:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=wnGyO6AZTjLMJ3BoN46jD7dalcFsom6F0bs9fTcI9aQ=; b=Sq4vYbPChQdenzsBoiwjupC6ugPvwhsq9i00ckfMfjUx4G0CgCbj9OIpAyXN1WtGXT TIM2E7WisKtMyH0DWuArYXBBENTHooqgyrXftinf44ENsz2LIHkiemxxDqDKwJ9fGou3 kFGll0Sc1zkKZ6GIOg0NmLZgETBJQE//co0874HiWBuSxxbQCH8r3wZhDS4OR5f9165V 60pp8DueuKhotyuwbUL6QjZI/OJ7gzHSixsrtefKmbi59f6sOmP33+7U1OhRCZT0RYkE 4Fd6cZoLpI0G0U6ZHJ13SFN7po/jRXwe5scIfTZ3HpBsJEC++ZMBVp+8wNbCxr4kRTPe OgPw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:reply-to:subject:to:cc:references:from :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding:content-language; bh=wnGyO6AZTjLMJ3BoN46jD7dalcFsom6F0bs9fTcI9aQ=; b=LdzOZsTHU1b0mTB5Xc06kQObWNc8PRRVHmAYJbga4zCmySy2Oiee185315KCS/OFt2 rize3/vSK0gWR/96udAXMV2SBMAZWT24EHJ5WTCuXAWTu/FBCrD+oPwJVlMAOdPSKQFy W2RBQ0FeIjyc0DbzBtYMlJkefkBr41CctDRCF+8Ac0Nxcm1/UNR7pC1Z8EUYlqRmfejx NFhWCgLajv8S6edc9h1QkXZxTLs98ZXFc5hymUls3otVYQCAhEF6mrLB6XnW8mn0gVsy voEQkGuYd9X8zCrEbVnhjaQHaUKvgAX6YhQY1SgiPwREr0U5GfSQSXKDkfJCXi9gQbLH AkHA== X-Gm-Message-State: APf1xPCeZwHYFeETKlAbAxGGgzk7YdmyPGWP0V9oL1CbPaDwXEn6kueT iGfVDnWlnzHPYCRDhwEfWt9d5KjhmA== X-Received: by 10.202.78.70 with SMTP id c67mr6676157oib.314.1519658244988; Mon, 26 Feb 2018 07:17:24 -0800 (PST) Received: from serve.minyard.net (serve.minyard.net. [2001:470:b8f6:1b::1]) by smtp.gmail.com with ESMTPSA id u19sm4796556otu.40.2018.02.26.07.17.23 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 26 Feb 2018 07:17:23 -0800 (PST) Received: from [192.168.27.3] (t430m.minyard.net [192.168.27.3]) by serve.minyard.net (Postfix) with ESMTPSA id 64EF62B9; Mon, 26 Feb 2018 09:17:22 -0600 (CST) Reply-To: minyard@acm.org Subject: Re: [PATCH] char/ipmi: add documentation for sysfs interface To: Aishwarya Pant , Arnd Bergmann , Greg Kroah-Hartman , openipmi-developer@lists.sourceforge.net, linux-kernel@vger.kernel.org, Jonathan Corbet Cc: Julia Lawall References: <20180224090645.GA15344@mordor.localdomain> From: Corey Minyard Message-ID: <5df2a0a6-d99e-58c1-eb06-cac063b4024c@acm.org> Date: Mon, 26 Feb 2018 09:17:22 -0600 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <20180224090645.GA15344@mordor.localdomain> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-GB Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 02/24/2018 03:06 AM, Aishwarya Pant wrote: > 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 Wow, you spent some time on this.  It all looks accurate, it's in my tree. Thanks, -corey > --- > .../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.