linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Olivier Dugas <olivier.dugas.1@gmail.com>
To: Peter Meerwald-Stadler <pmeerw@pmeerw.net>
Cc: jic23@kernel.org, leonard.crestez@intel.com, linux-iio@vger.kernel.org
Subject: Re: SI1133 light sensor: Is there anything to refer to?
Date: Mon, 19 Jun 2017 12:04:07 -0400	[thread overview]
Message-ID: <ec438ed1-2b6a-0f23-ed9d-eb6bcbbd3b05@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1706191652040.15475@vps.pmeerw.net>

Excellent news. I'll keep a watch for this new driver to show up.
In the meantime, we just got the sensor to respond correctly using 
i2cget|set commands.

FYI, the issue we had was that the reset value of ADCCONFIGx is not 0x00 
(as specified by the datasheet), but 0x0f, which selected no photodiode. 
Hence, we received only noise values.

Thanks a lot and have a good day

-- 

Olivier Dugas

On 17-06-19 11:10 AM, Peter Meerwald-Stadler wrote:
> Hello Olivier,
>
>> We've recently been trying to make the SI1133 light sensor work according to
>> what's written in its datasheet. Unfortunately many questions remain and the
>> si1145.c driver seems largely different from si1133. We believe that any code
>> sample would be of a great help. Are you aware of any driver, unmerged patch
>> or other code sample for this sensor?
> the si1133 belongs in the same family as the si1153 which has a different
> register layout than the previous chips, so I think a separate driver is
> needed
>
> I do have an eval board for the si1153 and started a driver, but it's not
> ready for submission (yet), the si1133 should be a lot simpler than the
> si1153
>
> regards, p.
>

  reply	other threads:[~2017-06-19 16:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-19 14:42 SI1133 light sensor: Is there anything to refer to? Olivier Dugas
2017-06-19 15:10 ` Peter Meerwald-Stadler
2017-06-19 16:04   ` Olivier Dugas [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-05-18 17:42 Maxime Roussin-Bélanger

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=ec438ed1-2b6a-0f23-ed9d-eb6bcbbd3b05@gmail.com \
    --to=olivier.dugas.1@gmail.com \
    --cc=jic23@kernel.org \
    --cc=leonard.crestez@intel.com \
    --cc=linux-iio@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).