kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: me@tobin.cc (Tobin C. Harding)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Problems with adding a sysfs file
Date: Tue, 18 Apr 2017 10:05:17 +1000	[thread overview]
Message-ID: <20170418000517.GB745@eros> (raw)
In-Reply-To: <CACFD4SRhLWtZsTvkgDTgeE54ZBkUqzkWgE7=JPZBb4jLMDb2Nw@mail.gmail.com>

On Mon, Apr 17, 2017 at 02:04:48PM -0700, Abhishek Bhardwaj wrote:
> I used a pr_debug and printk KERN_INFO ,before my original email , to
> verify they weren't being called.

You will have more success on kernel mailing lists if you do not top
post as you have done :)

> On Apr 17, 2017 1:43 PM, <valdis.kletnieks@vt.edu> wrote:
> 
> > On Mon, 17 Apr 2017 01:17:08 -0700, Abhishek Bhardwaj said:
> > > I followed this link to add a sysfs file
> > > http://kroah.com/log/blog/2013/06/26/how-to-create-a-
> > sysfs-file-correctly/
> > > .
> > >
> > > I set the driver.groups field and declared the attribute and attribute
> > > groups required by the sysfs file. When I boot my kernel I see the
> > > file but my store and show handlers don't get called when I try to cat
> > > or echo to the file. Is there any step I'm missing ?.
> >
> > The traditional way to start debugging this is to add a line at the
> > beginning
> > of your show and store routines:
> >
> >         printk(KERN_DEBUG "Now in our special sysfs show routine\n");

You could have put your response here, that way readers would have a
reference to you comment.

> > and see if it shows up in your dmesg or not.  If not, your routine
> > is probably not being called.  If it is, the problem is in the routine.
> >
> > (You'd be surprised how often people say their routine isn't getting
> > called,
> > when it in fact is, or vice versa..)
> >

Good luck,
Tobin.

      reply	other threads:[~2017-04-18  0:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-17  8:17 Problems with adding a sysfs file Abhishek Bhardwaj
2017-04-17 20:43 ` valdis.kletnieks at vt.edu
2017-04-17 21:04   ` Abhishek Bhardwaj
2017-04-18  0:05     ` Tobin C. Harding [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=20170418000517.GB745@eros \
    --to=me@tobin.cc \
    --cc=kernelnewbies@lists.kernelnewbies.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).