<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/drivers/iio/light/Kconfig, branch linux-5.4.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-5.4.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-5.4.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2022-12-08T10:23:02Z</updated>
<entry>
<title>iio: light: rpr0521: add missing Kconfig dependencies</title>
<updated>2022-12-08T10:23:02Z</updated>
<author>
<name>Paul Gazzillo</name>
</author>
<published>2022-11-10T21:47:29Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=2b916ee1d37cc8e2da9bfe50a55390d5004843bd'/>
<id>urn:sha1:2b916ee1d37cc8e2da9bfe50a55390d5004843bd</id>
<content type='text'>
[ Upstream commit 6ac12303572ef9ace5603c2c07f5f1b00a33f580 ]

Fix an implicit declaration of function error for rpr0521 under some configs

When CONFIG_RPR0521 is enabled without CONFIG_IIO_TRIGGERED_BUFFER,
the build results in "implicit declaration of function" errors, e.g.,
  drivers/iio/light/rpr0521.c:434:3: error: implicit declaration of function
           'iio_trigger_poll_chained' [-Werror=implicit-function-declaration]
    434 |   iio_trigger_poll_chained(data-&gt;drdy_trigger0);
        |   ^~~~~~~~~~~~~~~~~~~~~~~~

This fix adds select dependencies to RPR0521's configuration declaration.

Fixes: e12ffd241c00 ("iio: light: rpr0521 triggered buffer")
Signed-off-by: Paul Gazzillo &lt;paul@pgazz.com&gt;
Link: https://bugzilla.kernel.org/show_bug.cgi?id=216678
Reviewed-by: Andy Shevchenko &lt;andriy.shevchenko@linux.intel.com&gt;
Link: https://lore.kernel.org/r/20221110214729.ls5ixav5kxpeftk7@device
Signed-off-by: Jonathan Cameron &lt;Jonathan.Cameron@huawei.com&gt;
Signed-off-by: Sasha Levin &lt;sashal@kernel.org&gt;
</content>
</entry>
<entry>
<title>iio: light: fix kconfig dependency bug for VCNL4035</title>
<updated>2020-11-24T12:29:21Z</updated>
<author>
<name>Necip Fazil Yildiran</name>
</author>
<published>2020-11-02T22:35:24Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=7f76c608135e5f288db460235faee11ff378bb9a'/>
<id>urn:sha1:7f76c608135e5f288db460235faee11ff378bb9a</id>
<content type='text'>
commit 44a146a44f656fc03d368c1b9248d29a128cd053 upstream.

When VCNL4035 is enabled and IIO_BUFFER is disabled, it results in the
following Kbuild warning:

WARNING: unmet direct dependencies detected for IIO_TRIGGERED_BUFFER
  Depends on [n]: IIO [=y] &amp;&amp; IIO_BUFFER [=n]
  Selected by [y]:
  - VCNL4035 [=y] &amp;&amp; IIO [=y] &amp;&amp; I2C [=y]

The reason is that VCNL4035 selects IIO_TRIGGERED_BUFFER without depending
on or selecting IIO_BUFFER while IIO_TRIGGERED_BUFFER depends on
IIO_BUFFER. This can also fail building the kernel.

Honor the kconfig dependency to remove unmet direct dependency warnings
and avoid any potential build failures.

Fixes: 55707294c4eb ("iio: light: Add support for vishay vcnl4035")
Signed-off-by: Necip Fazil Yildiran &lt;fazilyildiran@gmail.com&gt;
Link: https://bugzilla.kernel.org/show_bug.cgi?id=209883
Link: https://lore.kernel.org/r/20201102223523.572461-1-fazilyildiran@gmail.com
Cc: &lt;stable@vger.kernel.org&gt;
Signed-off-by: Jonathan Cameron &lt;Jonathan.Cameron@huawei.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>iio: Fix an undefied reference error in noa1305_probe</title>
<updated>2019-10-09T18:11:29Z</updated>
<author>
<name>zhong jiang</name>
</author>
<published>2019-09-23T02:04:32Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=a26e0fbe06e20077afdaa40d1a90092f16b0bc67'/>
<id>urn:sha1:a26e0fbe06e20077afdaa40d1a90092f16b0bc67</id>
<content type='text'>
I hit the following error when compile the kernel.

drivers/iio/light/noa1305.o: In function `noa1305_probe':
noa1305.c:(.text+0x65): undefined reference to `__devm_regmap_init_i2c'
make: *** [vmlinux] Error 1

Signed-off-by: zhong jiang &lt;zhongjiang@huawei.com&gt;
Cc: &lt;Stable@vger.kernel.org&gt;
Signed-off-by: Jonathan Cameron &lt;Jonathan.Cameron@huawei.com&gt;
</content>
</entry>
<entry>
<title>iio: light: noa1305: Add support for NOA1305</title>
<updated>2019-08-05T16:24:18Z</updated>
<author>
<name>Martyn Welch</name>
</author>
<published>2019-08-02T11:42:28Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=741172d18e8a9cffb5c9c9c236d1311b6fcf6111'/>
<id>urn:sha1:741172d18e8a9cffb5c9c9c236d1311b6fcf6111</id>
<content type='text'>
This driver adds the initial support for the ON Semiconductor
NOA1305 Ambient Light Sensor.

Originally written by Sergei Miroshnichenko. Found here:
  https://github.com/EmcraftSystems/linux-upstream/commit/196d6cf897e632d2cb82d45484bd7a1bfdd5b6d9

Signed-off-by: Sergei M &lt;fizik1@yandex.com&gt;
Signed-off-by: Martyn Welch &lt;martyn.welch@collabora.com&gt;
Signed-off-by: Jonathan Cameron &lt;Jonathan.Cameron@huawei.com&gt;
</content>
</entry>
<entry>
<title>treewide: Add SPDX license identifier - Makefile/Kconfig</title>
<updated>2019-05-21T08:50:46Z</updated>
<author>
<name>Thomas Gleixner</name>
</author>
<published>2019-05-19T12:07:45Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=ec8f24b7faaf3d4799a7c3f4c1b87f6b02778ad1'/>
<id>urn:sha1:ec8f24b7faaf3d4799a7c3f4c1b87f6b02778ad1</id>
<content type='text'>
Add SPDX license identifiers to all Make/Kconfig files which:

 - Have no license information of any form

These files fall under the project license, GPL v2 only. The resulting SPDX
license identifier is:

  GPL-2.0-only

Signed-off-by: Thomas Gleixner &lt;tglx@linutronix.de&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>drivers: iio: Kconfig: pedantic cleanup</title>
<updated>2019-04-04T19:19:56Z</updated>
<author>
<name>Enrico Weigelt, metux IT consult</name>
</author>
<published>2019-03-06T14:52:23Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=d626be00e856c0cec3b5f420e7f061829538d63b'/>
<id>urn:sha1:d626be00e856c0cec3b5f420e7f061829538d63b</id>
<content type='text'>
Formatting of Kconfig files doesn't look so pretty, so just
take damp cloth and clean it up.

Signed-off-by: Enrico Weigelt, metux IT consult &lt;info@metux.net&gt;
Signed-off-by: Jonathan Cameron &lt;Jonathan.Cameron@huawei.com&gt;
</content>
</entry>
<entry>
<title>iio: light: add driver for MAX44009</title>
<updated>2019-02-02T15:47:46Z</updated>
<author>
<name>Robert Eshleman</name>
</author>
<published>2019-01-31T15:29:01Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=6aef699a7d7e53164eaac54da57012c8440f1485'/>
<id>urn:sha1:6aef699a7d7e53164eaac54da57012c8440f1485</id>
<content type='text'>
The MAX44009 is a low-power ambient light sensor from Maxim
Integrated. It differs from the MAX44000 in that it doesn't have
proximity sensing and that it requires far less current (1 micro-amp
vs 5 micro-amps). The register mapping and feature set between the
two are different enough to require a new driver for the MAX44009.

Developed and tested with a BeagleBone Black and UDOO Neo (i.MX6SX)

Supported features:

* Reading lux (processed value)

* Rising and falling illuminance threshold
  events

* Configuring integration time

https://datasheets.maximintegrated.com/en/ds/MAX44009.pdf

Signed-off-by: Robert Eshleman &lt;bobbyeshleman@gmail.com&gt;
Signed-off-by: Jonathan Cameron &lt;Jonathan.Cameron@huawei.com&gt;
</content>
</entry>
<entry>
<title>iio: light: Add support for vishay vcnl4035</title>
<updated>2018-11-16T18:32:29Z</updated>
<author>
<name>Parthiban Nallathambi</name>
</author>
<published>2018-11-07T17:08:20Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=55707294c4eb0d61054468ecccdddef5c5151fc0'/>
<id>urn:sha1:55707294c4eb0d61054468ecccdddef5c5151fc0</id>
<content type='text'>
Add support for VCNL4035, which is capable of Ambient light
sensing (ALS) and proximity function. This patch adds support
only for ALS function

Signed-off-by: Parthiban Nallathambi &lt;pn@denx.de&gt;
Reviewed-by: Andy Shevchenko &lt;andy.shevchenko@gmail.com&gt;
Signed-off-by: Jonathan Cameron &lt;Jonathan.Cameron@huawei.com&gt;
</content>
</entry>
<entry>
<title>iio: vcnl4000: add support for VCNL4200</title>
<updated>2018-07-29T11:19:28Z</updated>
<author>
<name>Tomas Novotny</name>
</author>
<published>2018-07-25T15:18:21Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=be38866fbb97f0ee2b144ab1de9ee2833a76e0fb'/>
<id>urn:sha1:be38866fbb97f0ee2b144ab1de9ee2833a76e0fb</id>
<content type='text'>
VCNL4200 is an integrated long distance (up to 1500mm) proximity and
ambient light sensor.

The support is very basic. There is no configuration of proximity and
ambient light sensing yet. Only the reading of both measured values is
done.

The reading of ambient light and proximity values is blocking. If you
request a new value too early, the driver waits for new value to be
ready.

Signed-off-by: Tomas Novotny &lt;tomas@novotny.cz&gt;
Signed-off-by: Jonathan Cameron &lt;Jonathan.Cameron@huawei.com&gt;
</content>
</entry>
<entry>
<title>iio: light: introduce si1133</title>
<updated>2018-07-23T18:18:11Z</updated>
<author>
<name>Maxime Roussin-Bélanger</name>
</author>
<published>2018-07-19T20:26:25Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=e01e7eaf37d865c72e2501a7b09e7a61317ce2d4'/>
<id>urn:sha1:e01e7eaf37d865c72e2501a7b09e7a61317ce2d4</id>
<content type='text'>
e-mail received from Silicon Lab to confirm that the licensing
isn't a problem.

"
Dear Maxime Roussin-Belanger,

The LUX calculation code only works with Si1133.
As long as the software is used with Silicon Lab's sensor product,
I don't see any problem.

Regards,
Tony
"

Signed-off-by: Maxime Roussin-Bélanger &lt;maxime.roussinbelanger@gmail.com&gt;
Reviewed-by: Jean-Francois Dagenais &lt;jeff.dagenais@gmail.com&gt;
Signed-off-by: Jonathan Cameron &lt;Jonathan.Cameron@huawei.com&gt;
</content>
</entry>
</feed>
