From: Gabriele Mazzotta <gabriele.mzt@gmail.com>
To: jic23@kernel.org
Cc: knaack.h@gmx.de, lars@metafoo.de, pmeerw@pmeerw.net,
marxin.liska@gmail.com, marex@denx.de, rui.zhang@intel.com,
linux-kernel@vger.kernel.org, linux-iio@vger.kernel.org
Subject: Re: [PATCH] iio: acpi: Add ACPI0008 Ambient Light Sensor
Date: Wed, 29 Apr 2015 13:51:21 +0200 [thread overview]
Message-ID: <1625165.pchJQFHZZe@xps13> (raw)
In-Reply-To: <1430306845-7117-1-git-send-email-gabriele.mzt@gmail.com>
On Wednesday 29 April 2015 13:27:25 Gabriele Mazzotta wrote:
> Add basic implementation of the ACPI0008 Ambient Light Sensor driver.
> This driver currently supports only the ALI property, yet is ready to
> be easily extended to handle ALC, ALT, ALP ones as well.
>
> Signed-off-by: Martin Liska <marxin.liska@gmail.com>
> Signed-off-by: Marek Vasut <marex@denx.de>
> Signed-off-by: Gabriele Mazzotta <gabriele.mzt@gmail.com>
> Cc: Zhang Rui <rui.zhang@intel.com>
> ---
> This continues http://marc.info/?t=140163463200002
> I've made few adjustments over the original patch:
>
> - Code aligned with 4.1-rc1 and cleaned up
> - Use signed integers to store values: sensors report 32bit signed
> values. In particular, -1 is reported when the current reading
> is above the supported range of sensitivity.
>
> Most of the changes are just a consequence of the changes in the
> iio subsystem.
>
> Gabriele
I'm sorry, I've just noticed that I haven't changed the value of
realbits in acpi_als_channels. This makes me wonder what would be the
proper value, given that this is a generic driver and all the
information I have are those in the ACPI specification (which states
what I reported here above).
Should I just set realbits to 32?
Thanks,
Gabriele
next prev parent reply other threads:[~2015-04-29 11:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-29 11:27 [PATCH] iio: acpi: Add ACPI0008 Ambient Light Sensor Gabriele Mazzotta
2015-04-29 11:51 ` Gabriele Mazzotta [this message]
2015-04-29 14:33 ` Marek Vasut
2015-04-29 15:36 ` Gabriele Mazzotta
2015-04-30 9:44 ` Marek Vasut
2015-04-30 11:27 ` Gabriele Mazzotta
2015-04-30 11:30 ` Marek Vasut
2015-04-30 12:24 ` Daniel Baluta
2015-04-30 19:14 ` Gabriele Mazzotta
2015-04-30 20:33 ` Paul Bolle
2015-04-30 20:58 ` Marek Vasut
2015-05-01 16:12 ` Gabriele Mazzotta
2015-05-02 11:22 ` Jonathan Cameron
2015-05-02 11:25 ` Jonathan Cameron
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=1625165.pchJQFHZZe@xps13 \
--to=gabriele.mzt@gmail.com \
--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=marex@denx.de \
--cc=marxin.liska@gmail.com \
--cc=pmeerw@pmeerw.net \
--cc=rui.zhang@intel.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