Hello Tero,
On Fri, 2 Sep 2011, Tero Kristo wrote:
On Fri, 2011-09-02 at 11:20 +0200, Paul Walmsley wrote:
If it would help, I'd be happy to do a first draft of the OMAP3430 PRM
hwmod data.
If you can do this it would help, as you have much better understanding
of the hwmod data than
On Wed, 2011-09-14 at 14:10 +0200, Paul Walmsley wrote:
Hello Tero,
On Fri, 2 Sep 2011, Tero Kristo wrote:
On Fri, 2011-09-02 at 11:20 +0200, Paul Walmsley wrote:
If it would help, I'd be happy to do a first draft of the OMAP3430 PRM
hwmod data.
If you can do this it would
Hi Tero,
On Thu, 1 Sep 2011, Tero Kristo wrote:
I've been looking at this now and got one question below. Otherwise your
comments look okay to me and I can work with those.
Great. As you work on it, please let me know if there's something that
doesn't make sense with this arrangement. I
Hi Paul,
On Fri, 2011-09-02 at 11:20 +0200, Paul Walmsley wrote:
Hi Tero,
On Thu, 1 Sep 2011, Tero Kristo wrote:
I've been looking at this now and got one question below. Otherwise your
comments look okay to me and I can work with those.
Great. As you work on it, please let me know
Hey Paul,
I've been looking at this now and got one question below. Otherwise your
comments look okay to me and I can work with those.
On Fri, 2011-08-26 at 11:12 +0200, Paul Walmsley wrote:
Hello Tero,
a few comments on this patch:
On Mon, 25 Jul 2011, Tero Kristo wrote:
Introduce a
Hello Tero,
a few comments on this patch:
On Mon, 25 Jul 2011, Tero Kristo wrote:
Introduce a chained interrupt handler mechanism for the PRCM
interrupt, so that individual PRCM event can cleanly be handled by
handlers in separate drivers. We do this by introducing PRCM event
names, which
On Mon, 2011-07-25 at 19:03 +0200, Balbi, Felipe wrote:
Hi,
On Mon, Jul 25, 2011 at 07:36:01PM +0300, Tero Kristo wrote:
Introduce a chained interrupt handler mechanism for the PRCM
interrupt, so that individual PRCM event can cleanly be handled by
handlers in separate drivers. We do
Hi,
On Tue, Jul 26, 2011 at 01:33:35PM +0300, Tero Kristo wrote:
+ while (1) {
+ unsigned int virtirq;
+
+ chip-irq_ack(desc-irq_data);
+
+ memset(pending, 0, sizeof(pending));
+ irq_setup-pending_events(pending);
+
+ /* No bit
Introduce a chained interrupt handler mechanism for the PRCM
interrupt, so that individual PRCM event can cleanly be handled by
handlers in separate drivers. We do this by introducing PRCM event
names, which are then matched to the particular PRCM interrupt bit
depending on the specific OMAP SoC
Hi,
On Mon, Jul 25, 2011 at 07:36:01PM +0300, Tero Kristo wrote:
Introduce a chained interrupt handler mechanism for the PRCM
interrupt, so that individual PRCM event can cleanly be handled by
handlers in separate drivers. We do this by introducing PRCM event
which drivers ? Are those somehow
10 matches
Mail list logo
