isl (4)

Leading comments

Copyright (c) 2015 Michael Gmelin <freebsd@grem.de>
All rights reserved.

Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions
are met:
1. Redistributions of source code must retain the above copyright
   notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright
   notice, this list of conditions and the following disclaimer in the
   docume...

(The comments found at the beginning of the groff file "man4/isl.4freebsd".)

NAME

isl - Intersil(TM) I2C ISL29018 sensor driver

SYNOPSIS

To compile this driver into the kernel, place the following lines into the kernel configuration file:

device isl device ig4 device smbus

Alternatively, to load the driver as a module at boot time, place the following line in loader.conf5:

isl_load="YES"
ig4_load="YES"

DESCRIPTION

The driver provides access to sensor data provided by the Intersil(TM) I2C ISL29018 Digital Ambient Light Sensor and Proximity Sensor with Interrupt Function. Functionality is basic and provided through the sysctl(8) interface.

SYSCTL VARIABLES

The following sysctl(8) variables are available:

dev.isl.X.als

Current ALS (Ambient Light Sensor) readout.

dev.isl.X.ir

Current IR (InfraRed) sensor readout.

dev.isl.X.prox

Current proximity sensor readout.

dev.isl.X.resolution

Current sensor resolution.

dev.isl.X.range

Current sensor range.

EXAMPLES

Ambient light sensor read out

$ sysctl dev.isl.0.als
dev.isl.0.als: 64

Automatically adjust brightness

This requires the port graphics/intel-backlight and only works with laptops using a supported Intel(R) GPU.

$ pkg install intel-backlight
$ sh /usr/local/share/examples/intel-backlight/isl_backlight.sh

SEE ALSO

ig4(4), smbus(4)

AUTHORS

An -nosplit The driver was written by An Michael Gmelin Aq Mt freebsd@grem.de .

This manual page was written by An Michael Gmelin Aq Mt freebsd@grem.de .

BUGS

The driver detects the device based on its I2C address (0x44). This might have unforeseen consequences if the initialization sequence is sent to an unknown device at that address.