From: Greg KH <gregkh@linuxfoundation.org>
To: Sean Young <sean@mess.org>
Cc: anton@samba.org, mchehab@s-opensource.com, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] [media] ir-spi: Fix issues with lirc API" failed to apply to 4.12-stable tree
Date: Mon, 7 Aug 2017 15:16:05 -0700 [thread overview]
Message-ID: <20170807221605.GA8002@kroah.com> (raw)
In-Reply-To: <20170729112444.h4mfbyxusufahqdb@gofer.mess.org>
On Sat, Jul 29, 2017 at 12:24:45PM +0100, Sean Young wrote:
>
> From: Anton Blanchard <anton@samba.org>
> Subject: [PATCH] [media] ir-spi: Fix issues with lirc API
>
> The ir-spi driver has 2 issues which prevents it from working with
> lirc:
>
> 1. The ir-spi driver uses 16 bits of SPI data to create one cycle of
> the waveform. As such our SPI clock needs to be 16x faster than the
> carrier frequency.
>
> The driver is inconsistent in how it currently handles this. It
> initializes it to the carrier frequency:
>
> But the commit message has some example code which initialises it
> to 16x the carrier frequency:
>
> val = 608000;
> ret = ioctl(fd, LIRC_SET_SEND_CARRIER, &val);
>
> To maintain compatibility with lirc, always do the frequency adjustment
> in the driver.
>
> 2. lirc presents pulses in microseconds, but the ir-spi driver treats
> them as cycles of the carrier. Similar to other lirc drivers, do the
> conversion with DIV_ROUND_CLOSEST().
>
> Fixes: fe052da49201 ("[media] rc: add support for IR LEDs driven through SPI")
>
> Cc: stable@vger.kernel.org
> Signed-off-by: Anton Blanchard <anton@samba.org>
> Signed-off-by: Sean Young <sean@mess.org>
> Signed-off-by: Mauro Carvalho Chehab <mchehab@s-opensource.com>
> ---
> drivers/media/rc/ir-spi.c | 9 ++++++---
> 1 file changed, 6 insertions(+), 3 deletions(-)
Thanks for the backport.
greg k-h
prev parent reply other threads:[~2017-08-07 22:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-22 13:22 FAILED: patch "[PATCH] [media] ir-spi: Fix issues with lirc API" failed to apply to 4.12-stable tree gregkh
2017-07-29 11:24 ` Sean Young
2017-08-07 22:16 ` Greg KH [this message]
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=20170807221605.GA8002@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=anton@samba.org \
--cc=mchehab@s-opensource.com \
--cc=sean@mess.org \
--cc=stable@vger.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).