All of lore.kernel.org
 help / color / mirror / Atom feed
From: Darren Hart <dvhart@linux.intel.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: "lkml," <linux-kernel@vger.kernel.org>,
	Grant Likely <grant.likely@secretlab.ca>,
	Denis Turischev <denis@compulab.co.il>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: gpio-sch GPIO_SYSFS access
Date: Thu, 07 Feb 2013 07:17:41 -0800	[thread overview]
Message-ID: <5113C595.3070402@linux.intel.com> (raw)
In-Reply-To: <CACRpkdacYOeG2tqSW5YhqbkxGnxCxamAc_UUyghEQXO98OvKJw@mail.gmail.com>



On 02/07/2013 02:09 AM, Linus Walleij wrote:
> On Thu, Feb 7, 2013 at 1:58 AM, Darren Hart <dvhart@linux.intel.com> wrote:
> 
>> Is it that some other driver has claimed these GPIO lines? If so, how do
>> I determine which one?
> 
> Yes I think that could be it, the driver would need to call
> gpio_export() for it to also be accessible in sysfs.

Do you mean gpiochip_export()?

Hrm, neither gpio-pch nor gpio-sch call gpiochip_export() directly. They
both call gpiochip_add() and that calls gpiochip_export() unconditionally.
As far as I could tell, both drivers call gpiochip_export().

I thought maybe the sch happened to early, maybe hitting the the
pre-driver-model-support note in gpiochip_export(), but it runs after
the pch chip for some reason, and that one is fine. I suppose I could be
failing on device_create or sysfs_create_group and just not seeing the
output. I'll try to get DYNAMIC_DEBUG and pr_debug in gpiolib.c working
(that always seems to be an unnecessarily arduous exercise).

> 
> Configure in debugfs and check the file "gpio" in debugfs
> to figure out the client.

That file contained only the gpiochip244 from the gpio-pch driver,
nothing from the sch.

Thanks!

-- 
Darren Hart
Intel Open Source Technology Center
Yocto Project - Technical Lead - Linux Kernel

  reply	other threads:[~2013-02-07 15:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-07  0:58 gpio-sch GPIO_SYSFS access Darren Hart
2013-02-07 10:09 ` Linus Walleij
2013-02-07 15:17   ` Darren Hart [this message]
2013-02-08  0:36   ` Darren Hart
2013-02-08  4:40   ` Darren Hart
2013-02-08  7:08     ` Darren Hart
2013-02-08  8:49       ` Samuel Ortiz
2013-02-08 10:36         ` Darren Hart
2013-02-08 11:07           ` Samuel Ortiz
2013-02-08 17:43             ` Darren Hart

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=5113C595.3070402@linux.intel.com \
    --to=dvhart@linux.intel.com \
    --cc=denis@compulab.co.il \
    --cc=grant.likely@secretlab.ca \
    --cc=gregkh@linuxfoundation.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    /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.