linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bernie Thompson <bernie@plugable.com>
To: linux-fbdev@vger.kernel.org
Subject: Re: [PATCH 5/10] udlfb: Add functions to expose sysfs metrics and
Date: Thu, 18 Feb 2010 23:03:37 +0000	[thread overview]
Message-ID: <480988181002181503i58f6f4afo5b164bac879bb2a1@mail.gmail.com> (raw)
In-Reply-To: <1266245168.4353.3300.camel@bernie-aspireone>

Hi Greg,

On Thu, Feb 18, 2010 at 7:57 AM, Greg KH <greg@kroah.com> wrote:

> All new sysfs files will need a Documentation/ABI/ patch as well to
> explain the files.

I'll construct an additional patch to document the edid file (this
aught to be a standardized thing for all framebuffers, anyway - and
others have done similar/same).

And I'll do a separate one for the individual metrics if they're kept
in sysfs in the future.

>> metrics_misc
>
> This isn't.  sysfs files are "one value per file".  If you want to do
> something else, like this file, I suggest using debugfs instead.

The metrics stuff is a good candidate for moving to debugfs, I guess,
in a future patch. For now, anything in that set which violates sysfs
guidelines (metrics_misc) aught to just be removed, I guess.

These metrics have already been very helpful for comparing different
rendering algorithms, for debugging, and it's very helpful for
gathering info from end-users that may not have anything other than
sysfs set up. There are so many different hardware/software scenarios
that there's often no way to have any sense of what's happening
without more detailed instrumentation like this.

Best wishes,
Bernie
http://plugable.com/

  parent reply	other threads:[~2010-02-18 23:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-15 14:46 [PATCH 5/10] udlfb: Add functions to expose sysfs metrics and Bernie Thompson
2010-02-18 15:57 ` Greg KH
2010-02-18 23:03 ` Bernie Thompson [this message]
2010-02-19  0:31 ` Greg KH

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=480988181002181503i58f6f4afo5b164bac879bb2a1@mail.gmail.com \
    --to=bernie@plugable.com \
    --cc=linux-fbdev@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).