public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: nm@ti•com (Nishanth Menon)
To: linux-arm-kernel@lists•infradead.org
Subject: [RFC PATCH 0/7] ARM: OMAP4+: PRM: minor cleanups and dt support of interrupts
Date: Tue, 17 Jun 2014 10:38:48 -0500	[thread overview]
Message-ID: <53A06108.9010108@ti.com> (raw)
In-Reply-To: <1402025761-16831-1-git-send-email-nm@ti.com>

On 06/05/2014 10:35 PM, Nishanth Menon wrote:
> 
> Hi,
> 
> The following series is a minimal set of cleanups and generalization
> in the direction of supporting daisychain wakeup on all OMAP4+
> platforms. We cannot still add IO_WAKEUP ability for OMAP5/DRA7/AM437x
> yet pending further pinctrl patches.
> 
> These do have a few cosmetic issues, but hope is to get a view about
> the approach. Also note that documentation of bindings for ti,dra7-prm
> etc are still pending.
> 
> Nishanth Menon (7):
>   ARM: OMAP4+: prminst: provide function to find prm_dev instance
>     offset
>   ARM: OMAP4: prm use the generic prm_inst to allow logic to be
>     abstracted
>   ARM: OMAP4+: PRM: remove "wkup" event
>   ARM: OMAP4+: PRM: register interrupt information from DT
>   ARM: dts: OMAP4: Add PRM interrupt
>   ARM: dts: OMAP5: add PRM interrupt
>   ARM: dts: DRA7: add PRM interrupt
> 
>  arch/arm/boot/dts/dra7.dtsi       |    1 +
>  arch/arm/boot/dts/omap4.dtsi      |    1 +
>  arch/arm/boot/dts/omap5.dtsi      |    1 +
>  arch/arm/mach-omap2/prm44xx.c     |   89 ++++++++++++++++++++++++++++++++-----
>  arch/arm/mach-omap2/prminst44xx.c |   41 ++++++++++-------
>  arch/arm/mach-omap2/prminst44xx.h |    3 ++
>  6 files changed, 111 insertions(+), 25 deletions(-)
> 
Gentle ping on this series? are we ok with this approach?

-- 
Regards,
Nishanth Menon

      parent reply	other threads:[~2014-06-17 15:38 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-06  3:35 [RFC PATCH 0/7] ARM: OMAP4+: PRM: minor cleanups and dt support of interrupts Nishanth Menon
2014-06-06  3:35 ` [RFC PATCH 1/7] ARM: OMAP4+: prminst: provide function to find prm_dev instance offset Nishanth Menon
2014-06-06  3:35 ` [RFC PATCH 2/7] ARM: OMAP4: prm use the generic prm_inst to allow logic to be abstracted Nishanth Menon
2014-06-06  3:35 ` [RFC PATCH 3/7] ARM: OMAP4+: PRM: remove "wkup" event Nishanth Menon
2014-07-21 10:44   ` Tony Lindgren
2014-07-21 11:17     ` Nishanth Menon
2014-06-06  3:35 ` [RFC PATCH 4/7] ARM: OMAP4+: PRM: register interrupt information from DT Nishanth Menon
2014-07-21 10:51   ` Tony Lindgren
2014-07-21 11:22     ` Nishanth Menon
2014-07-21 11:28       ` Tony Lindgren
2014-07-21 12:08         ` Nishanth Menon
2014-07-21 12:31           ` Tony Lindgren
2014-06-06  3:35 ` [RFC PATCH 5/7] ARM: dts: OMAP4: Add PRM interrupt Nishanth Menon
2014-06-06  3:36 ` [RFC PATCH 6/7] ARM: dts: OMAP5: add " Nishanth Menon
2014-06-06  3:36 ` [RFC PATCH 7/7] ARM: dts: DRA7: " Nishanth Menon
2014-06-17 15:38 ` Nishanth Menon [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=53A06108.9010108@ti.com \
    --to=nm@ti$(echo .)com \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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