From: Tony Lindgren <tony@atomide.com>
To: Nishanth Menon <nm@ti.com>
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org
Subject: Re: [PATCH 0/3] ARM: OMAP: DRA7: Update to latest TRM and cleanup
Date: Fri, 10 Jun 2016 02:34:00 -0700 [thread overview]
Message-ID: <20160610093359.GQ22406@atomide.com> (raw)
In-Reply-To: <1464096940-27145-1-git-send-email-nm@ti.com>
Hi,
* Nishanth Menon <nm@ti.com> [160524 06:37]:
> Hi,
>
> Here are the final(hopefully) pending patches for DRA7 based on recent
> TRM updates. Updates include removing retention support on L3init and
> L4per as per latest SoC updates.
>
> Test Log: X15 (no modules): http://pastebin.ubuntu.com/16655027/
>
> Latest TRM (rev F): http://www.ti.com/lit/pdf/spruhz6 (public on May 18)
>
> Nishanth Menon (3):
> ARM: OMAP: DRA7: powerdomain data: Set L3init and L4per to ON
> ARM: OMAP: DRA7: powerdomain data: Remove unused pwrsts_logic_ret
> ARM: OMAP: DRA7: powerdomain data: Remove unused pwrsts_mem_ret
>
> arch/arm/mach-omap2/powerdomains7xx_data.c | 76 +-----------------------------
> 1 file changed, 2 insertions(+), 74 deletions(-)
Can these wait until v4.8 merge window, are this needed as fixes to
avoid hardware problems?
Regards,
Tony
next prev parent reply other threads:[~2016-06-10 9:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-24 13:35 [PATCH 0/3] ARM: OMAP: DRA7: Update to latest TRM and cleanup Nishanth Menon
2016-05-24 13:35 ` [PATCH 1/3] ARM: OMAP: DRA7: powerdomain data: Set L3init and L4per to ON Nishanth Menon
2016-05-24 13:35 ` [PATCH 2/3] ARM: OMAP: DRA7: powerdomain data: Remove unused pwrsts_logic_ret Nishanth Menon
2016-05-24 13:35 ` [PATCH 3/3] ARM: OMAP: DRA7: powerdomain data: Remove unused pwrsts_mem_ret Nishanth Menon
2016-06-10 9:34 ` Tony Lindgren [this message]
2016-06-10 14:18 ` [PATCH 0/3] ARM: OMAP: DRA7: Update to latest TRM and cleanup Nishanth Menon
2016-06-13 8:42 ` 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=20160610093359.GQ22406@atomide.com \
--to=tony@atomide.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
/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