From: Tony Lindgren <tony@atomide.com>
To: Ruslan Bilovol <ruslan.bilovol@ti.com>
Cc: linux@arm.linux.org.uk, b-cousson@ti.com, paul@pwsan.com,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
keshava_mgowda@ti.com
Subject: Re: [PATCH] ARM: OMAP2+: mux: add support for PAD wakeup event handler
Date: Mon, 10 Sep 2012 11:39:44 -0700 [thread overview]
Message-ID: <20120910183943.GA1303@atomide.com> (raw)
In-Reply-To: <1347273528-2056-1-git-send-email-ruslan.bilovol@ti.com>
* Ruslan Bilovol <ruslan.bilovol@ti.com> [120910 03:39]:
> OMAP mux now parses active wakeup events from pad registers and calls
> corresponding handler, if handler is not registered - corresponding
> hwmod ISRs once a wakeup is detected.
> This is useful for cases when routing wakeups to corresponding hwmod
> ISRs complicates those ISRs handlers (for example, ISR handler may
> not know who the interrupt source is)
The mux code in arch/arm/mach-omap2 will be going away and replaced
by device tree based pinctrl-single. It's not a good idea to add more
dependencies to custom frameworks as that just makes the transition
harder on us.
Regards,
Tony
WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: OMAP2+: mux: add support for PAD wakeup event handler
Date: Mon, 10 Sep 2012 11:39:44 -0700 [thread overview]
Message-ID: <20120910183943.GA1303@atomide.com> (raw)
In-Reply-To: <1347273528-2056-1-git-send-email-ruslan.bilovol@ti.com>
* Ruslan Bilovol <ruslan.bilovol@ti.com> [120910 03:39]:
> OMAP mux now parses active wakeup events from pad registers and calls
> corresponding handler, if handler is not registered - corresponding
> hwmod ISRs once a wakeup is detected.
> This is useful for cases when routing wakeups to corresponding hwmod
> ISRs complicates those ISRs handlers (for example, ISR handler may
> not know who the interrupt source is)
The mux code in arch/arm/mach-omap2 will be going away and replaced
by device tree based pinctrl-single. It's not a good idea to add more
dependencies to custom frameworks as that just makes the transition
harder on us.
Regards,
Tony
next prev parent reply other threads:[~2012-09-10 18:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-10 10:38 [PATCH] ARM: OMAP2+: mux: add support for PAD wakeup event handler Ruslan Bilovol
2012-09-10 10:38 ` Ruslan Bilovol
2012-09-10 10:51 ` Munegowda, Keshava
2012-09-10 10:51 ` Munegowda, Keshava
2012-09-10 18:39 ` Tony Lindgren [this message]
2012-09-10 18:39 ` Tony Lindgren
2012-09-11 7:42 ` Munegowda, Keshava
2012-09-11 7:42 ` Munegowda, Keshava
2012-09-11 16:27 ` Tony Lindgren
2012-09-11 16:27 ` Tony Lindgren
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=20120910183943.GA1303@atomide.com \
--to=tony@atomide.com \
--cc=b-cousson@ti.com \
--cc=keshava_mgowda@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=paul@pwsan.com \
--cc=ruslan.bilovol@ti.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.