From: Sean Young <sean@mess.org>
To: Andi Shyti <andi.shyti@samsung.com>
Cc: Mauro Carvalho Chehab <mchehab@osg.samsung.com>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
Andi Shyti <andi@etezian.org>
Subject: Re: [RFC 5/7] [media] ir-lirc-codec: do not handle any buffer for raw transmitters
Date: Tue, 19 Jul 2016 23:16:10 +0100 [thread overview]
Message-ID: <20160719221610.GC24697@gofer.mess.org> (raw)
In-Reply-To: <1468943818-26025-6-git-send-email-andi.shyti@samsung.com>
On Wed, Jul 20, 2016 at 12:56:56AM +0900, Andi Shyti wrote:
> Raw transmitters receive the data which need to be sent to
> receivers from userspace as stream of bits, they don't require
> any handling from the lirc framework.
No drivers of type RC_DRIVER_IR_RAW_TX should handle tx just like any
other device, so data should be provided as an array of u32 alternating
pulse-space. If your device does not handle input like that then convert
it into that format in the driver. Every other driver has to do some
sort of conversion of that kind.
Thanks
Sean
>
> Signed-off-by: Andi Shyti <andi.shyti@samsung.com>
> ---
> drivers/media/rc/ir-lirc-codec.c | 30 +++++++++++++++++++-----------
> 1 file changed, 19 insertions(+), 11 deletions(-)
>
> diff --git a/drivers/media/rc/ir-lirc-codec.c b/drivers/media/rc/ir-lirc-codec.c
> index 5effc65..80e94b6 100644
> --- a/drivers/media/rc/ir-lirc-codec.c
> +++ b/drivers/media/rc/ir-lirc-codec.c
> @@ -121,17 +121,6 @@ static ssize_t ir_lirc_transmit_ir(struct file *file, const char __user *buf,
> if (!lirc)
> return -EFAULT;
>
> - if (n < sizeof(unsigned) || n % sizeof(unsigned))
> - return -EINVAL;
> -
> - count = n / sizeof(unsigned);
> - if (count > LIRCBUF_SIZE || count % 2 == 0)
> - return -EINVAL;
> -
> - txbuf = memdup_user(buf, n);
> - if (IS_ERR(txbuf))
> - return PTR_ERR(txbuf);
> -
> dev = lirc->dev;
> if (!dev) {
> ret = -EFAULT;
> @@ -143,6 +132,25 @@ static ssize_t ir_lirc_transmit_ir(struct file *file, const char __user *buf,
> goto out;
> }
>
> + if (dev->driver_type == RC_DRIVER_IR_RAW_TX) {
> + txbuf = memdup_user(buf, n);
> + if (IS_ERR(txbuf))
> + return PTR_ERR(txbuf);
> +
> + return dev->tx_ir(dev, txbuf, n);
> + }
> +
> + if (n < sizeof(unsigned) || n % sizeof(unsigned))
> + return -EINVAL;
> +
> + count = n / sizeof(unsigned);
> + if (count > LIRCBUF_SIZE || count % 2 == 0)
> + return -EINVAL;
> +
> + txbuf = memdup_user(buf, n);
> + if (IS_ERR(txbuf))
> + return PTR_ERR(txbuf);
> +
> for (i = 0; i < count; i++) {
> if (txbuf[i] > IR_MAX_DURATION / 1000 - duration || !txbuf[i]) {
> ret = -EINVAL;
> --
> 2.8.1
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-media" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2016-07-19 22:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-19 15:56 [RFC 0/7] Add support for IR transmitters Andi Shyti
2016-07-19 15:56 ` [RFC 1/7] [media] rc-main: assign driver type during allocation Andi Shyti
2016-07-19 22:04 ` Sean Young
2016-07-21 0:19 ` Andi Shyti
2016-07-19 15:56 ` [RFC 2/7] [media] rc-main: split setup and unregister functions Andi Shyti
2016-07-19 15:56 ` [RFC 3/7] [media] rc-core: add support for IR raw transmitters Andi Shyti
2016-07-19 22:10 ` Sean Young
2016-07-21 0:44 ` Andi Shyti
2016-07-19 15:56 ` [RFC 4/7] [media] rc-ir-raw: do not generate any receiving thread for " Andi Shyti
2016-07-19 15:56 ` [RFC 5/7] [media] ir-lirc-codec: do not handle any buffer " Andi Shyti
2016-07-19 22:16 ` Sean Young [this message]
2016-07-21 0:48 ` Andi Shyti
2016-07-21 14:43 ` Sean Young
2016-07-19 15:56 ` [RFC 6/7] Documentation: bindings: add documentation for ir-spi device driver Andi Shyti
2016-07-19 15:56 ` [RFC 7/7] [media] rc: add support for IR LEDs driven through SPI Andi Shyti
2016-07-19 23:11 ` Sean Young
2016-07-21 1:09 ` Andi Shyti
2016-07-21 10:22 ` Sean Young
2016-07-21 14:57 ` Andi Shyti
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=20160719221610.GC24697@gofer.mess.org \
--to=sean@mess.org \
--cc=andi.shyti@samsung.com \
--cc=andi@etezian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@osg.samsung.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).