linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eddie James <eajames@linux.vnet.ibm.com>
To: linux-hwmon@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, jdelvare@suse.com,
	linux@roeck-us.net, joel@jms.id.au,
	Eddie James <eajames@linux.vnet.ibm.com>
Subject: [PATCH v2 0/2] hwmon: (ucd9000) Add gpio and debugfs interfaces
Date: Tue, 13 Mar 2018 15:59:07 -0500	[thread overview]
Message-ID: <1520974749-5372-1-git-send-email-eajames@linux.vnet.ibm.com> (raw)

The ucd9000 series chips have gpio pins. Add a gpio chip interface to the ucd
device so that users can query and set the state of the gpio pins.

Add a debugfs interface using the existing pmbus debugfs directory to provide
MFR_STATUS and the status of the gpi faults to users.

Changes since v1:
 - dropped dev_err messages
 - made gpio chip registration conditional on having gpio pins
 - made mfr_status debugfs attribute more simple

Christopher Bostic (2):
  hwmon: (ucd9000) Add gpio chip interface
  hwmon: (ucd9000) Add debugfs attributes to provide mfr_status

 drivers/hwmon/pmbus/ucd9000.c | 341 +++++++++++++++++++++++++++++++++++++++++-
 1 file changed, 340 insertions(+), 1 deletion(-)

-- 
1.8.3.1

             reply	other threads:[~2018-03-13 20:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-13 20:59 Eddie James [this message]
2018-03-13 20:59 ` [PATCH v2 1/2] hwmon: (ucd9000) Add gpio chip interface Eddie James
2018-03-13 21:13   ` Andy Shevchenko
2018-03-14 18:55     ` Guenter Roeck
2018-03-14 19:01       ` Eddie James
2018-03-16  5:26   ` kbuild test robot
2018-03-16  6:01   ` kbuild test robot
2018-03-13 20:59 ` [PATCH v2 2/2] hwmon: (ucd9000) Add debugfs attributes to provide mfr_status Eddie James
2018-03-14 19:19   ` Guenter Roeck
2018-03-14 19:46     ` Eddie James
2018-03-14 21:16       ` Guenter Roeck

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=1520974749-5372-1-git-send-email-eajames@linux.vnet.ibm.com \
    --to=eajames@linux.vnet.ibm.com \
    --cc=jdelvare@suse.com \
    --cc=joel@jms.id.au \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    /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).