From: Pavel Machek <pavel@ucw.cz>
To: Christian Eggers <ceggers@arri.de>
Cc: Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Jonathan Cameron <jic23@kernel.org>,
Andy Shevchenko <andy.shevchenko@gmail.com>,
Hartmut Knaack <knaack.h@gmx.de>,
Lars-Peter Clausen <lars@metafoo.de>,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iio: documentation: light: Add as73211 sysfs documentation
Date: Mon, 10 Aug 2020 11:00:54 +0200 [thread overview]
Message-ID: <20200810090054.GA8495@localhost> (raw)
In-Reply-To: <20200809074335.23734-1-ceggers@arri.de>
Hi!
> The driver for the as73211 light sensor provides the following not yet
> documented sysfs entries:
> - in_intensity_(x|y|z)_raw
> - in_intensity_(x|y|z)_scale
> - in_intensity_sampling_frequency(_available)
> - in_intensity_hardwaregain(_available)
Should that be hardware_gain ?
Pavel
--
next prev parent reply other threads:[~2020-08-10 9:01 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-05 5:57 [PATCH v6 0/2] iio: light: Support AMS AS73211 digital XYZ sensor Christian Eggers
2020-08-05 5:57 ` [PATCH v6 1/2] dt-bindings: iio: light: add AMS AS73211 support Christian Eggers
2020-08-06 17:44 ` Jonathan Cameron
2020-08-05 5:57 ` [PATCH v6 2/2] iio: light: as73211: New driver Christian Eggers
2020-08-05 7:39 ` Andy Shevchenko
2020-08-06 17:44 ` Jonathan Cameron
2020-08-07 15:46 ` Christian Eggers
2020-08-08 16:14 ` Jonathan Cameron
2020-08-09 7:43 ` [PATCH] iio: documentation: light: Add as73211 sysfs documentation Christian Eggers
2020-08-09 11:30 ` Jonathan Cameron
2020-08-10 5:24 ` [PATCH v2] " Christian Eggers
2020-08-16 9:19 ` Jonathan Cameron
2020-08-10 9:00 ` Pavel Machek [this message]
2020-08-10 9:57 ` [PATCH] " Christian Eggers
2020-08-10 12:35 ` Pavel Machek
2020-08-10 13:24 ` Christian Eggers
2020-08-16 9:18 ` Jonathan Cameron
2020-09-01 18:46 ` [PATCH v6 2/2] iio: light: as73211: New driver Jonathan Cameron
2020-09-03 18:43 ` Jonathan Cameron
2020-09-09 18:05 ` Christian Eggers
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=20200810090054.GA8495@localhost \
--to=pavel@ucw.cz \
--cc=Jonathan.Cameron@huawei.com \
--cc=andy.shevchenko@gmail.com \
--cc=ceggers@arri.de \
--cc=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
/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;
as well as URLs for NNTP newsgroup(s).