From: Lars-Peter Clausen <lars@metafoo.de>
To: Marek Vasut <marex@denx.de>
Cc: linux-iio@vger.kernel.org, Martin Liska <marxin.liska@gmail.com>,
Jonathan Cameron <jic23@kernel.org>,
Zhang Rui <rui.zhang@intel.com>
Subject: Re: [PATCH V4] iio: acpi: Add ACPI0008 ALS driver
Date: Mon, 28 Jan 2013 15:10:47 +0100 [thread overview]
Message-ID: <510686E7.3050605@metafoo.de> (raw)
In-Reply-To: <1359250167-782-1-git-send-email-marex@denx.de>
On 01/27/2013 02:29 AM, Marek Vasut wrote:
> From: Martin Liska <marxin.liska@gmail.com>
>
> 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>
> Cc: Jonathan Cameron <jic23@kernel.org>
> Cc: Zhang Rui <rui.zhang@intel.com>
Hi,
Looks good, except for the trigger/buffer support. Which for one can't be
enabled since you didn't set the INDIO_BUFFER_TRIGGERED mode flag. But also
the implementation itself seems to have a few rough edges.
> ---
> drivers/staging/iio/light/Kconfig | 10 ++
> drivers/staging/iio/light/Makefile | 1 +
> drivers/staging/iio/light/acpi-als.c | 320 ++++++++++++++++++++++++++++++++++
> 3 files changed, 331 insertions(+)
> create mode 100644 drivers/staging/iio/light/acpi-als.c
>
> V2: Fix the channel mask, so it's really reading RAW data.
> V3: Put scan timestamp into the buffer only when enabled,
> Set the light sensor ID to 0 instead of 1
> V4: Select IIO_TRIGGERED_BUFFER as we need it here
>
> diff --git a/drivers/staging/iio/light/Kconfig b/drivers/staging/iio/light/Kconfig
> index 4bed30e..9c3d146 100644
> --- a/drivers/staging/iio/light/Kconfig
> +++ b/drivers/staging/iio/light/Kconfig
> @@ -50,4 +50,14 @@ config TSL2x7x
> tmd2672, tsl2772, tmd2772 devices.
> Provides iio_events and direct access via sysfs.
>
> +config ACPI_ALS
> + tristate "ACPI Ambient Light Sensor"
> + depends on ACPI
> + select IIO_TRIGGERED_BUFFER
> + help
> + Support for the ACPI0008 Ambient Light Sensor.
> +
> + This driver can also be built as a module. If so, the module
> + will be called acpi-als.
> +
Keep the entries in alphabetical order.
> endmenu
> diff --git a/drivers/staging/iio/light/Makefile b/drivers/staging/iio/light/Makefile
> index 141af1e..13090e6 100644
> --- a/drivers/staging/iio/light/Makefile
> +++ b/drivers/staging/iio/light/Makefile
> @@ -7,3 +7,4 @@ obj-$(CONFIG_SENSORS_ISL29018) += isl29018.o
> obj-$(CONFIG_SENSORS_ISL29028) += isl29028.o
> obj-$(CONFIG_TSL2583) += tsl2583.o
> obj-$(CONFIG_TSL2x7x) += tsl2x7x_core.o
> +obj-$(CONFIG_ACPI_ALS) += acpi-als.o
Same here.
> diff --git a/drivers/staging/iio/light/acpi-als.c b/drivers/staging/iio/light/acpi-als.c
> new file mode 100644
> index 0000000..6140613
> --- /dev/null
> +++ b/drivers/staging/iio/light/acpi-als.c
> @@ -0,0 +1,320 @@
[...]
> +
> +static void acpi_als_notify(struct acpi_device *device, u32 event)
> +{
> + struct iio_dev *iio = acpi_driver_data(device);
> + struct acpi_als *als = iio_priv(iio);
> + uint16_t *buffer = als->evt_buffer;
> + s64 time_ns = iio_get_time_ns();
> +
> + mutex_lock(&als->lock);
> +
> + memset(buffer, 0, als->evt_buffer_len);
> +
> + switch (event) {
> + case ACPI_ALS_NOTIFY_ILLUMINANCE:
> + *buffer++ = als_read_value(als, ACPI_ALS_ILLUMINANCE);
> + break;
> + default:
> + /* Unhandled event */
> + dev_dbg(&device->dev, "Unhandled ACPI ALS event (%08x)!\n",
> + event);
> + return;
> + }
> +
> + if (iio->scan_timestamp)
> + *(s64 *)ALIGN((uintptr_t)buffer, sizeof(s64)) = time_ns;
> +
> + if (iio_buffer_enabled(iio))
> + iio_push_to_buffer(iio->buffer, (uint8_t *)als->evt_buffer);
> +
Normally you'd call iio_trigger_poll here and have the buffer handling in
acpi_als_trigger_handler. This allows you for example to use other triggers,
e.g. a timer based trigger.
> + mutex_unlock(&als->lock);
> +}
[...]
> +
> +static int acpi_als_trigger_init(struct iio_dev *iio)
> +{
> + struct iio_trigger *trig;
> + int ret;
> +
> + trig = iio_trigger_alloc("%s-dev%i", iio->name, iio->id);
> + if (!trig)
> + return -ENOMEM;
> +
> + trig->dev.parent = iio->dev.parent;
> + trig->private_data = iio;
> + trig->ops = &acpi_als_trigger_ops;
> +
> + ret = iio_trigger_register(trig);
> + if (ret) {
> + iio_trigger_free(trig);
> + return ret;
> + }
> +
> + iio->trig = trig;
als->trig = trig;
> +
> + return 0;
> +}
> +
> +static void acpi_als_trigger_remove(struct iio_dev *iio)
> +{
> + iio_trigger_unregister(iio->trig);
> + iio_trigger_free(iio->trig);
iio->trig, is the trigger that is currently assigned to the device. You
should really use als->trig here.
> +}
> +
> +static int acpi_als_add(struct acpi_device *device)
> +{
> + struct acpi_als *als;
> + struct iio_dev *iio;
> + struct device *dev = &device->dev;
> + int ret;
> +
> + /*
> + * The event buffer contains timestamp and all the data from
> + * the ACPI0008 block. There are multiple, but so far we only
> + * support _ALI (illuminance). Yes, we're ready for more!
> + */
> + uint16_t *evt_buffer;
> + const unsigned int evt_sources = 1;
> + const unsigned int evt_buffer_size = sizeof(int64_t) +
> + (sizeof(uint16_t) * evt_sources);
> +
> + evt_buffer = devm_kzalloc(dev, evt_buffer_size, GFP_KERNEL);
> + if (!evt_buffer)
> + return -ENOMEM;
> +
> + iio = iio_device_alloc(sizeof(*als));
> + if (!iio) {
> + dev_err(dev, "Failed to allocate IIO device\n");
> + return -ENOMEM;
> + }
> +
> + als = iio_priv(iio);
> +
> + device->driver_data = iio;
> + als->device = device;
> + als->evt_buffer = evt_buffer;
> + mutex_init(&als->lock);
> +
> + iio->name = ACPI_ALS_DEVICE_NAME;
> + iio->dev.parent = dev;
> + iio->info = &acpi_als_info;
> + iio->modes = INDIO_DIRECT_MODE;
INDIO_BUFFER_TRIGGERED
> + iio->channels = acpi_als_channels;
> + iio->num_channels = ARRAY_SIZE(acpi_als_channels);
> +
> + ret = iio_triggered_buffer_setup(iio, &iio_pollfunc_store_time,
> + &acpi_als_trigger_handler, NULL);
> + if (ret)
> + goto err_iio;
> +
> + ret = acpi_als_trigger_init(iio);
> + if (ret)
> + goto err_trig;
> +
> + ret = iio_device_register(iio);
> + if (ret < 0)
> + goto err_dev;
> +
> + return 0;
> +
> +err_dev:
> + acpi_als_trigger_remove(iio);
> +err_trig:
> + iio_triggered_buffer_cleanup(iio);
> +err_iio:
> + iio_device_free(iio);
> + return ret;
> +}
> +
[...]
> +
> +static struct acpi_driver acpi_als_driver = {
> + .name = "acpi_als",
> + .class = ACPI_ALS_CLASS,
> + .ids = acpi_als_device_ids,
> + .ops = {
> + .add = acpi_als_add,
> + .remove = acpi_als_remove,
> + .notify = acpi_als_notify,
> + },
> +};
> +
> +static int acpi_als_init(void)
> +{
> + return acpi_bus_register_driver(&acpi_als_driver);
> +}
> +
> +static void acpi_als_exit(void)
> +{
> + acpi_bus_unregister_driver(&acpi_als_driver);
> +}
> +
> +module_init(acpi_als_init);
> +module_exit(acpi_als_exit);
module_acpi_driver(acpi_als_driver);
next prev parent reply other threads:[~2013-01-28 14:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-27 1:29 [PATCH V4] iio: acpi: Add ACPI0008 ALS driver Marek Vasut
2013-01-28 14:10 ` Lars-Peter Clausen [this message]
2013-01-28 18:19 ` Marek Vasut
2013-01-28 21:33 ` Lars-Peter Clausen
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=510686E7.3050605@metafoo.de \
--to=lars@metafoo.de \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=marex@denx.de \
--cc=marxin.liska@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).