From: "Andrew Jeffery" <andrew@aj.id.au>
To: "naveen moses" <naveen.moses@hotmail.com>,
"openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>
Cc: Zhikui Ren <zhikui.ren@intel.com>,
Vernon Mauery <vernon.mauery@linux.intel.com>,
Jae Hyun Yoo <jae.hyun.yoo@linux.intel.com>,
Ed Tanous <ed@tanous.net>,
naveen moses <naveen.moses@outlook.com>
Subject: Re: support for gpio as ipmb sensor
Date: Wed, 06 Oct 2021 10:46:40 +1030 [thread overview]
Message-ID: <ef4d5ac6-49e8-40d6-9e6b-1fe030f3909a@www.fastmail.com> (raw)
In-Reply-To: <PS2PR02MB26959672C7002D26EB5F4A4691AF9@PS2PR02MB2695.apcprd02.prod.outlook.com>
Hi Naveen,
On Tue, 5 Oct 2021, at 23:46, naveen moses wrote:
> Hi All,
>
> we have a couple of gpios ( input ) accessed via ipmb commands in our platform.
> which cannot be directly monitored using gpio monitor.
What do you mean when you say "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).
What about modelling the behaviour the GPIO state represents rather
than just providing a DBus interface to the GPIO values?
Andrew
next prev parent reply other threads:[~2021-10-06 0:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-05 13:16 support for gpio as ipmb sensor naveen moses
2021-10-06 0:16 ` Andrew Jeffery [this message]
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=ef4d5ac6-49e8-40d6-9e6b-1fe030f3909a@www.fastmail.com \
--to=andrew@aj.id.au \
--cc=ed@tanous.net \
--cc=jae.hyun.yoo@linux.intel.com \
--cc=naveen.moses@hotmail.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).