From: t-kristo@ti.com (Tero Kristo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 00/18] ARM: OMAP2+: CM/PRM cleanup set
Date: Sat, 12 Apr 2014 13:22:54 +0300 [thread overview]
Message-ID: <534913FE.1020802@ti.com> (raw)
In-Reply-To: <1393949958-816-1-git-send-email-t-kristo@ti.com>
On 03/04/2014 06:19 PM, Tero Kristo wrote:
> Hi,
>
> This set cleans up the CM/PRM codebase a bit, removing the need for direct
> CM/PRM register access macros outside CM/PRM drivers. This is done in
> preparation to isolate these drivers into its own driver directory.
> Currently my plan is to create a single PRCM driver, which will contain
> both, and as such, CM/PRM inter-access is not removed in this set.
>
> This set is built on top of the OMAP2 DT clock conversion set, but most
> of the patches can also be standalone if need be.
>
> Testing done:
> - omap2 : none (any feedback welcome)
> - omap3-beagle : boot, suspend-resume (RET), suspend-resume (OFF)
> - omap4-panda-es : boot, suspend-resume (RET)
>
> Branch also available here:
> tree: https://github.com/t-kristo/linux-pm.git
> branch: 3.14-rc4-cm-prm-cleanup
>
> -Tero
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo at vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
Hi,
This work is outdated and is preceded by the stuff here (for the
interested parties):
https://github.com/t-kristo/linux-pm/tree/3.14-rc4-cm-prm-driver-wip
I'll be posting small sets of patches out of here once the pre-reqs for
the WIP branch are covered.
-Tero
prev parent reply other threads:[~2014-04-12 10:22 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-04 16:19 [PATCH 00/18] ARM: OMAP2+: CM/PRM cleanup set Tero Kristo
2014-03-04 16:19 ` [PATCH 01/18] ARM: OMAP3: CM: remove a few OMAP34XX_CM_REGADDR defines Tero Kristo
2014-03-04 16:19 ` [PATCH 02/18] ARM: OMAP2+: prcm: add omap_test_timeout to prcm-common.h Tero Kristo
2014-03-04 16:19 ` [PATCH 03/18] ARM: OMAP2/3: CM: remove some external dependencies Tero Kristo
2014-03-04 16:19 ` [PATCH 04/18] ARM: OMAP3: PRM: move prcm wakeup helper to prm driver Tero Kristo
2014-03-04 16:19 ` [PATCH 05/18] ARM: OMAP3: PRM: move iva reset to PRM driver Tero Kristo
2014-03-04 16:19 ` [PATCH 06/18] ARM: OMAP3: PRM: move modem " Tero Kristo
2014-03-04 16:19 ` [PATCH 07/18] ARM: OMAP2/3: CM: remove direct register access macros from common header Tero Kristo
2014-03-04 16:19 ` [PATCH 08/18] ARM: OMAP3: PRM: add API for checking and clearing cold reset status Tero Kristo
2014-03-04 16:19 ` [PATCH 09/18] ARM: OMAP3: PRM: add API for saving PRM scratchpad contents Tero Kristo
2014-03-04 16:19 ` [PATCH 10/18] ARM: OMAP24xx: PRM: add API for clearing wakeup status bits Tero Kristo
2014-03-04 16:19 ` [PATCH 11/18] ARM: OMAP24xx: PRM: move PRM init code within PRM driver from PM core Tero Kristo
2014-03-04 16:19 ` [PATCH 12/18] ARM: OMAP3: PM: remove access to PRM_VOLTCTRL register Tero Kristo
2014-03-25 22:36 ` Tony Lindgren
2014-03-26 8:00 ` Tero Kristo
2014-03-26 18:40 ` Tony Lindgren
2014-03-04 16:19 ` [PATCH 13/18] ARM: OMAP3: PRM: move PRM init code from PM core to the driver Tero Kristo
2014-03-04 16:19 ` [PATCH 14/18] ARM: OMAP2/3: PRM: split PRM header file to common and internal versions Tero Kristo
2014-03-04 16:19 ` [PATCH 15/18] ARM: OMAP4+: PRM: make prm register access internal to PRM driver only Tero Kristo
2014-03-04 16:19 ` [PATCH 16/18] ARM: OMAP3: control: add API for setting up the modem pads Tero Kristo
2014-03-04 16:19 ` [PATCH 17/18] ARM: OMAP3: PRM: move modem reset and iva2 idle to PRM driver Tero Kristo
2014-03-04 16:19 ` [PATCH 18/18] ARM: OMAP3: control: isolate control module init to its own function Tero Kristo
2014-03-05 17:36 ` [PATCH 00/18] ARM: OMAP2+: CM/PRM cleanup set Tony Lindgren
2014-04-12 10:22 ` Tero Kristo [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=534913FE.1020802@ti.com \
--to=t-kristo@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).