From: rnayak@ti.com (Rajendra Nayak)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/4] OMAP2+: Cleanup PRM and CM regbit headers
Date: Fri, 5 Jul 2013 16:02:33 +0530 [thread overview]
Message-ID: <1373020357-13528-1-git-send-email-rnayak@ti.com> (raw)
Over the years the PRM and CM headers for OMAP have been growing largely
due to autogeneration which creates headers for complete PRM and
CM register space, regardless of the actual usage of these registers in
the kernel.
The PRM and CM regbit headers in particular were found to be around
90% unused and hence this series is an attempt to clean all unsued
data from these headers.
Rajendra Nayak (4):
ARM: OMAP2: PRM/CM: Cleanup unused header
ARM: OMAP3: PRM/CM: Cleanup unused header
ARM: OMAP4: PRM/CM: Cleanup unused header
ARM: OMAP5: PRM/CM: Cleanup unused header
arch/arm/mach-omap2/cm-regbits-24xx.h | 318 ----
arch/arm/mach-omap2/cm-regbits-33xx.h | 749 --------
arch/arm/mach-omap2/cm-regbits-34xx.h | 632 -------
arch/arm/mach-omap2/cm-regbits-44xx.h | 1558 ---------------
arch/arm/mach-omap2/cm-regbits-54xx.h | 1633 ----------------
arch/arm/mach-omap2/omap_hwmod_54xx_data.c | 1 -
arch/arm/mach-omap2/powerdomains54xx_data.c | 1 -
arch/arm/mach-omap2/prm-regbits-24xx.h | 247 ---
arch/arm/mach-omap2/prm-regbits-33xx.h | 306 ---
arch/arm/mach-omap2/prm-regbits-34xx.h | 481 -----
arch/arm/mach-omap2/prm-regbits-44xx.h | 2226 ----------------------
arch/arm/mach-omap2/prm-regbits-54xx.h | 2701 ---------------------------
12 files changed, 10853 deletions(-)
delete mode 100644 arch/arm/mach-omap2/prm-regbits-54xx.h
--
1.7.9.5
next reply other threads:[~2013-07-05 10:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-05 10:32 Rajendra Nayak [this message]
2013-07-05 10:32 ` [PATCH 1/4] ARM: OMAP2: PRM/CM: Cleanup unused header Rajendra Nayak
2013-07-05 10:32 ` [PATCH 2/4] ARM: OMAP3: " Rajendra Nayak
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=1373020357-13528-1-git-send-email-rnayak@ti.com \
--to=rnayak@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).