[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACRpkdb0Bv1iwtd61GUQLU25nAKrfk-VS0PGKTYh_LoyjYWHFg@mail.gmail.com>
Date: Mon, 4 Mar 2019 13:07:09 +0100
From: Linus Walleij <linus.walleij@...aro.org>
To: Marek Behun <marek.behun@....cz>
Cc: Tony Lindgren <tony@...mide.com>, Shawn Guo <shawnguo@...nel.org>,
"open list:GPIO SUBSYSTEM" <linux-gpio@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v3 bus+gpio 3/5] bus: moxtet: Add sysfs documentation
On Fri, Mar 1, 2019 at 4:15 PM Marek Behun <marek.behun@....cz> wrote:
> On Fri, 1 Mar 2019 15:34:26 +0100
> Linus Walleij <linus.walleij@...aro.org> wrote:
>
> > > +What: /sys/bus/moxtet/devices/moxtet-<name>.<addr>/output_value
> > > +Date: March 2019
> > > +KernelVersion: 5.2
> > > +Contact: Marek BehĂșn <marek.behun@....cz>
> > > +Description: (RW) Read last written value or write value to the
> > > module on
> > > + this Moxtet address. Format: %x
> >
> > What is the usecase for these?
> >
> > If this is for debugging it should be in debugfs rather than in sysfs.
> >
> > If it is here for random userspace drivers, we need some good
> > explanation as to why they can't just be kernel drivers.
>
> Hmm, it was for debugging purposes but the ability to write there is
> not needed anymore... Shall I make it read/only? Or completely remove
> it?
I would either remove it or move it to debugfs.
Yours,
Linus Walleij
Powered by blists - more mailing lists