From: Maxim Levitsky <maximlevitsky@gmail.com>
To: Christoph Bartelmus <lirc@bartelmus.de>
Cc: linux-input@vger.kernel.org, linux-media@vger.kernel.org,
lirc-list@lists.sourceforge.net, mchehab@redhat.com
Subject: Re: [PATCH 10/13] IR: extend interfaces to support more device settings LIRC: add new IOCTL that enables learning mode (wide band receiver)
Date: Sat, 31 Jul 2010 01:01:04 +0300 [thread overview]
Message-ID: <1280527264.3159.10.camel@maxim-laptop> (raw)
In-Reply-To: <BTpNtKTJjFB@christoph>
On Fri, 2010-07-30 at 23:22 +0200, Christoph Bartelmus wrote:
> Hi!
>
> Maxim Levitsky "maximlevitsky@gmail.com" wrote:
>
> > Still missing features: carrier report & timeout reports.
> > Will need to pack these into ir_raw_event
>
>
> Hm, this patch changes the LIRC interface but I can't see the according
> patch to the documentation.
>
> [...]
> > * @tx_ir: transmit IR
> > * @s_idle: optional: enable/disable hardware idle mode, upon which,
> > +<<<<<<< current
> > * device doesn't interrupt host untill it sees IR data
> > +=======
>
> Huh?
:-)
>
> > + device doesn't interrupt host untill it sees IR data
> > + * @s_learning_mode: enable wide band receiver used for learning
> +>>>>>>>> patched
>
> s/untill/until/
>
> [...]
> > #define LIRC_CAN_MEASURE_CARRIER 0x02000000
> > +#define LIRC_CAN_HAVE_WIDEBAND_RECEIVER 0x04000000
>
> LIRC_CAN_USE_WIDEBAND_RECEIVER
OK.
>
> [...]
> > @@ -145,7 +146,7 @@
> > * if enabled from the next key press on the driver will send
> > * LIRC_MODE2_FREQUENCY packets
> > */
> > -#define LIRC_SET_MEASURE_CARRIER_MODE _IOW('i', 0x0000001d, __u32)
> > +#define LIRC_SET_MEASURE_CARRIER_MODE _IOW('i', 0x0000001d, __u32)
> >
> > /*
> > * to set a range use
> > @@ -162,4 +163,6 @@
> > #define LIRC_SETUP_START _IO('i', 0x00000021)
> > #define LIRC_SETUP_END _IO('i', 0x00000022)
> >
> > +#define LIRC_SET_WIDEBAND_RECEIVER _IOW('i', 0x00000023, __u32)
>
> If you really want this new ioctl, then it should be clarified how it
> behaves in relation to LIRC_SET_MEASURE_CARRIER_MODE.
In my opinion, I won't need the LIRC_SET_MEASURE_CARRIER_MODE,
I would just optionally turn that on in learning mode.
You disagree, and since that is not important (besides TX and learning
features are present only at fraction of ENE devices. The only user I
did the debugging with, doesn't seem to want to help debug that code
anymore...)
But anyway, in current state I want these features to be independent.
Driver will enable learning mode if it have to.
I'll add the documentation.
>
> Do you have to enable the wide-band receiver explicitly before you can
> enable carrier reports or does enabling carrier reports implicitly switch
> to the wide-band receiver?
I would implicitly switch the learning mode on, untill user turns off
the carrier reports.
>
> What happens if carrier mode is enabled and you explicitly turn off the
> wide-band receiver?
Wouldn't it be better to have one ioctl for both after all?
>
> And while we're at interface stuff:
> Do we really need LIRC_SETUP_START and LIRC_SETUP_END? It is only used
> once in lircd during startup.
I don't think so.
Best regards,
Maxim Levitsky
next prev parent reply other threads:[~2010-07-30 22:01 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-30 11:38 [PATCH 0/9 v3] IR: few fixes, additions and ENE driver Maxim Levitsky
2010-07-30 11:38 ` [PATCH 01/13] IR: Kconfig fixes Maxim Levitsky
2010-07-30 11:38 ` [PATCH 02/13] IR: minor fixes: Maxim Levitsky
2010-07-30 11:38 ` [PATCH 03/13] IR: replace spinlock with mutex Maxim Levitsky
2010-07-30 11:38 ` [PATCH 04/13] IR: fix locking in ir_raw_event_work Maxim Levitsky
2010-07-30 11:38 ` [PATCH 05/13] IR: JVC: make repeat work Maxim Levitsky
2010-07-30 11:38 ` [PATCH 06/13] IR: nec decoder: fix repeat Maxim Levitsky
2010-07-30 19:36 ` Mauro Carvalho Chehab
2010-07-30 19:54 ` Maxim Levitsky
2010-07-30 11:38 ` [PATCH 07/13] IR: NECX: support repeat Maxim Levitsky
2010-07-30 11:38 ` [PATCH 08/13] IR: Allow not to compile keymaps in Maxim Levitsky
2010-07-30 11:38 ` [PATCH 09/13] IR: add helper function for hardware with small o/b buffer Maxim Levitsky
2010-07-30 11:38 ` [PATCH 10/13] IR: extend interfaces to support more device settings LIRC: add new IOCTL that enables learning mode (wide band receiver) Maxim Levitsky
2010-07-30 21:22 ` Christoph Bartelmus
2010-07-30 22:01 ` Maxim Levitsky [this message]
2010-07-31 8:10 ` Christoph Bartelmus
2010-07-31 9:35 ` Maxim Levitsky
2010-07-30 11:38 ` [PATCH 11/13] IR: report unknown scancodes the in-kernel decoders found Maxim Levitsky
2010-07-30 11:38 ` [PATCH 12/13] STAGING: remove lirc_ene0100 driver Maxim Levitsky
2010-07-30 11:38 ` [PATCH 13/13] IR: Port ene driver to new IR subsystem and enable it Maxim Levitsky
2010-07-30 19:33 ` [PATCH 0/9 v3] IR: few fixes, additions and ENE driver Mauro Carvalho Chehab
2010-07-30 19:52 ` Maxim Levitsky
-- strict thread matches above, loose matches on Subject: below --
2010-07-30 2:17 [PATCH 0/9 v2] " Maxim Levitsky
2010-07-30 2:17 ` [PATCH 10/13] IR: extend interfaces to support more device settings LIRC: add new IOCTL that enables learning mode (wide band receiver) Maxim Levitsky
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=1280527264.3159.10.camel@maxim-laptop \
--to=maximlevitsky@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=lirc-list@lists.sourceforge.net \
--cc=lirc@bartelmus.de \
--cc=mchehab@redhat.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;
as well as URLs for NNTP newsgroup(s).