From: Sean Young <sean@mess.org>
To: "David Härdeman" <david@hardeman.nu>
Cc: linux-media@vger.kernel.org, mchehab@s-opensource.com
Subject: Re: [PATCH] rc-core: cleanup rc_register_device (v2)
Date: Sun, 21 May 2017 09:34:48 +0100 [thread overview]
Message-ID: <20170521083448.GA29040@gofer.mess.org> (raw)
In-Reply-To: <20170521064509.iuou3gzqdv37znan@hardeman.nu>
On Sun, May 21, 2017 at 08:45:09AM +0200, David Härdeman wrote:
> On Sat, May 20, 2017 at 12:10:40PM +0100, Sean Young wrote:
> >On Wed, May 03, 2017 at 12:04:00PM +0200, David Härdeman wrote:
> >> The device core infrastructure is based on the presumption that
> >> once a driver calls device_add(), it must be ready to accept
> >> userspace interaction.
> >>
> >> This requires splitting rc_setup_rx_device() into two functions
> >> and reorganizing rc_register_device() so that as much work
> >> as possible is performed before calling device_add().
> >>
> >> Version 2: switch the order in which rc_prepare_rx_device() and
> >> ir_raw_event_prepare() gets called so that dev->change_protocol()
> >> gets called before device_add().
> >
> >With this patch applied, when I plug in an iguanair usb device, I get.
>
> I'm not surprised that changes to rc_register_device() might require
> some driver-specific fixes as well.
No, it means that if any driver generates IR early enough after
rc_register_device(), you will get this.
> I haven't looked at this yet, and I'm going on vacation in a few hours,
> so I'll probably take a look in a week...
I'm currently testing and reviewing all the pending rc patches for v4.13,
if I have time left I might fix it up.
Thanks
Sean
prev parent reply other threads:[~2017-05-21 8:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-03 10:04 [PATCH] rc-core: cleanup rc_register_device (v2) David Härdeman
2017-05-17 20:09 ` Sean Young
2017-05-18 7:55 ` David Härdeman
2017-05-18 9:42 ` Sean Young
2017-05-20 11:10 ` Sean Young
2017-05-21 6:45 ` David Härdeman
2017-05-21 8:34 ` Sean Young [this message]
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=20170521083448.GA29040@gofer.mess.org \
--to=sean@mess.org \
--cc=david@hardeman.nu \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@s-opensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.