linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@cam.ac.uk>
To: Marek Vasut <marex@denx.de>
Cc: "Martin Liška" <marxin.liska@gmail.com>,
	platform-driver-x86@vger.kernel.org, linux-iio@vger.kernel.org,
	"Zhang Rui" <rui.zhang@intel.com>,
	"Corentin Chary" <corentin.chary@gmail.com>,
	joeyli <jlee@suse.com>, "Len Brown" <len.brown@intel.com>,
	pavel@denx.de, "Jonathan Cameron" <jic23@kernel.org>,
	"Jon Brenner" <jbrenner@taosinc.com>,
	"Peter Meerwald" <pmeerw@pmeerw.net>
Subject: Re: ACPI ambient light sensor
Date: Mon, 09 Jul 2012 14:29:38 +0100	[thread overview]
Message-ID: <4FFADCC2.6080006@cam.ac.uk> (raw)
In-Reply-To: <201207082228.14318.marex@denx.de>

cc'd Jon Brenner and Peter Meerwald.
>
>> Hello,
>>     Iconia Tab W500 contains Ambient Light Sensor (hid 0008), I started
>> implementing IIO device drive having following questions:
>>
>>     - chip could offer following variables: illuminance, color chromaticity
>>     and color temperature, how should I connect last 2 vars to any of IIO
>>     CHANNEL types?
Jon's recent proposed additional modifiers cover temperature. 
Chromaticity is a new one I think though?
>>     - I'm not sure how to connect an illuminance mapping to IIO
>>     infrastructure?
When you say mapping, what do you mean? That term tends to get used
for quite a few different things...
>
> See IIO_DEVICE_ATTR() maybe ?
>
>> Thank you,
>> Martin Liška
>
> Best regards,
> Marek Vasut
> --
> To unsubscribe from this list: send the line "unsubscribe linux-iio" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

  reply	other threads:[~2012-07-09 13:29 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-08 20:03 ACPI ambient light sensor Martin Liška
2012-07-08 20:28 ` Marek Vasut
2012-07-09 13:29   ` Jonathan Cameron [this message]
2012-09-11  7:48     ` Martin Liška
2012-09-11  8:27       ` Marek Vasut
2012-09-11  8:35       ` Peter Meerwald
2012-09-11  9:21       ` Marek Vasut
2012-10-21 17:02         ` Martin Liška
2012-10-21 17:32           ` Marek Vasut
2012-10-21 18:05           ` Jonathan Cameron
2012-10-27 16:39             ` Martin Liška
2012-10-27 17:08               ` Jonathan Cameron
2012-10-27 18:00                 ` Corentin Chary
2012-11-29  2:46                   ` ACPI ALS patch marxin.liska
2012-11-29  2:46                     ` [PATCH] ACPI ALS driver for iio introduced marxin.liska
2012-11-29  8:02                       ` Corentin Chary
2012-11-29 10:18                         ` Lars-Peter Clausen
     [not found]                         ` <CAObPJ3NM7mn+pXJ801hC2Dn7t9kqp4X_FuD8TSmJ6-eH7UP8pA@mail.gmail.com>
2012-12-02 11:20                           ` Corentin Chary
2012-11-29 10:15                       ` Lars-Peter Clausen
2012-12-01 16:46                         ` Martin Liška
2012-12-02 13:24                           ` 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=4FFADCC2.6080006@cam.ac.uk \
    --to=jic23@cam.ac.uk \
    --cc=corentin.chary@gmail.com \
    --cc=jbrenner@taosinc.com \
    --cc=jic23@kernel.org \
    --cc=jlee@suse.com \
    --cc=len.brown@intel.com \
    --cc=linux-iio@vger.kernel.org \
    --cc=marex@denx.de \
    --cc=marxin.liska@gmail.com \
    --cc=pavel@denx.de \
    --cc=platform-driver-x86@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).