linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Timo Kokkonen <timo.t.kokkonen@iki.fi>
To: Sakari Ailus <sakari.ailus@iki.fi>
Cc: Sebastian Reichel <sre@ring0.de>,
	linux-media@vger.kernel.org, linux-omap@vger.kernel.org
Subject: Re: [git:v4l-dvb/for_v3.7] [media] media: rc: Introduce RX51 IR transmitter driver
Date: Thu, 16 Aug 2012 21:18:04 +0300	[thread overview]
Message-ID: <502D395C.8020003@iki.fi> (raw)
In-Reply-To: <20120816163458.GA29636@valkosipuli.retiisi.org.uk>

On 08/16/12 19:34, Sakari Ailus wrote:
> Hi Sebastian,
> 
> On Thu, Aug 16, 2012 at 01:21:04PM +0200, Sebastian Reichel wrote:
>> Hi,
>>
>>>> It was an requirement back then that this driver needs to be a module as
>>>> 99% of the N900 owners still don't even know they have this kind of
>>>> capability on their devices, so it doesn't make sense to keep the module
>>>> loaded unless the user actually needs it.
>>>
>>> I don't think that's so important --- currently the vast majority of the
>>> N900 users using the mainline kernel compile it themselves. It's more
>>> important to have a clean implementation at this point.
>>
>> I would like to enable this feature for the Debian OMAP kernel,
>> which is not only used for N900, but also for Pandaboard, etc.
> 
> Fair enough. Thanks for the info!
> 
> Timo: thinking this a little more, do you think the call is really needed?
> AFAIU it doesn't really achieve what it's supposed to, keeping the CPU from
> going to sleep. I noticed exactly the same problem you did, it was bad to
> the extent irsend failed due to a timeout unless I kept the CPU busy.

Yes, that's right. It's not really useful as is.

> So I think we can remove the call, which results in two things: the driver
> can be built as a module and the platform data does not contain a function
> pointer any longer.

Yeah, I agree. Although with the original N900 kernel the call did make
it work. But the power management implementation was different there
too. Maybe the proper fix for the problem is today something different
it was back then.

If I have time I'll see if I can figure out something..

-Timo


      reply	other threads:[~2012-08-16 18:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-13 19:53 [git:v4l-dvb/for_v3.7] [media] media: rc: Introduce RX51 IR transmitter driver Mauro Carvalho Chehab
2012-08-15 16:06 ` Sakari Ailus
2012-08-15 19:46   ` Timo Kokkonen
2012-08-16 10:23     ` Sakari Ailus
2012-08-16 11:21       ` Sebastian Reichel
2012-08-16 16:34         ` Sakari Ailus
2012-08-16 18:18           ` Timo Kokkonen [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=502D395C.8020003@iki.fi \
    --to=timo.t.kokkonen@iki.fi \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=sakari.ailus@iki.fi \
    --cc=sre@ring0.de \
    /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).