From: Jiri Kosina <jikos@kernel.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>,
ksummit <Ksummit-discuss@lists.linuxfoundation.org>
Subject: Re: [Ksummit-discuss] [MAINTAINERS SUMMIT] Moving debugfs file systems into sysfs
Date: Thu, 4 Oct 2018 13:50:36 +0200 (CEST) [thread overview]
Message-ID: <nycvar.YFH.7.76.1810041346070.14430@cbobk.fhfr.pm> (raw)
In-Reply-To: <20181003143354.GB29980@kroah.com>
On Wed, 3 Oct 2018, Greg Kroah-Hartman wrote:
> Why not put the raw descriptors in sysfs? That's what pci and usb do,
> there's no reason you can't do the same here. You already have a sysfs
> device. Oh wait, you do, 'report_descriptor' right? Why do you also
> need it in debugfs?
Those are actually two different things -- the one in sysfs is verbatim
(binary) as has been read from device, but the one in debugfs is actually
showing how in-kernel parser has understood what came out of the device.
Which is not necessarily the same thing :)
Also it's rather verbose, with a lot of strings etc., not sure whether
you'd want to see that in sysfs.
With 'events' in hid debugfs, it's a similar story really (except it
doesn't currently have sysfs counterpart at all, as that'd basically just
be showing raw data as coming from the device).
Thanks,
--
Jiri Kosina
SUSE Labs
next prev parent reply other threads:[~2018-10-04 11:50 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-01 18:04 Steven Rostedt
2018-10-02 1:18 ` Greg KH
2018-10-02 1:26 ` Greg KH
2018-10-02 13:07 ` Steven Rostedt
2018-10-02 14:59 ` Olof Johansson
2018-10-02 16:00 ` Shuah Khan
2018-10-02 16:17 ` Greg Kroah-Hartman
2018-10-02 16:30 ` Greg Kroah-Hartman
2018-10-02 21:37 ` Mauro Carvalho Chehab
2018-10-02 21:57 ` Shuah Khan
2018-10-02 22:22 ` Greg Kroah-Hartman
2018-10-03 12:59 ` Jan Kara
2018-10-03 13:40 ` Greg Kroah-Hartman
2018-10-03 13:44 ` Jiri Kosina
2018-10-03 14:32 ` Greg Kroah-Hartman
2018-10-03 14:33 ` Greg Kroah-Hartman
2018-10-04 11:50 ` Jiri Kosina [this message]
2018-10-03 14:53 ` Jan Kara
2018-10-04 16:11 ` Takashi Iwai
2018-10-03 14:11 ` Shuah Khan
2018-10-03 10:06 ` Sudeep Holla
2018-10-03 13:13 ` Mark Brown
2018-10-03 14:52 ` Sudeep Holla
2018-10-02 8:40 ` Jani Nikula
2018-10-02 13:11 ` Steven Rostedt
2018-10-02 21:32 ` Mauro Carvalho Chehab
2018-10-03 6:23 ` Jani Nikula
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=nycvar.YFH.7.76.1810041346070.14430@cbobk.fhfr.pm \
--to=jikos@kernel.org \
--cc=Ksummit-discuss@lists.linuxfoundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=mchehab+samsung@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