openbmc.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: naveen moses <naveen.moses@hotmail.com>
To: "openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>
Cc: "zhikui.ren@intel.com" <zhikui.ren@intel.com>,
	"jae.hyun.yoo@linux.intel.com" <jae.hyun.yoo@linux.intel.com>,
	"andrew@aj.id.au" <andrew@aj.id.au>,
	"vernon.mauery@linux.intel.com" <vernon.mauery@linux.intel.com>,
	"ed@tanous.net" <ed@tanous.net>,
	naveen moses <naveen.moses@outlook.com>
Subject: support for gpio  as ipmb sensor
Date: Tue, 5 Oct 2021 13:16:34 +0000	[thread overview]
Message-ID: <PS2PR02MB26959672C7002D26EB5F4A4691AF9@PS2PR02MB2695.apcprd02.prod.outlook.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 695 bytes --]

Hi All,

we have a couple of gpios ( input ) accessed via ipmb commands in our platform.
which cannot be directly monitored using gpio monitor.

our idea is to expose them as ipmb sensors which has gpio state as property which is updated based
on the current state of the gpio.

at present there is no compatible interface under xyz/openbmc_project/sensors for gpio as sensor.

So is this acceptable to create a new interface for gpio state under xyz/openbmc_project/sensors :
interface name : gpioState
which has a property named value whose possible values are boolean (true or false).

any alternate implementation suggestions or corrections are welcome.

Thanks,
Naveen.


[-- Attachment #2: Type: text/html, Size: 3053 bytes --]

             reply	other threads:[~2021-10-05 23:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-05 13:16 naveen moses [this message]
2021-10-06  0:16 ` support for gpio as ipmb sensor Andrew Jeffery
2021-10-06 14:40   ` Patrick Williams
2021-10-07  6:12   ` naveen moses
2021-10-07  7:45     ` naveen moses
2021-10-07 10:01       ` Andrei Kartashev

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=PS2PR02MB26959672C7002D26EB5F4A4691AF9@PS2PR02MB2695.apcprd02.prod.outlook.com \
    --to=naveen.moses@hotmail.com \
    --cc=andrew@aj.id.au \
    --cc=ed@tanous.net \
    --cc=jae.hyun.yoo@linux.intel.com \
    --cc=naveen.moses@outlook.com \
    --cc=openbmc@lists.ozlabs.org \
    --cc=vernon.mauery@linux.intel.com \
    --cc=zhikui.ren@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).