linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jarod Wilson <jarod@redhat.com>
To: "David Härdeman" <david@hardeman.nu>
Cc: mchehab@infradead.org, linux-media@vger.kernel.org
Subject: Re: [PATCH 0/3] Proposed ir-core (rc-core) changes
Date: Thu, 26 Aug 2010 15:14:50 -0400	[thread overview]
Message-ID: <20100826191450.GA11951@redhat.com> (raw)
In-Reply-To: <20100824225427.13006.57226.stgit@localhost.localdomain>

On Wed, Aug 25, 2010 at 01:01:57AM +0200, David Härdeman wrote:
> The following series merges the different files that currently make up
> the ir-core module into a single-file rc-core module.
> 
> In addition, the ir_input_dev and ir_dev_props structs are replaced
> by a single rc_dev struct with an API similar to that of the input
> subsystem.
> 
> This allows the removal of all knowledge of any input devices from the
> rc drivers and paves the way for allowing multiple input devices per
> rc device in the future. The namespace conversion from ir_* to rc_*
> should mostly be done for the drivers with this patchset.
> 
> I have intentionally not signed off on the patches yet since they haven't
> been tested. I'd like your feedback on the general approach before I spend
> the time to properly test the result.
> 
> Also, the imon driver is not converted (and will thus break with this
> patchset). The reason is that the imon driver wants to generate mouse
> events on the input dev under the control of rc-core. I was hoping that
> Jarod would be willing to convert the imon driver to create a separate
> input device for sending mouse events to userspace :)

Yeah, I could be persuaded to do that. Means that the imon driver, when
driving one of the touchscreen devices, will bring up 3 separate input
devices, but oh well. (I'd actually considered doing that when porting to
ir-core in the first place, but went the lazy route. ;)

> Comments please...

Haven't tried it out at all yet or done more than a quick skim through the
patches, but at first glance, I do like the idea of further abstracting
away the input layer. I know I tanked a few things the first go 'round,
thinking I needed to do both some rc-layer and input-layer setup and/or
teardown. It becomes more cut and dry if you don't see anything
input-related anywhere at all.

One thing I did note with the patches is that a lot of bits were altered
from ir-foo to rc-foo, but not all of them... If we're going to make the
change, why no go whole hog? (Or was it only things relevant to ir
specifically right now that didn't get renamed?)

-- 
Jarod Wilson
jarod@redhat.com


  parent reply	other threads:[~2010-08-26 19:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-24 23:01 [PATCH 0/3] Proposed ir-core (rc-core) changes David Härdeman
2010-08-24 23:02 ` [PATCH 1/3] merge rc-core David Härdeman
2010-08-24 23:02 ` [PATCH 2/3] remove remaining users of the ir-functions keyhandlers David Härdeman
2010-08-24 23:02 ` [PATCH 3/3] make rc_dev the primary interface for remote control drivers David Härdeman
2010-08-26 19:14 ` Jarod Wilson [this message]
2010-08-27 10:50   ` [PATCH 0/3] Proposed ir-core (rc-core) changes David Härdeman
  -- strict thread matches above, loose matches on Subject: below --
2010-08-27 15:44 Andy Walls
2010-08-27 15:55 Andy Walls
2010-08-27 17:58 ` Jarod Wilson

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=20100826191450.GA11951@redhat.com \
    --to=jarod@redhat.com \
    --cc=david@hardeman.nu \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@infradead.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).