From: khilman@ti•com (Kevin Hilman)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCHv3 0/6] ARM: OMAP3PLUS: IO daisychain support fixes
Date: Mon, 05 Mar 2012 16:32:21 -0800 [thread overview]
Message-ID: <877gyyin6y.fsf@ti.com> (raw)
In-Reply-To: <1330525621-29836-1-git-send-email-t-kristo@ti.com> (Tero Kristo's message of "Wed, 29 Feb 2012 16:26:55 +0200")
Tero Kristo <t-kristo@ti•com> writes:
> Hi,
>
> The previous version of this set was sent by Vishwanath BS, but as he
> is busy with other stuff, I am taking over.
>
> Some basic info about this set based on comments received on set v2.
> IO chain is now enabled always, and a re-trigger for the chain is
> done during hwmod enable / disable. This means that IO chain is always
> armed according to the latest pad specific WAKE_ENABLE setting, and
> if it is modified, the IO chain needs to be re-armed (thus the hooks
> within omap_hwmod code.) Having IO chain armed all the time allows us
> to receive IO event interrupts even during non-sleep states if the
> corresponding hardware module is disabled, and is unable to detect any
> IO activity itself.
>
> Version 3 contains the following changes:
>
> - global: renamed *_trigger_wuclk_ctrl funcs as *_trigger_io_chain
> - patch 3: added trigger WUCLKIN disable at the end of omap4_trigger_io_chain
> (fix pulled from the omap4 core retention set)
> - patch 5: added function pointer for using machine specific io_chain trigger
> function, initialized during boot
> - patch 7 dropped as the support capability for omap3 is now handled as
> part of patch 5 init
>
> Tested on omap3 beagle + omap4 blaze boards. Suspend / resume works, and
> hwmod_io interrupts are generated. Omap4 was tested with the core retention
> support set.
Reviewed-by: Kevin Hilman <khilman@ti•com>
I also tested this on 3430/n900 and verified IO wakeups are working as
expected.
Tested-by: Kevin Hilman <khilman@ti•com>
Paul, as discussed on IRC, when you're OK with it, this can go through
your queue since it's mostly PRM core code.
Kevin
prev parent reply other threads:[~2012-03-06 0:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-29 14:26 [PATCHv3 0/6] ARM: OMAP3PLUS: IO daisychain support fixes Tero Kristo
2012-02-29 14:26 ` [PATCHv3 1/6] ARM: OMAP3 PM: correct enable/disable of daisy io chain Tero Kristo
2012-02-29 14:26 ` [PATCHv3 2/6] ARM: OMAP3 PM: Move IO Daisychain function to omap3 prm file Tero Kristo
2012-03-01 6:49 ` Rajendra Nayak
2012-03-01 8:28 ` Tero Kristo
2012-03-01 8:43 ` Rajendra Nayak
2012-02-29 14:26 ` [PATCHv3 3/6] ARM: OMAP4 PM: Add IO Daisychain support Tero Kristo
2012-02-29 14:26 ` [PATCHv3 4/6] ARM: OMAP3 PM: Enable IO Wake up Tero Kristo
2012-02-29 17:22 ` Paul Walmsley
2012-03-01 6:52 ` Rajendra Nayak
2012-03-01 8:25 ` Tero Kristo
2012-03-01 22:37 ` Kevin Hilman
2012-03-02 9:19 ` Tero Kristo
2012-03-02 9:23 ` Rajendra Nayak
2012-02-29 14:27 ` [PATCHv3 5/6] ARM: OMAP3PLUS PM: Add IO Daisychain support via hwmod mux Tero Kristo
2012-02-29 14:27 ` [PATCHv3 6/6] ARM: OMAP3 PM: Remove IO Daisychain control from cpuidle Tero Kristo
2012-03-06 0:32 ` Kevin Hilman [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=877gyyin6y.fsf@ti.com \
--to=khilman@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