public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: Paul Walmsley <paul@pwsan.com>
Cc: Hiroshi DOYU <Hiroshi.DOYU@nokia.com>, linux-omap@vger.kernel.org
Subject: Re: [PATCH 1/2] ARM: OMAP: CLKFW: Initial debugfs support for omap clock framework
Date: Thu, 17 Apr 2008 11:54:02 -0700	[thread overview]
Message-ID: <200804171154.02983.david-b@pacbell.net> (raw)
In-Reply-To: <alpine.DEB.1.00.0804171243340.8530@utopia.booyaka.com>

On Thursday 17 April 2008, Paul Walmsley wrote:
> Hello David,
> 
> On Thu, 17 Apr 2008, David Brownell wrote:
> 
> > On Thursday 17 April 2008, Paul Walmsley wrote:
> > > But it would be nice to be able to call into clock functions like 
> > > round_rate, set_rate, and set_parent via filesystem writes for debugging 
> > > purposes, and I don't think that debugfs supports this.
> > 
> > It does, if you set up the files properly ... except
> > maybe the set_parent stuff.
> 
> Could you be more specific?  The only write support that I see in the 
> debugfs API is to store bytes into memory locations.  We'd need to call 
> functions also upon writes.

struct dentry *debugfs_create_file(const char *name, mode_t mode,
                                   struct dentry *parent, void *data,
                                   const struct file_operations *fops);

... provide a file_operations vector supporting writes.  Or building
more complex values with seq_file, etc.

There are indeed lots of functions letting you create single-valued
attributes.  I happen to find that model uselessly constraining,
and can't really imagine using it.

- Dave


  reply	other threads:[~2008-04-17 18:54 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-16  8:44 [PATCH 1/1] ARM: OMAP: CLKFW: Initial sysfs support for omap clock framework Hiroshi DOYU
2008-04-16  8:57 ` Hiroshi DOYU
2008-04-16 13:20   ` Hiroshi DOYU
2008-04-16 16:58 ` David Brownell
2008-04-16 20:51   ` Tony Lindgren
2008-04-17 14:09     ` [PATCH 1/2] ARM: OMAP: CLKFW: Initial debugfs " Hiroshi DOYU
2008-04-17 14:09       ` [PATCH 2/2] ARM: OMAP: CLKFW: Remove procfs entry for debugging " Hiroshi DOYU
2008-04-17 16:23       ` [PATCH 1/2] ARM: OMAP: CLKFW: Initial debugfs support for omap " Paul Walmsley
2008-04-17 18:40         ` David Brownell
2008-04-17 18:45           ` Paul Walmsley
2008-04-17 18:54             ` David Brownell [this message]
2008-04-17 19:17               ` Paul Walmsley
2008-04-17 18:57             ` Hiroshi DOYU
2008-04-17 19:14               ` David Brownell
2008-04-17 19:44                 ` Paul Walmsley
2008-04-17 19:49                   ` Igor Stoppa
2008-04-17 20:47                     ` Paul Walmsley
2008-04-17 21:22                       ` David Brownell
2008-04-18  7:08                       ` Igor Stoppa
2008-04-17 19:58                   ` Hiroshi DOYU
2008-04-21 18:40                     ` Tony Lindgren

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=200804171154.02983.david-b@pacbell.net \
    --to=david-b@pacbell.net \
    --cc=Hiroshi.DOYU@nokia.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=paul@pwsan.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox