From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] ARM: l2c: OMAP4/AM437x: Additional register programming support.
Date: Fri, 2 Jan 2015 09:38:59 -0800 [thread overview]
Message-ID: <20150102173859.GE3298@atomide.com> (raw)
In-Reply-To: <1420219072-6521-1-git-send-email-nm@ti.com>
* Nishanth Menon <nm@ti.com> [150102 09:20]:
> Hi,
>
> OMAP4 and AM437x ROM code provides services to program PL310's latency
> registers and AM437x provides service for programming Address filter
> registers.
>
> Provide support in the kernel for the same.
>
> This provides some support to the series: http://marc.info/?l=linux-arm-kernel&m=141933190912495&w=2
Are these to be applied before Thomasz's series as fixes? If we
don't need these as fixes for the -rc, then probably makes sense
for RMK to merge them all together for v3.20.
Regards,
Tony
> Nishanth Menon (2):
> ARM: l2c: OMAP4/AM437x: Introduce support for cache latency
> programming
> ARM: l2c: AM437x: Introduce support for cache filter programming
>
> arch/arm/mach-omap2/common.h | 1 +
> arch/arm/mach-omap2/omap-secure.h | 2 ++
> arch/arm/mach-omap2/omap-smc.S | 20 ++++++++++++++++++++
> arch/arm/mach-omap2/omap4-common.c | 36 ++++++++++++++++++++++++++++++++++++
> 4 files changed, 59 insertions(+)
>
> Regards,
> Nishanth Menon
>
> --
> 1.7.9.5
>
next prev parent reply other threads:[~2015-01-02 17:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-02 17:17 [PATCH 0/2] ARM: l2c: OMAP4/AM437x: Additional register programming support Nishanth Menon
2015-01-02 17:17 ` [PATCH 1/2] ARM: l2c: OMAP4/AM437x: Introduce support for cache latency programming Nishanth Menon
2015-01-02 17:17 ` [PATCH 2/2] ARM: l2c: AM437x: Introduce support for cache filter programming Nishanth Menon
2015-01-02 17:38 ` Tony Lindgren [this message]
2015-01-02 17:52 ` [PATCH 0/2] ARM: l2c: OMAP4/AM437x: Additional register programming support Nishanth Menon
2015-01-19 21:28 ` Tony Lindgren
2015-01-19 21:32 ` 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=20150102173859.GE3298@atomide.com \
--to=tony@atomide.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).