[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160701140042.GB1257@jack.zhora.eu>
Date: Fri, 1 Jul 2016 23:00:42 +0900
From: Andi Shyti <andi@...zian.org>
To: Sean Young <sean@...s.org>
Cc: Andi Shyti <andi.shyti@...sung.com>,
Mauro Carvalho Chehab <mchehab@....samsung.com>,
Rob Herring <robh+dt@...nel.org>,
Mark Rutland <mark.rutland@....com>,
devicetree@...r.kernel.org, linux-media@...r.kernel.org,
linux-kernel@...r.kernel.org, Andi Shyti <andi@...zian.org>
Subject: Re: [PATCH] [media] rc: ir-spi: add support for IR LEDs connected
with SPI
Hi Sean,
> > > 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.
> >
> > Also here I'm getting a bit confused. When I started writing
> > this, I didn't even know of the existence of a remote controlling
> > framework, but then I run across this:
> >
> > "LIRC is a package that allows you to decode and send infra-red
> > signals of many (but not all) commonly used remote controls. "
> >
> > taken from lirc.org: my case is exactly falling into this
> > description.
> >
> > Am I missing anything?
>
> See drivers/staging/media/lirc/TODO: "All drivers should either be
> ported to ir-core, or dropped entirely". ir-core has since been renamed
> to rc-core; it is uses for non-IR purposes like cec.
>
> lirc exists as the user-space ABI but not it is not the preferred
> framework for kernel space.
I missed this part and now what you say makes sense.
> I'm happy to help.
I will do as you recommend and thanks a lot, appreciated :)
Andi
Powered by blists - more mailing lists