From: "David Härdeman" <david@hardeman.nu>
To: Tom Gundersen <teg@jklm.no>
Cc: "Juan J. Garcia de Soria" <skandalfo@gmail.com>,
Sean Young <sean@mess.org>,
"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
linux-media@vger.kernel.org
Subject: Re: WPC8769L (WEC1020) support in winbond-cir?
Date: Tue, 15 Oct 2013 23:59:43 +0200 [thread overview]
Message-ID: <20131015215943.GC26542@hardeman.nu> (raw)
In-Reply-To: <CAG-2HqX-TO7h8zJ6F01r2LfRVjQtb0pK_1wKGsYVKzB0zC7TQA@mail.gmail.com>
On Mon, Oct 14, 2013 at 03:16:20PM +0200, Tom Gundersen wrote:
>Hi David and Juan,
>
>I'm going through the various out-of-tree LIRC drivers to see if we
>can stop shipping them in Arch Linux [0]. So far it appears we can
>drop all except for lirc_wpc8769l [1] (PnP id WEC1020).
>
>I noticed the comment in windownd-cir [2]:
>
> * Currently supports the Winbond WPCD376i chip (PNP id WEC1022), but
> * could probably support others (Winbond WEC102X, NatSemi, etc)
> * with minor modifications.
>
>What are your thoughts on adding support for WEC1020 upstream? Is
>anyone interested in doing this work (I sadly don't have the correct
>device, so can't really do it myself)?
IIRC, Juan had a hacked-up version of the winbond-cir driver working on
his hardware back in March (the hardware seems similar enough, basically
the WEC1022 adds some additional Wake-On-IR functionality...I seem to
recall).
But I think Juan is the one to talk to. I don't have the WEC1020
hardware and I don't have his experience of adding support for it...
--
David Härdeman
next prev parent reply other threads:[~2013-10-15 21:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-14 13:16 WPC8769L (WEC1020) support in winbond-cir? Tom Gundersen
2013-10-14 14:07 ` Mauro Carvalho Chehab
2013-10-14 14:42 ` Tom Gundersen
2013-10-15 21:59 ` David Härdeman [this message]
[not found] ` <CAB+yVgCtvRHRLxP2SRgCAqkCKdyThgr48fOvBFe9YHfz3xArmQ@mail.gmail.com>
2013-10-16 14:47 ` Juan Jesús García de Soria Lucena
[not found] ` <CAG-2HqVh1hzC0rzft9gD+4zmJpnpH9OKj64vyO4teCrX5wuT+g@mail.gmail.com>
2013-10-22 10:57 ` Juan Jesús García de Soria Lucena
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=20131015215943.GC26542@hardeman.nu \
--to=david@hardeman.nu \
--cc=linux-input@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=sean@mess.org \
--cc=skandalfo@gmail.com \
--cc=teg@jklm.no \
/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).