From: Sean Young <sean@mess.org>
To: Andi Shyti <andi.shyti@samsung.com>
Cc: Mauro Carvalho Chehab <mchehab@osg.samsung.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org, linux-media@vger.kernel.org,
linux-kernel@vger.kernel.org, Andi Shyti <andi@etezian.org>
Subject: Re: [PATCH] [media] rc: ir-spi: add support for IR LEDs connected with SPI
Date: Fri, 1 Jul 2016 10:44:58 +0100 [thread overview]
Message-ID: <20160701094458.GA8933@gofer.mess.org> (raw)
In-Reply-To: <1467362022-12704-1-git-send-email-andi.shyti@samsung.com>
On Fri, Jul 01, 2016 at 05:33:42PM +0900, Andi Shyti wrote:
> 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 a character device. The chardev is
> handled by the LIRC framework and its functionality basically
> provides:
>
> - raw write: data to be sent to the SPI and then streamed to the
> MOSI line;
> - set frequency: sets the frequency whith which the data should
> be sent;
> - set length: sets the data length. This information is
> optional, if the length is set, then userspace should send raw
> data only with that length; while if the length is set to '0',
> then the driver will figure out himself the length of the data
> based on the length of the data written on the character
> device.
> The latter is not recommended, though, as the driver, at
> any write, allocates and deallocates a buffer where the data
> from userspace are stored.
>
> The driver provides three feedback commands:
>
> - get length: reads the length set and (as mentioned), if the
> length is '0' it will be calculated at any write
> - get frequency: the driver reports the frequency. If userpace
> doesn't set the frequency, the driver will use a default value
> of 38000Hz.
This interface is not compatible with other lirc devices; there is no
way of determining whether this is a regular lirc device or this new
flavour you've invented.
Also I don't see what justifies this new interface. This can be
implemented in rc-core in less lines of code and it will be entirely
compatible with existing user-space.
Sean
next prev parent reply other threads:[~2016-07-01 9:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-01 8:33 [PATCH] [media] rc: ir-spi: add support for IR LEDs connected with SPI Andi Shyti
2016-07-01 9:44 ` Sean Young [this message]
2016-07-01 12:30 ` Andi Shyti
2016-07-01 13:22 ` Sean Young
2016-07-01 14:00 ` Andi Shyti
2016-07-02 4:03 ` kbuild test robot
[not found] ` <1467362022-12704-1-git-send-email-andi.shyti-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2016-07-02 4:50 ` kbuild test robot
2016-07-05 14:22 ` Rob Herring
2016-07-05 15:08 ` 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=20160701094458.GA8933@gofer.mess.org \
--to=sean@mess.org \
--cc=andi.shyti@samsung.com \
--cc=andi@etezian.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mchehab@osg.samsung.com \
--cc=robh+dt@kernel.org \
/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).