From: James Hogan <james.hogan@imgtec.com>
To: <mchehab@osg.samsung.com>
Cc: Sifan Naeem <sifan.naeem@imgtec.com>,
<linux-kernel@vger.kernel.org>, <linux-media@vger.kernel.org>,
<james.hartley@imgtec.com>, <ezequiel.garcia@imgtec.com>
Subject: Re: [PATCH v2 3/5] rc: img-ir: biphase enabled with workaround
Date: Fri, 12 Dec 2014 13:55:33 +0000 [thread overview]
Message-ID: <548AF3D5.8000109@imgtec.com> (raw)
In-Reply-To: <548ADA82.80603@imgtec.com>
[-- Attachment #1: Type: text/plain, Size: 1600 bytes --]
On 12/12/14 12:07, James Hogan wrote:
> Hi Sifan,
>
> On 11/12/14 20:06, Sifan Naeem wrote:
>> Biphase decoding in the current img-ir has got a quirk, where multiple
>> Interrupts are generated when an incomplete IR code is received by the
>> decoder.
>>
>> Patch adds a work around for the quirk and enables biphase decoding.
>>
>> Changes from v1:
>> * rebased due to conflict with "img-ir/hw: Fix potential deadlock stopping timer"
>> * spinlock taken in img_ir_suspend_timer
>> * check for hw->stopping before handling quirks in img_ir_isr_hw
>> * new memeber added to img_ir_priv_hw to save irq status over suspend
>
> For future reference, the list of changes between patchset versions is
> usually put after a "---" so that it doesn't get included in the final
> git commit message. You can also add any Acked-by/Reviewed-by tags
> you've been given to new versions of patchset, assuming nothing
> significant has changed in that patch (maintainers generally add
> relevant tags for you, that are sent in response to the patches being
> applied).
>
> Anyway, the whole patchset looks okay to me, aside from the one question
> I just asked on patch 3 of v1, which I'm not so sure about. I'll let you
> decide whether that needs changing since you have the hardware to verify it.
>
> So for the whole patchset feel free to add my:
> Acked-by: James Hogan <james.hogan@imgtec.com>
Mauro: Assuming no other changes are requested in this patchset, do you
want these resent with the moving of changelogs out of the main commit
messages?
Cheers
James
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-12-12 13:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-11 20:06 [PATCH v2 0/5] rc: img-ir: rc5 and rc6 support added Sifan Naeem
2014-12-11 20:06 ` [PATCH v2 1/5] rc: img-ir: add scancode requests to a struct Sifan Naeem
2014-12-11 20:06 ` [PATCH v2 2/5] rc: img-ir: pass toggle bit to the rc driver Sifan Naeem
2014-12-11 20:06 ` [PATCH v2 3/5] rc: img-ir: biphase enabled with workaround Sifan Naeem
2014-12-12 12:07 ` James Hogan
2014-12-12 13:55 ` James Hogan [this message]
2014-12-11 20:06 ` [PATCH v2 4/5] rc: img-ir: add philips rc5 decoder module Sifan Naeem
2014-12-11 20:06 ` [PATCH v2 5/5] rc: img-ir: add philips rc6 " Sifan Naeem
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=548AF3D5.8000109@imgtec.com \
--to=james.hogan@imgtec.com \
--cc=ezequiel.garcia@imgtec.com \
--cc=james.hartley@imgtec.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@osg.samsung.com \
--cc=sifan.naeem@imgtec.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