From: "Pali Rohár" <pali.rohar@gmail.com>
To: Tony Lindgren <tony@atomide.com>
Cc: Aaro Koskinen <aaro.koskinen@iki.fi>,
Ivaylo Dimitrov <ivo.g.dimitrov.75@gmail.com>,
Sebastian Reichel <sre@kernel.org>, Pavel Machel <pavel@ucw.cz>,
Nishanth Menon <nm@ti.com>,
Timo Kokkonen <timo.t.kokkonen@iki.fi>,
linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Nokia N900: Broken lirc ir-rx51 driver
Date: Fri, 22 Apr 2016 15:49:29 +0200 [thread overview]
Message-ID: <20160422134929.GG29406@pali> (raw)
In-Reply-To: <20160106011249.GH12777@atomide.com>
On Tuesday 05 January 2016 17:12:50 Tony Lindgren wrote:
> * Pali Rohár <pali.rohar@gmail.com> [160105 02:19]:
> > On Saturday 02 January 2016 09:06:57 Tony Lindgren wrote:
> > >
> > > Yup please take a look at thread "[PATCH 0/3] pwm: omap: Add PWM support
> > > using dual-mode timers". Chances are we still need to set up the dmtimer
> > > code to provide also irqchip functions. That way ir-rx51.c can just do
> > > request_irq on the selected dmtimer for interrupts.
> >
> > No I see that patch from that thread uses dmtimer.h from plat-omap. So
> > it is really OK?
>
> It's using the header to populate the platform data in mach-omap2 so
> that's fine. But we do not want to directly expose the dmtimer functions
> to device drivers as they are not Linux generic at this point.
>
> Regards,
>
> Tony
Hi Tony! Is there any progress for ir-rx51 driver? Months ago we were
waiting for some omap pwm patches... What is current state?
--
Pali Rohár
pali.rohar@gmail.com
next prev parent reply other threads:[~2016-04-22 13:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-02 14:45 Nokia N900: Broken lirc ir-rx51 driver Pali Rohár
2016-01-02 17:06 ` Tony Lindgren
2016-01-05 10:18 ` Pali Rohár
2016-01-06 1:12 ` Tony Lindgren
2016-04-22 13:49 ` Pali Rohár [this message]
2016-04-22 22:21 ` Tony Lindgren
2016-05-02 7:06 ` Pavel Machek
2016-05-02 8:39 ` Ivaylo Dimitrov
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=20160422134929.GG29406@pali \
--to=pali.rohar@gmail.com \
--cc=aaro.koskinen@iki.fi \
--cc=ivo.g.dimitrov.75@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
--cc=pavel@ucw.cz \
--cc=sre@kernel.org \
--cc=timo.t.kokkonen@iki.fi \
--cc=tony@atomide.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.