linux-leds.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ian Pilcher <arequipeno@gmail.com>
To: linux-leds@vger.kernel.org, kernelnewbies@kernelnewbies.org,
	linux-kernel@vger.kernel.org
Subject: Re: device_create_file returns 0 but doesn't work
Date: Sun, 01 Sep 2013 23:48:34 -0500	[thread overview]
Message-ID: <522418A2.8030909@gmail.com> (raw)
In-Reply-To: <l00j5e$8b0$1@ger.gmane.org>

On 09/01/2013 06:38 PM, Ian Pilcher wrote:
> I am trying to add an additional sysfs attribute to a device (LED) that
> is created by another driver.  (My ultimate goal is to provide a way for
> a userspace application to use the functionality provided by
> led_blink_set, which doesn't currently seem to be possible.)

Turns out it is possible, with the LED timer trigger, so this issue is
now moot.

> 
> The kernel module code that sets up all the GPIOs & LEDs in my NAS is
> at:
> 
>   http://pastebin.com/TJZGww8T
> 
> The call to device_create_file is at line 373.
> 
> device_create_file is returning 0, but the "foo" attribute is not being
> created.  ("find /sys -name '*foo*'" doesn't find anything, so I'm not
> just looking in the wrong place.)

Still rather odd that it doesn't work, however, since ledtrig-timer.c
seems to do pretty much the same thing.  Oh well.

-- 
========================================================================
Ian Pilcher                                         arequipeno@gmail.com
Sometimes there's nothing left to do but crash and burn...or die trying.
========================================================================

      reply	other threads:[~2013-09-02  4:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-01 23:38 device_create_file returns 0 but doesn't work Ian Pilcher
2013-09-02  4:48 ` Ian Pilcher [this message]

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=522418A2.8030909@gmail.com \
    --to=arequipeno@gmail.com \
    --cc=kernelnewbies@kernelnewbies.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-leds@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 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).