From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Thu, 4 Oct 2018 13:50:36 +0200 (CEST) From: Jiri Kosina To: Greg Kroah-Hartman In-Reply-To: <20181003143354.GB29980@kroah.com> Message-ID: References: <20181002161730.GA7119@kroah.com> <20181002163001.GA11068@kroah.com> <20181002183743.78eac32d@coco.lan> <0e19e6d0-47bd-d57f-8e31-e3521c467fe0@kernel.org> <20181002222238.GA11788@kroah.com> <20181003125916.GB21043@quack2.suse.cz> <20181003134012.GA13071@kroah.com> <20181003143233.GA29980@kroah.com> <20181003143354.GB29980@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Cc: Mauro Carvalho Chehab , ksummit Subject: Re: [Ksummit-discuss] [MAINTAINERS SUMMIT] Moving debugfs file systems into sysfs List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , 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