All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Wang, Kuiying" <kuiying.wang@intel.com>
To: Brad Bishop <bradleyb@fuzziesquirrel.com>,
	"geissonator@yahoo.com" <geissonator@yahoo.com>
Cc: "kunyi731@gmail.com" <kunyi731@gmail.com>,
	"Mihm, James" <james.mihm@intel.com>,
	"Tanous, Ed" <ed.tanous@intel.com>,
	"Li, Yong B" <yong.b.li@intel.com>,
	"Feist, James" <james.feist@intel.com>,
	"Jia, Chunhui" <chunhui.jia@intel.com>,
	"venture@google.com" <venture@google.com>,
	"openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>,
	"Xu, Qiang" <qiang.xu@intel.com>,
	"Yang, Cheng C" <cheng.c.yang@intel.com>,
	"chunhui.jia@linux.intel.com" <chunhui.jia@linux.intel.com>,
	"Nguyen, Hai V" <hai.v.nguyen@intel.com>
Subject: About new gpio API in linux/gpio.h adopted by kernel 4.8
Date: Thu, 6 Sep 2018 07:29:55 +0000	[thread overview]
Message-ID: <959CAFA1E282D14FB901BE9A7BF4E77249E0C0B0@shsmsx102.ccr.corp.intel.com> (raw)

Hi Brad/Andrew,
I found the new gpio API adopted by kernel 4.8, is not fully ready, all the lines are "unnamed".
If that we cannot switch to it now. 
Or there is special kernel based configuration I have to do?

root@wolfpass:/tmp# ./gpiodetect
gpiochip0 [SGPIOA] (8 lines)
gpiochip1 [SGPIOB] (8 lines)
gpiochip10 [1e780000.gpio] (232 lines)
gpiochip2 [SGPIOC] (8 lines)
gpiochip3 [SGPIOD] (8 lines)
gpiochip4 [SGPIOE] (8 lines)
gpiochip5 [SGPIOF] (8 lines)
gpiochip6 [SGPIOG] (8 lines)
gpiochip7 [SGPIOH] (8 lines)
gpiochip8 [SGPIOI] (8 lines)
gpiochip9 [SGPIOJ] (8 lines)
root@wolfpass:/tmp# ./gpioinfo /dev/gpiochip1
gpiochip1 - 8 lines:
        line   0:      unnamed       unused  output  active-high
        line   1:      unnamed       unused  output  active-high
        line   2:      unnamed       unused  output  active-high
        line   3:      unnamed       unused  output  active-high
        line   4:      unnamed       unused  output  active-high
        line   5:      unnamed       unused  output  active-high
        line   6:      unnamed       unused  output  active-high
        line   7:      unnamed       unused  output  active-high
root@wolfpass:/tmp# ./gpioinfo /dev/gpiochip10
gpiochip10 - 232 lines:
        line   0:      unnamed       unused   input  active-high
        line   1:      unnamed       unused   input  active-high
        line   2:      unnamed       unused   input  active-high
        line   3:      unnamed       unused   input  active-high
        line   4:      unnamed       unused   input  active-high
        line   5:      unnamed       unused   input  active-high
        line   6:      unnamed       unused   input  active-high
        line   7:      unnamed       unused   input  active-high
        line   8:      unnamed       unused   input  active-high
        line   9:      unnamed       unused   input  active-high
        line  10:      unnamed       unused   input  active-high
        line  11:      unnamed       unused   input  active-high
        line  12:      unnamed       unused   input  active-high
        line  13:      unnamed       unused   input  active-high
        line  14:      unnamed       unused   input  active-high
        line  15:      unnamed       unused   input  active-high
        line  16:      unnamed       unused   input  active-high
root@wolfpass:/tmp# ./gpioget /dev/gpiochip10 219
./gpioget: error reading GPIO values: Device or resource busy

Thanks,
Kuiying.

             reply	other threads:[~2018-09-06  7:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-06  7:29 Wang, Kuiying [this message]
2018-09-06 12:47 ` About new gpio API in linux/gpio.h adopted by kernel 4.8 Andrew Geissler
2018-09-06 13:29   ` Andrew Jeffery
2018-09-07 10:10     ` Wang, Kuiying

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=959CAFA1E282D14FB901BE9A7BF4E77249E0C0B0@shsmsx102.ccr.corp.intel.com \
    --to=kuiying.wang@intel.com \
    --cc=bradleyb@fuzziesquirrel.com \
    --cc=cheng.c.yang@intel.com \
    --cc=chunhui.jia@intel.com \
    --cc=chunhui.jia@linux.intel.com \
    --cc=ed.tanous@intel.com \
    --cc=geissonator@yahoo.com \
    --cc=hai.v.nguyen@intel.com \
    --cc=james.feist@intel.com \
    --cc=james.mihm@intel.com \
    --cc=kunyi731@gmail.com \
    --cc=openbmc@lists.ozlabs.org \
    --cc=qiang.xu@intel.com \
    --cc=venture@google.com \
    --cc=yong.b.li@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.