[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2026020347-mushy-lunar-d12d@gregkh>
Date: Tue, 3 Feb 2026 17:58:42 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Svyatoslav Ryhel <clamor95@...il.com>
Cc: Lee Jones <lee@...nel.org>, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>,
Dmitry Torokhov <dmitry.torokhov@...il.com>,
Pavel Machek <pavel@...nel.org>, Arnd Bergmann <arnd@...db.de>,
Sebastian Reichel <sre@...nel.org>,
Michał Mirosław <mirq-linux@...e.qmqm.pl>,
Ion Agorria <ion@...rria.com>, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-input@...r.kernel.org,
linux-leds@...r.kernel.org, linux-pm@...r.kernel.org
Subject: Re: [PATCH v1 2/9] misc: Support Asus Transformer's EC access device
On Tue, Feb 03, 2026 at 06:50:01PM +0200, Svyatoslav Ryhel wrote:
> > debugfs allows you to do much much more than simple stuff like
> > BIN_ATTR_RW(). Go wild there, but don't put debugging stuff in sysfs,
> > that is NOT what it is there for at all, but rather, that is exactly
> > what debugfs is for.
> >
>
> I am removing said stuff from sysfs, that is not what I am asking.
> Debugs does not allow to upload register values in a form of binary
> block. It allows only dumping via debugfs_create_blob or
> debugfs_create_regset32 but not writing. If you know examples of
> reading and writing register sets as binary data, please point me to
> it.
You can easily write your own given that debugfs allows you to use what
ever file operations you want to use for a file. Why not just use that?
> I am asking if it is possible only to preserve dockram_read/write
> functions in the code, without exposing it to sysfs.
Why would you want to do that?
confused,
greg k-h
Powered by blists - more mailing lists