All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nishanth Menon <nm@ti.com>
To: Dave Gerlach <d-gerlach@ti.com>
Cc: Tony Lindgren <tony@atomide.com>, Sekhar Nori <nsekhar@ti.com>,
	Santosh Shilimkar <santosh.shilimkar@ti.com>,
	Benoit Cousson <bcousson@baylibre.com>,
	linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 0/3] OMAP4+: Get rid of internal SRAM handling
Date: Wed, 10 Sep 2014 11:56:43 -0500	[thread overview]
Message-ID: <20140910165643.GA3118@splat> (raw)
In-Reply-To: <cover.1410362895.git.d-gerlach@ti.com>

On 11:04-20140910, Dave Gerlach wrote:
> v3:
> Fix minor issue in last patch to check for null sram_pool if no sram
> phandle is given in DT.
> 
> Make all OMAP DT only platforms (am33xx, am43xx, omap4 and omap5)
> use drivers/misc/sram.c driver instead of the omap internal
> implementation for SRAM handling.
> 
> Previous discussion can be found at [1].
> 
> Regards,
> Dave
> 
> [1] http://lists.infradead.org/pipermail/linux-arm-kernel/2013-August/195588.html
> 
> Rajendra Nayak (3):
>   ARM: AM335x: Get rid of unused sram init function
>   ARM: OMAP4+: Move SRAM data to DT
>   ARM: OMAP4+: Remove static iotable mappings for SRAM
> 
>  Documentation/devicetree/bindings/arm/omap/mpu.txt |  3 ++
>  arch/arm/boot/dts/am33xx.dtsi                      |  5 ++-
>  arch/arm/boot/dts/am4372.dtsi                      |  5 +++
>  arch/arm/boot/dts/omap4.dtsi                       |  6 ++++
>  arch/arm/boot/dts/omap5.dtsi                       |  8 ++++-
>  arch/arm/configs/omap2plus_defconfig               |  1 +
>  arch/arm/mach-omap2/io.c                           | 17 ----------
>  arch/arm/mach-omap2/omap4-common.c                 | 22 +++++++++++-
>  arch/arm/mach-omap2/sram.c                         | 39 +---------------------
>  arch/arm/mach-omap2/sram.h                         |  7 ----
>  10 files changed, 46 insertions(+), 67 deletions(-)
> 

Could you please provide logs for the following:
a) Low power transition tests for OMAP3,4 on all available platforms as
well?
b) provide bootlogs on all omap2plus platforms to ensure we have no
regressions.

-- 
Regards,
Nishanth Menon

WARNING: multiple messages have this Message-ID (diff)
From: nm@ti.com (Nishanth Menon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 0/3] OMAP4+: Get rid of internal SRAM handling
Date: Wed, 10 Sep 2014 11:56:43 -0500	[thread overview]
Message-ID: <20140910165643.GA3118@splat> (raw)
In-Reply-To: <cover.1410362895.git.d-gerlach@ti.com>

On 11:04-20140910, Dave Gerlach wrote:
> v3:
> Fix minor issue in last patch to check for null sram_pool if no sram
> phandle is given in DT.
> 
> Make all OMAP DT only platforms (am33xx, am43xx, omap4 and omap5)
> use drivers/misc/sram.c driver instead of the omap internal
> implementation for SRAM handling.
> 
> Previous discussion can be found at [1].
> 
> Regards,
> Dave
> 
> [1] http://lists.infradead.org/pipermail/linux-arm-kernel/2013-August/195588.html
> 
> Rajendra Nayak (3):
>   ARM: AM335x: Get rid of unused sram init function
>   ARM: OMAP4+: Move SRAM data to DT
>   ARM: OMAP4+: Remove static iotable mappings for SRAM
> 
>  Documentation/devicetree/bindings/arm/omap/mpu.txt |  3 ++
>  arch/arm/boot/dts/am33xx.dtsi                      |  5 ++-
>  arch/arm/boot/dts/am4372.dtsi                      |  5 +++
>  arch/arm/boot/dts/omap4.dtsi                       |  6 ++++
>  arch/arm/boot/dts/omap5.dtsi                       |  8 ++++-
>  arch/arm/configs/omap2plus_defconfig               |  1 +
>  arch/arm/mach-omap2/io.c                           | 17 ----------
>  arch/arm/mach-omap2/omap4-common.c                 | 22 +++++++++++-
>  arch/arm/mach-omap2/sram.c                         | 39 +---------------------
>  arch/arm/mach-omap2/sram.h                         |  7 ----
>  10 files changed, 46 insertions(+), 67 deletions(-)
> 

Could you please provide logs for the following:
a) Low power transition tests for OMAP3,4 on all available platforms as
well?
b) provide bootlogs on all omap2plus platforms to ensure we have no
regressions.

-- 
Regards,
Nishanth Menon

  parent reply	other threads:[~2014-09-10 16:56 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-10 16:04 [PATCH v3 0/3] OMAP4+: Get rid of internal SRAM handling Dave Gerlach
2014-09-10 16:04 ` Dave Gerlach
2014-09-10 16:04 ` [PATCH v3 1/3] ARM: AM335x: Get rid of unused sram init function Dave Gerlach
2014-09-10 16:04   ` Dave Gerlach
2014-09-10 16:04 ` [PATCH v3 2/3] ARM: OMAP4+: Move SRAM data to DT Dave Gerlach
2014-09-10 16:04   ` Dave Gerlach
2014-09-10 16:04 ` [PATCH v3 3/3] ARM: OMAP4+: Remove static iotable mappings for SRAM Dave Gerlach
2014-09-10 16:04   ` Dave Gerlach
2014-09-10 16:56 ` Nishanth Menon [this message]
2014-09-10 16:56   ` [PATCH v3 0/3] OMAP4+: Get rid of internal SRAM handling Nishanth Menon
2014-09-12 18:47   ` Dave Gerlach
2014-09-12 18:47     ` Dave Gerlach
2014-09-18 16:48     ` Tony Lindgren
2014-09-18 16:48       ` 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=20140910165643.GA3118@splat \
    --to=nm@ti.com \
    --cc=bcousson@baylibre.com \
    --cc=d-gerlach@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=nsekhar@ti.com \
    --cc=santosh.shilimkar@ti.com \
    --cc=tony@atomide.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.