All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Nishanth Menon <nm@ti.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	linux-omap <linux-omap@vger.kernel.org>
Subject: Re: [PATCH 0/3] ARM: OMAP: DRA7: Update to latest TRM and cleanup
Date: Mon, 13 Jun 2016 01:42:26 -0700	[thread overview]
Message-ID: <20160613084225.GT22406@atomide.com> (raw)
In-Reply-To: <CAGo_u6okpNGkfYno02nCfEsryki5drrhfwnZUj=ycghh62qoTg@mail.gmail.com>

* Nishanth Menon <nm@ti.com> [160610 07:20]:
> On Fri, Jun 10, 2016 at 4:34 AM, Tony Lindgren <tony@atomide.com> wrote:
> > 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?
> 
> Yes - at least patch #1 is a h/w "limitation" and can result in non
> functional SoC after a duration of operation. the patches #2/3 are
> code shrinkage to remove unused data.

OK thanks that's a good reason to have them merged for v4.7.
I've applied them into omap-for-v4.7/fixes and will send a pull
request later today.

Regards,

Tony

WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] ARM: OMAP: DRA7: Update to latest TRM and cleanup
Date: Mon, 13 Jun 2016 01:42:26 -0700	[thread overview]
Message-ID: <20160613084225.GT22406@atomide.com> (raw)
In-Reply-To: <CAGo_u6okpNGkfYno02nCfEsryki5drrhfwnZUj=ycghh62qoTg@mail.gmail.com>

* Nishanth Menon <nm@ti.com> [160610 07:20]:
> On Fri, Jun 10, 2016 at 4:34 AM, Tony Lindgren <tony@atomide.com> wrote:
> > 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?
> 
> Yes - at least patch #1 is a h/w "limitation" and can result in non
> functional SoC after a duration of operation. the patches #2/3 are
> code shrinkage to remove unused data.

OK thanks that's a good reason to have them merged for v4.7.
I've applied them into omap-for-v4.7/fixes and will send a pull
request later today.

Regards,

Tony

  reply	other threads:[~2016-06-13  8:42 UTC|newest]

Thread overview: 18+ 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 ` Nishanth Menon
2016-05-24 13:35 ` 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   ` Nishanth Menon
2016-05-24 13:35   ` 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   ` Nishanth Menon
2016-05-24 13:35   ` Nishanth Menon
2016-05-24 13:35 ` [PATCH 3/3] ARM: OMAP: DRA7: powerdomain data: Remove unused pwrsts_mem_ret Nishanth Menon
2016-05-24 13:35   ` Nishanth Menon
2016-05-24 13:35   ` Nishanth Menon
2016-06-10  9:34 ` [PATCH 0/3] ARM: OMAP: DRA7: Update to latest TRM and cleanup Tony Lindgren
2016-06-10  9:34   ` Tony Lindgren
2016-06-10 14:18   ` Nishanth Menon
2016-06-10 14:18     ` Nishanth Menon
2016-06-13  8:42     ` Tony Lindgren [this message]
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=20160613084225.GT22406@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.