From: Felipe Balbi <balbi@ti.com>
To: Tony Lindgren <tony@atomide.com>
Cc: Felipe Balbi <balbi@ti.com>,
Linux OMAP Mailing List <linux-omap@vger.kernel.org>
Subject: Re: [RFT/RFC/PATCH 00/13] CBUS meets GENIRQ
Date: Thu, 10 Feb 2011 11:14:47 +0200 [thread overview]
Message-ID: <20110210091447.GA3580@legolas.emea.dhcp.ti.com> (raw)
In-Reply-To: <20110210024349.GI20795@atomide.com>
Hi,
On Wed, Feb 09, 2011 at 06:43:49PM -0800, Tony Lindgren wrote:
> * Felipe Balbi <balbi@ti.com> [110203 02:20]:
> > Hi Tony,
> >
> > When you have some extra time, could you run these on N810
> > to check whether I'm on the right path ? After these patches
> > all CBUS drivers are using standard request_threaded_irq()
> > calls. It's one step closer into getting those in mainline.
>
> Cool sorry it took a while, this is starting to look like
no problem ;-)
> it will be pretty close to be posted for merging :)
yeah, I guess so too.
> I guess we should move files around to have:
>
> drivers/mfd/cbus-retu.c
> drivers/mfd/cbus-tahvo.c
>
> drivers/rtc/rtc-cbus-retu.c
sure we gotta do that.
> Anything else remaining to do?
there are a few things remaining still. The drivers aren't as good as
I'd like them to be yet.
> Also the following patch was needed to get this to boot
> with interrupts working. Maybe you have a better plan
> for getting the retu irq_base?
That's on my TODO list, I need to pass IRQ number via pdata.
> Anyways, since n8x0 boots and stays up, we know it's
> working, so I've pushed them all to the cbus branch.
Cool thanks. I'll update my local cbus branch based on yours and try to
find some time to play with the last few stuff. Maybe I'll have some
small time during the weekend which I could use to play with it.
--
balbi
prev parent reply other threads:[~2011-02-10 9:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-03 10:20 [RFT/RFC/PATCH 00/13] CBUS meets GENIRQ Felipe Balbi
2011-02-03 10:20 ` [RFT/RFC/PATCH 01/13] cbus: retu: get rid of retu-user.c Felipe Balbi
2011-02-03 10:20 ` [RFT/RFC/PATCH 02/13] cbus: retu: give it a context structure Felipe Balbi
2011-02-03 10:20 ` [RFT/RFC/PATCH 03/13] cbus: retu: move module_* close to the matching symbol Felipe Balbi
2011-02-03 10:20 ` [RFT/RFC/PATCH 04/13] cbus: retu: cleanup error path Felipe Balbi
2011-02-03 10:20 ` [RFT/RFC/PATCH 05/13] arm: omap: irqs: add CBUS_RETU_IRQ_BASE and CBUS_RETU_IRQ_END Felipe Balbi
2011-02-03 10:20 ` [RFT/RFC/PATCH 06/13] arm: omap: cbus: pass irq_base and irq_end via platform_data Felipe Balbi
2011-02-03 10:20 ` [RFT/RFC/PATCH 07/13] cbus: retu: move to threaded IRQ and GENIRQ Felipe Balbi
2011-02-03 10:20 ` [RFT/RFC/PATCH 08/13] cbus: retu: headset: convert to threaded_irq Felipe Balbi
2011-02-03 10:20 ` [RFT/RFC/PATCH 09/13] cbus: retu-pwrbutton: convert to threaded irq Felipe Balbi
2011-02-03 10:20 ` [RFT/RFC/PATCH 10/13] cbus: retu-rtc: move " Felipe Balbi
2011-02-03 10:20 ` [RFT/RFC/PATCH 11/13] cbus: retu-rtc: drop the reset_occurred flag Felipe Balbi
2011-02-03 10:20 ` [RFT/RFC/PATCH 12/13] cbus: Makefile: re-enable retu-wdt Felipe Balbi
2011-02-03 10:20 ` [RFT/RFC/PATCH 13/13] cbus: tahvo: drop tahvo-user Felipe Balbi
2011-02-10 2:43 ` [RFT/RFC/PATCH 00/13] CBUS meets GENIRQ Tony Lindgren
2011-02-10 9:14 ` Felipe Balbi [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=20110210091447.GA3580@legolas.emea.dhcp.ti.com \
--to=balbi@ti.com \
--cc=linux-omap@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox