From: Pavel Machek <pavel@ucw.cz>
To: Andrey Smirnov <andrew.smirnov@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Chris Healy <cphealy@gmail.com>,
Lucas Stach <l.stach@pengutronix.de>,
Nikita Yushchenko <nikita.yoush@cogentembedded.com>,
Lee Jones <lee.jones@linaro.org>
Subject: Re: [PATCH v5 1/2] platform: Add driver for RAVE Supervisory Processor
Date: Wed, 30 Aug 2017 11:06:59 +0200 [thread overview]
Message-ID: <20170830090658.GA31423@amd> (raw)
In-Reply-To: <CAHQ1cqFYEGAcCxh7fM+VtvoDxt6phxoqD9KYUOLX4ZXLTWWtLw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1662 bytes --]
On Mon 2017-08-28 09:23:10, Andrey Smirnov wrote:
> On Thu, Aug 24, 2017 at 9:04 AM, Pavel Machek <pavel@ucw.cz> wrote:
> > On Fri 2017-07-28 07:27:03, Andrey Smirnov wrote:
> >> Add a driver for RAVE Supervisory Processor, an MCU implementing
> >> varoius bits of housekeeping functionality (watchdoging, backlight
> >> control, LED control, etc) on RAVE family of products by Zodiac
> >> Inflight Innovations.
> >>
> >> This driver implementes core MFD/serdev device as well as
> >> communication subroutines necessary for commanding the device.
> >
> > This introduces new /sysfs userland interfaces, right? That needs documenting,
> > and some review.
> >
>
> Correct and yes, good point. I was originally asked to implement all
> of the exposed attributes via sysfs, but, after more discussion, I now
> have green light to move a large chunk of those into debugfs which is
> what I intend to do in v6, I'll also update it to document all of the
> remaining sysfs entries.
Ok, we still would like to have documentation. .. and debugfs is for
debugging, not for production use.
> > For example... bootreason is there on Nokia N900, too. We want to use same interface...
> >
>
> I tried grepping Documentation/ABI and kernel tree in general for that
> sysfs interface, but wasn't able to find it. If you don't mind, could
> you point me to where it's implemented?
I'm not sure if the implementation is in the mainline, but the
bootloader provides this functionality.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2017-08-30 9:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-28 14:27 [PATCH v5 0/2] ZII RAVE platform driver Andrey Smirnov
2017-07-28 14:27 ` [PATCH v5 1/2] platform: Add driver for RAVE Supervisory Processor Andrey Smirnov
2017-07-29 13:23 ` kbuild test robot
2017-08-24 16:04 ` Pavel Machek
2017-08-28 16:23 ` Andrey Smirnov
2017-08-30 9:06 ` Pavel Machek [this message]
2017-07-28 14:27 ` [PATCH v5 2/2] dt-bindings: mfd: Add bindings for ZII RAVE devices Andrey Smirnov
2017-08-28 15:51 ` Greg Kroah-Hartman
2017-08-28 16:23 ` Andrey Smirnov
2017-07-28 23:30 ` [PATCH v5 0/2] ZII RAVE platform driver Greg Kroah-Hartman
2017-07-29 0:07 ` Andrey Smirnov
2017-08-02 20:31 ` Andrey Smirnov
2017-08-02 23:03 ` Greg Kroah-Hartman
2017-08-28 15:51 ` Greg Kroah-Hartman
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=20170830090658.GA31423@amd \
--to=pavel@ucw.cz \
--cc=andrew.smirnov@gmail.com \
--cc=cphealy@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=l.stach@pengutronix.de \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nikita.yoush@cogentembedded.com \
/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