2017-12-12 10:47:20 +03:00
|
|
|
// SPDX-License-Identifier: GPL-2.0
|
|
|
|
// SPI driven IR LED device driver
|
|
|
|
//
|
|
|
|
// Copyright (c) 2016 Samsung Electronics Co., Ltd.
|
2018-04-13 16:48:29 +03:00
|
|
|
// Copyright (c) Andi Shyti <andi@etezian.org>
|
[media] rc: add support for IR LEDs driven through SPI
The ir-spi is a simple device driver which supports the
connection between an IR LED and the MOSI line of an SPI device.
The driver, indeed, uses the SPI framework to stream the raw data
provided by userspace through an rc character device. The chardev
is handled by the LIRC framework and its functionality basically
provides:
- write: the driver gets a pulse/space signal and translates it
to a binary signal that will be streamed to the IR led through
the SPI framework.
- set frequency: sets the frequency whith which the data should
be sent. This is handle with ioctl with the
LIRC_SET_SEND_CARRIER flag (as per lirc documentation)
- set duty cycle: this is also handled with ioctl with the
LIRC_SET_SEND_DUTY_CYCLE flag. The driver handles duty cycles
of 50%, 60%, 70%, 75%, 80% and 90%, calculated on 16bit data.
The character device is created under /dev/lircX name, where X is
and ID assigned by the LIRC framework.
Example of usage:
fd = open("/dev/lirc0", O_RDWR);
if (fd < 0)
return -1;
val = 608000;
ret = ioctl(fd, LIRC_SET_SEND_CARRIER, &val);
if (ret < 0)
return -1;
val = 60;
ret = ioctl(fd, LIRC_SET_SEND_DUTY_CYCLE, &val);
if (ret < 0)
return -1;
n = write(fd, buffer, BUF_LEN);
if (n < 0 || n != BUF_LEN)
ret = -1;
close(fd);
Signed-off-by: Andi Shyti <andi.shyti@samsung.com>
Signed-off-by: Sean Young <sean@mess.org>
Signed-off-by: Mauro Carvalho Chehab <mchehab@s-opensource.com>
2016-12-16 09:12:18 +03:00
|
|
|
|
|
|
|
#include <linux/delay.h>
|
|
|
|
#include <linux/fs.h>
|
|
|
|
#include <linux/module.h>
|
|
|
|
#include <linux/mutex.h>
|
|
|
|
#include <linux/of_gpio.h>
|
|
|
|
#include <linux/regulator/consumer.h>
|
|
|
|
#include <linux/spi/spi.h>
|
|
|
|
#include <media/rc-core.h>
|
|
|
|
|
|
|
|
#define IR_SPI_DRIVER_NAME "ir-spi"
|
|
|
|
|
|
|
|
#define IR_SPI_DEFAULT_FREQUENCY 38000
|
|
|
|
#define IR_SPI_MAX_BUFSIZE 4096
|
|
|
|
|
|
|
|
struct ir_spi_data {
|
|
|
|
u32 freq;
|
|
|
|
bool negated;
|
|
|
|
|
|
|
|
u16 tx_buf[IR_SPI_MAX_BUFSIZE];
|
|
|
|
u16 pulse;
|
|
|
|
u16 space;
|
|
|
|
|
|
|
|
struct rc_dev *rc;
|
|
|
|
struct spi_device *spi;
|
|
|
|
struct regulator *regulator;
|
|
|
|
};
|
|
|
|
|
|
|
|
static int ir_spi_tx(struct rc_dev *dev,
|
|
|
|
unsigned int *buffer, unsigned int count)
|
|
|
|
{
|
|
|
|
int i;
|
|
|
|
int ret;
|
|
|
|
unsigned int len = 0;
|
|
|
|
struct ir_spi_data *idata = dev->priv;
|
|
|
|
struct spi_transfer xfer;
|
|
|
|
|
|
|
|
/* convert the pulse/space signal to raw binary signal */
|
|
|
|
for (i = 0; i < count; i++) {
|
2017-05-07 04:00:11 +03:00
|
|
|
unsigned int periods;
|
[media] rc: add support for IR LEDs driven through SPI
The ir-spi is a simple device driver which supports the
connection between an IR LED and the MOSI line of an SPI device.
The driver, indeed, uses the SPI framework to stream the raw data
provided by userspace through an rc character device. The chardev
is handled by the LIRC framework and its functionality basically
provides:
- write: the driver gets a pulse/space signal and translates it
to a binary signal that will be streamed to the IR led through
the SPI framework.
- set frequency: sets the frequency whith which the data should
be sent. This is handle with ioctl with the
LIRC_SET_SEND_CARRIER flag (as per lirc documentation)
- set duty cycle: this is also handled with ioctl with the
LIRC_SET_SEND_DUTY_CYCLE flag. The driver handles duty cycles
of 50%, 60%, 70%, 75%, 80% and 90%, calculated on 16bit data.
The character device is created under /dev/lircX name, where X is
and ID assigned by the LIRC framework.
Example of usage:
fd = open("/dev/lirc0", O_RDWR);
if (fd < 0)
return -1;
val = 608000;
ret = ioctl(fd, LIRC_SET_SEND_CARRIER, &val);
if (ret < 0)
return -1;
val = 60;
ret = ioctl(fd, LIRC_SET_SEND_DUTY_CYCLE, &val);
if (ret < 0)
return -1;
n = write(fd, buffer, BUF_LEN);
if (n < 0 || n != BUF_LEN)
ret = -1;
close(fd);
Signed-off-by: Andi Shyti <andi.shyti@samsung.com>
Signed-off-by: Sean Young <sean@mess.org>
Signed-off-by: Mauro Carvalho Chehab <mchehab@s-opensource.com>
2016-12-16 09:12:18 +03:00
|
|
|
int j;
|
2017-03-27 16:34:35 +03:00
|
|
|
u16 val;
|
[media] rc: add support for IR LEDs driven through SPI
The ir-spi is a simple device driver which supports the
connection between an IR LED and the MOSI line of an SPI device.
The driver, indeed, uses the SPI framework to stream the raw data
provided by userspace through an rc character device. The chardev
is handled by the LIRC framework and its functionality basically
provides:
- write: the driver gets a pulse/space signal and translates it
to a binary signal that will be streamed to the IR led through
the SPI framework.
- set frequency: sets the frequency whith which the data should
be sent. This is handle with ioctl with the
LIRC_SET_SEND_CARRIER flag (as per lirc documentation)
- set duty cycle: this is also handled with ioctl with the
LIRC_SET_SEND_DUTY_CYCLE flag. The driver handles duty cycles
of 50%, 60%, 70%, 75%, 80% and 90%, calculated on 16bit data.
The character device is created under /dev/lircX name, where X is
and ID assigned by the LIRC framework.
Example of usage:
fd = open("/dev/lirc0", O_RDWR);
if (fd < 0)
return -1;
val = 608000;
ret = ioctl(fd, LIRC_SET_SEND_CARRIER, &val);
if (ret < 0)
return -1;
val = 60;
ret = ioctl(fd, LIRC_SET_SEND_DUTY_CYCLE, &val);
if (ret < 0)
return -1;
n = write(fd, buffer, BUF_LEN);
if (n < 0 || n != BUF_LEN)
ret = -1;
close(fd);
Signed-off-by: Andi Shyti <andi.shyti@samsung.com>
Signed-off-by: Sean Young <sean@mess.org>
Signed-off-by: Mauro Carvalho Chehab <mchehab@s-opensource.com>
2016-12-16 09:12:18 +03:00
|
|
|
|
2017-05-07 04:00:11 +03:00
|
|
|
periods = DIV_ROUND_CLOSEST(buffer[i] * idata->freq, 1000000);
|
|
|
|
|
|
|
|
if (len + periods >= IR_SPI_MAX_BUFSIZE)
|
[media] rc: add support for IR LEDs driven through SPI
The ir-spi is a simple device driver which supports the
connection between an IR LED and the MOSI line of an SPI device.
The driver, indeed, uses the SPI framework to stream the raw data
provided by userspace through an rc character device. The chardev
is handled by the LIRC framework and its functionality basically
provides:
- write: the driver gets a pulse/space signal and translates it
to a binary signal that will be streamed to the IR led through
the SPI framework.
- set frequency: sets the frequency whith which the data should
be sent. This is handle with ioctl with the
LIRC_SET_SEND_CARRIER flag (as per lirc documentation)
- set duty cycle: this is also handled with ioctl with the
LIRC_SET_SEND_DUTY_CYCLE flag. The driver handles duty cycles
of 50%, 60%, 70%, 75%, 80% and 90%, calculated on 16bit data.
The character device is created under /dev/lircX name, where X is
and ID assigned by the LIRC framework.
Example of usage:
fd = open("/dev/lirc0", O_RDWR);
if (fd < 0)
return -1;
val = 608000;
ret = ioctl(fd, LIRC_SET_SEND_CARRIER, &val);
if (ret < 0)
return -1;
val = 60;
ret = ioctl(fd, LIRC_SET_SEND_DUTY_CYCLE, &val);
if (ret < 0)
return -1;
n = write(fd, buffer, BUF_LEN);
if (n < 0 || n != BUF_LEN)
ret = -1;
close(fd);
Signed-off-by: Andi Shyti <andi.shyti@samsung.com>
Signed-off-by: Sean Young <sean@mess.org>
Signed-off-by: Mauro Carvalho Chehab <mchehab@s-opensource.com>
2016-12-16 09:12:18 +03:00
|
|
|
return -EINVAL;
|
|
|
|
|
|
|
|
/*
|
|
|
|
* the first value in buffer is a pulse, so that 0, 2, 4, ...
|
|
|
|
* contain a pulse duration. On the contrary, 1, 3, 5, ...
|
|
|
|
* contain a space duration.
|
|
|
|
*/
|
|
|
|
val = (i % 2) ? idata->space : idata->pulse;
|
2017-05-07 04:00:11 +03:00
|
|
|
for (j = 0; j < periods; j++)
|
[media] rc: add support for IR LEDs driven through SPI
The ir-spi is a simple device driver which supports the
connection between an IR LED and the MOSI line of an SPI device.
The driver, indeed, uses the SPI framework to stream the raw data
provided by userspace through an rc character device. The chardev
is handled by the LIRC framework and its functionality basically
provides:
- write: the driver gets a pulse/space signal and translates it
to a binary signal that will be streamed to the IR led through
the SPI framework.
- set frequency: sets the frequency whith which the data should
be sent. This is handle with ioctl with the
LIRC_SET_SEND_CARRIER flag (as per lirc documentation)
- set duty cycle: this is also handled with ioctl with the
LIRC_SET_SEND_DUTY_CYCLE flag. The driver handles duty cycles
of 50%, 60%, 70%, 75%, 80% and 90%, calculated on 16bit data.
The character device is created under /dev/lircX name, where X is
and ID assigned by the LIRC framework.
Example of usage:
fd = open("/dev/lirc0", O_RDWR);
if (fd < 0)
return -1;
val = 608000;
ret = ioctl(fd, LIRC_SET_SEND_CARRIER, &val);
if (ret < 0)
return -1;
val = 60;
ret = ioctl(fd, LIRC_SET_SEND_DUTY_CYCLE, &val);
if (ret < 0)
return -1;
n = write(fd, buffer, BUF_LEN);
if (n < 0 || n != BUF_LEN)
ret = -1;
close(fd);
Signed-off-by: Andi Shyti <andi.shyti@samsung.com>
Signed-off-by: Sean Young <sean@mess.org>
Signed-off-by: Mauro Carvalho Chehab <mchehab@s-opensource.com>
2016-12-16 09:12:18 +03:00
|
|
|
idata->tx_buf[len++] = val;
|
|
|
|
}
|
|
|
|
|
|
|
|
memset(&xfer, 0, sizeof(xfer));
|
|
|
|
|
2017-05-07 04:00:11 +03:00
|
|
|
xfer.speed_hz = idata->freq * 16;
|
[media] rc: add support for IR LEDs driven through SPI
The ir-spi is a simple device driver which supports the
connection between an IR LED and the MOSI line of an SPI device.
The driver, indeed, uses the SPI framework to stream the raw data
provided by userspace through an rc character device. The chardev
is handled by the LIRC framework and its functionality basically
provides:
- write: the driver gets a pulse/space signal and translates it
to a binary signal that will be streamed to the IR led through
the SPI framework.
- set frequency: sets the frequency whith which the data should
be sent. This is handle with ioctl with the
LIRC_SET_SEND_CARRIER flag (as per lirc documentation)
- set duty cycle: this is also handled with ioctl with the
LIRC_SET_SEND_DUTY_CYCLE flag. The driver handles duty cycles
of 50%, 60%, 70%, 75%, 80% and 90%, calculated on 16bit data.
The character device is created under /dev/lircX name, where X is
and ID assigned by the LIRC framework.
Example of usage:
fd = open("/dev/lirc0", O_RDWR);
if (fd < 0)
return -1;
val = 608000;
ret = ioctl(fd, LIRC_SET_SEND_CARRIER, &val);
if (ret < 0)
return -1;
val = 60;
ret = ioctl(fd, LIRC_SET_SEND_DUTY_CYCLE, &val);
if (ret < 0)
return -1;
n = write(fd, buffer, BUF_LEN);
if (n < 0 || n != BUF_LEN)
ret = -1;
close(fd);
Signed-off-by: Andi Shyti <andi.shyti@samsung.com>
Signed-off-by: Sean Young <sean@mess.org>
Signed-off-by: Mauro Carvalho Chehab <mchehab@s-opensource.com>
2016-12-16 09:12:18 +03:00
|
|
|
xfer.len = len * sizeof(*idata->tx_buf);
|
|
|
|
xfer.tx_buf = idata->tx_buf;
|
|
|
|
|
|
|
|
ret = regulator_enable(idata->regulator);
|
|
|
|
if (ret)
|
|
|
|
return ret;
|
|
|
|
|
|
|
|
ret = spi_sync_transfer(idata->spi, &xfer, 1);
|
|
|
|
if (ret)
|
|
|
|
dev_err(&idata->spi->dev, "unable to deliver the signal\n");
|
|
|
|
|
|
|
|
regulator_disable(idata->regulator);
|
|
|
|
|
|
|
|
return ret ? ret : count;
|
|
|
|
}
|
|
|
|
|
|
|
|
static int ir_spi_set_tx_carrier(struct rc_dev *dev, u32 carrier)
|
|
|
|
{
|
|
|
|
struct ir_spi_data *idata = dev->priv;
|
|
|
|
|
|
|
|
if (!carrier)
|
|
|
|
return -EINVAL;
|
|
|
|
|
|
|
|
idata->freq = carrier;
|
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
static int ir_spi_set_duty_cycle(struct rc_dev *dev, u32 duty_cycle)
|
|
|
|
{
|
|
|
|
struct ir_spi_data *idata = dev->priv;
|
2018-01-27 17:05:37 +03:00
|
|
|
int bits = (duty_cycle * 15) / 100;
|
[media] rc: add support for IR LEDs driven through SPI
The ir-spi is a simple device driver which supports the
connection between an IR LED and the MOSI line of an SPI device.
The driver, indeed, uses the SPI framework to stream the raw data
provided by userspace through an rc character device. The chardev
is handled by the LIRC framework and its functionality basically
provides:
- write: the driver gets a pulse/space signal and translates it
to a binary signal that will be streamed to the IR led through
the SPI framework.
- set frequency: sets the frequency whith which the data should
be sent. This is handle with ioctl with the
LIRC_SET_SEND_CARRIER flag (as per lirc documentation)
- set duty cycle: this is also handled with ioctl with the
LIRC_SET_SEND_DUTY_CYCLE flag. The driver handles duty cycles
of 50%, 60%, 70%, 75%, 80% and 90%, calculated on 16bit data.
The character device is created under /dev/lircX name, where X is
and ID assigned by the LIRC framework.
Example of usage:
fd = open("/dev/lirc0", O_RDWR);
if (fd < 0)
return -1;
val = 608000;
ret = ioctl(fd, LIRC_SET_SEND_CARRIER, &val);
if (ret < 0)
return -1;
val = 60;
ret = ioctl(fd, LIRC_SET_SEND_DUTY_CYCLE, &val);
if (ret < 0)
return -1;
n = write(fd, buffer, BUF_LEN);
if (n < 0 || n != BUF_LEN)
ret = -1;
close(fd);
Signed-off-by: Andi Shyti <andi.shyti@samsung.com>
Signed-off-by: Sean Young <sean@mess.org>
Signed-off-by: Mauro Carvalho Chehab <mchehab@s-opensource.com>
2016-12-16 09:12:18 +03:00
|
|
|
|
2018-01-27 17:05:37 +03:00
|
|
|
idata->pulse = GENMASK(bits, 0);
|
[media] rc: add support for IR LEDs driven through SPI
The ir-spi is a simple device driver which supports the
connection between an IR LED and the MOSI line of an SPI device.
The driver, indeed, uses the SPI framework to stream the raw data
provided by userspace through an rc character device. The chardev
is handled by the LIRC framework and its functionality basically
provides:
- write: the driver gets a pulse/space signal and translates it
to a binary signal that will be streamed to the IR led through
the SPI framework.
- set frequency: sets the frequency whith which the data should
be sent. This is handle with ioctl with the
LIRC_SET_SEND_CARRIER flag (as per lirc documentation)
- set duty cycle: this is also handled with ioctl with the
LIRC_SET_SEND_DUTY_CYCLE flag. The driver handles duty cycles
of 50%, 60%, 70%, 75%, 80% and 90%, calculated on 16bit data.
The character device is created under /dev/lircX name, where X is
and ID assigned by the LIRC framework.
Example of usage:
fd = open("/dev/lirc0", O_RDWR);
if (fd < 0)
return -1;
val = 608000;
ret = ioctl(fd, LIRC_SET_SEND_CARRIER, &val);
if (ret < 0)
return -1;
val = 60;
ret = ioctl(fd, LIRC_SET_SEND_DUTY_CYCLE, &val);
if (ret < 0)
return -1;
n = write(fd, buffer, BUF_LEN);
if (n < 0 || n != BUF_LEN)
ret = -1;
close(fd);
Signed-off-by: Andi Shyti <andi.shyti@samsung.com>
Signed-off-by: Sean Young <sean@mess.org>
Signed-off-by: Mauro Carvalho Chehab <mchehab@s-opensource.com>
2016-12-16 09:12:18 +03:00
|
|
|
|
|
|
|
if (idata->negated) {
|
|
|
|
idata->pulse = ~idata->pulse;
|
|
|
|
idata->space = 0xffff;
|
|
|
|
} else {
|
|
|
|
idata->space = 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
static int ir_spi_probe(struct spi_device *spi)
|
|
|
|
{
|
|
|
|
int ret;
|
|
|
|
u8 dc;
|
|
|
|
struct ir_spi_data *idata;
|
|
|
|
|
|
|
|
idata = devm_kzalloc(&spi->dev, sizeof(*idata), GFP_KERNEL);
|
|
|
|
if (!idata)
|
|
|
|
return -ENOMEM;
|
|
|
|
|
|
|
|
idata->regulator = devm_regulator_get(&spi->dev, "irda_regulator");
|
|
|
|
if (IS_ERR(idata->regulator))
|
|
|
|
return PTR_ERR(idata->regulator);
|
|
|
|
|
|
|
|
idata->rc = devm_rc_allocate_device(&spi->dev, RC_DRIVER_IR_RAW_TX);
|
|
|
|
if (!idata->rc)
|
|
|
|
return -ENOMEM;
|
|
|
|
|
|
|
|
idata->rc->tx_ir = ir_spi_tx;
|
|
|
|
idata->rc->s_tx_carrier = ir_spi_set_tx_carrier;
|
|
|
|
idata->rc->s_tx_duty_cycle = ir_spi_set_duty_cycle;
|
2017-07-01 19:13:19 +03:00
|
|
|
idata->rc->device_name = "IR SPI";
|
[media] rc: add support for IR LEDs driven through SPI
The ir-spi is a simple device driver which supports the
connection between an IR LED and the MOSI line of an SPI device.
The driver, indeed, uses the SPI framework to stream the raw data
provided by userspace through an rc character device. The chardev
is handled by the LIRC framework and its functionality basically
provides:
- write: the driver gets a pulse/space signal and translates it
to a binary signal that will be streamed to the IR led through
the SPI framework.
- set frequency: sets the frequency whith which the data should
be sent. This is handle with ioctl with the
LIRC_SET_SEND_CARRIER flag (as per lirc documentation)
- set duty cycle: this is also handled with ioctl with the
LIRC_SET_SEND_DUTY_CYCLE flag. The driver handles duty cycles
of 50%, 60%, 70%, 75%, 80% and 90%, calculated on 16bit data.
The character device is created under /dev/lircX name, where X is
and ID assigned by the LIRC framework.
Example of usage:
fd = open("/dev/lirc0", O_RDWR);
if (fd < 0)
return -1;
val = 608000;
ret = ioctl(fd, LIRC_SET_SEND_CARRIER, &val);
if (ret < 0)
return -1;
val = 60;
ret = ioctl(fd, LIRC_SET_SEND_DUTY_CYCLE, &val);
if (ret < 0)
return -1;
n = write(fd, buffer, BUF_LEN);
if (n < 0 || n != BUF_LEN)
ret = -1;
close(fd);
Signed-off-by: Andi Shyti <andi.shyti@samsung.com>
Signed-off-by: Sean Young <sean@mess.org>
Signed-off-by: Mauro Carvalho Chehab <mchehab@s-opensource.com>
2016-12-16 09:12:18 +03:00
|
|
|
idata->rc->driver_name = IR_SPI_DRIVER_NAME;
|
|
|
|
idata->rc->priv = idata;
|
|
|
|
idata->spi = spi;
|
|
|
|
|
|
|
|
idata->negated = of_property_read_bool(spi->dev.of_node,
|
|
|
|
"led-active-low");
|
|
|
|
ret = of_property_read_u8(spi->dev.of_node, "duty-cycle", &dc);
|
|
|
|
if (ret)
|
|
|
|
dc = 50;
|
|
|
|
|
|
|
|
/* ir_spi_set_duty_cycle cannot fail,
|
|
|
|
* it returns int to be compatible with the
|
|
|
|
* rc->s_tx_duty_cycle function
|
|
|
|
*/
|
|
|
|
ir_spi_set_duty_cycle(idata->rc, dc);
|
|
|
|
|
|
|
|
idata->freq = IR_SPI_DEFAULT_FREQUENCY;
|
|
|
|
|
|
|
|
return devm_rc_register_device(&spi->dev, idata->rc);
|
|
|
|
}
|
|
|
|
|
|
|
|
static int ir_spi_remove(struct spi_device *spi)
|
|
|
|
{
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
static const struct of_device_id ir_spi_of_match[] = {
|
|
|
|
{ .compatible = "ir-spi-led" },
|
|
|
|
{},
|
|
|
|
};
|
|
|
|
|
|
|
|
static struct spi_driver ir_spi_driver = {
|
|
|
|
.probe = ir_spi_probe,
|
|
|
|
.remove = ir_spi_remove,
|
|
|
|
.driver = {
|
|
|
|
.name = IR_SPI_DRIVER_NAME,
|
|
|
|
.of_match_table = ir_spi_of_match,
|
|
|
|
},
|
|
|
|
};
|
|
|
|
|
|
|
|
module_spi_driver(ir_spi_driver);
|
|
|
|
|
2018-04-13 16:48:29 +03:00
|
|
|
MODULE_AUTHOR("Andi Shyti <andi@etezian.org>");
|
[media] rc: add support for IR LEDs driven through SPI
The ir-spi is a simple device driver which supports the
connection between an IR LED and the MOSI line of an SPI device.
The driver, indeed, uses the SPI framework to stream the raw data
provided by userspace through an rc character device. The chardev
is handled by the LIRC framework and its functionality basically
provides:
- write: the driver gets a pulse/space signal and translates it
to a binary signal that will be streamed to the IR led through
the SPI framework.
- set frequency: sets the frequency whith which the data should
be sent. This is handle with ioctl with the
LIRC_SET_SEND_CARRIER flag (as per lirc documentation)
- set duty cycle: this is also handled with ioctl with the
LIRC_SET_SEND_DUTY_CYCLE flag. The driver handles duty cycles
of 50%, 60%, 70%, 75%, 80% and 90%, calculated on 16bit data.
The character device is created under /dev/lircX name, where X is
and ID assigned by the LIRC framework.
Example of usage:
fd = open("/dev/lirc0", O_RDWR);
if (fd < 0)
return -1;
val = 608000;
ret = ioctl(fd, LIRC_SET_SEND_CARRIER, &val);
if (ret < 0)
return -1;
val = 60;
ret = ioctl(fd, LIRC_SET_SEND_DUTY_CYCLE, &val);
if (ret < 0)
return -1;
n = write(fd, buffer, BUF_LEN);
if (n < 0 || n != BUF_LEN)
ret = -1;
close(fd);
Signed-off-by: Andi Shyti <andi.shyti@samsung.com>
Signed-off-by: Sean Young <sean@mess.org>
Signed-off-by: Mauro Carvalho Chehab <mchehab@s-opensource.com>
2016-12-16 09:12:18 +03:00
|
|
|
MODULE_DESCRIPTION("SPI IR LED");
|
|
|
|
MODULE_LICENSE("GPL v2");
|