From: Dave Gerlach <d-gerlach@ti.com>
To: Tero Kristo <t-kristo@ti.com>,
linux-omap@vger.kernel.org, tony@atomide.com, paul@pwsan.com,
s-anna@ti.com
Cc: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/2] ARM: AM43xx: PRM: fix reset handling issues
Date: Tue, 5 May 2015 11:32:26 -0500 [thread overview]
Message-ID: <5548F09A.10401@ti.com> (raw)
In-Reply-To: <1430832785-1976-1-git-send-email-t-kristo@ti.com>
Tero,
On 05/05/2015 08:33 AM, Tero Kristo wrote:
> Hi,
>
> The work done for consolidating PRM code introduced a reset issue
> on AM43xx which is visible at least with wkup-m3, and prevents
> taking the wkup-m3 core out from reset. Fixed by passing all the
> relevant PRCM data from hwmod data, which was previously partly
> omitted on OMAP4+ case.
>
> This set also removes some redundant AM33xx hwmod code and just
> re-uses the OMAP4+ version of the same.
>
> Thanks to Dave Gerlach and Anna Suman for reporting this. Dave, care
> to give this patch set a try to see if it fixes the problem you see?
>
Thanks for fixing this up, I swapped these patches for my reset patch on my
suspend branch [1] and tested the following:
am335x-gp-evm: boot and firmware loaded, suspend/resume multiple cycles
am437x-gp-evm: boot and firmware loaded, suspend/resume multiple cycles
Patches look fine to me.
Regards,
Dave
[1] https://github.com/dgerlach/linux-pm/tree/pm-ds0-v4.1-rc1-WIP
> Testing done:
> - am335x-bone: boot
> - am437x-gp-evm: boot
> - omap4-panda-es: boot, suspend/resume, cpuidle
>
> -Tero
>
WARNING: multiple messages have this Message-ID (diff)
From: d-gerlach@ti.com (Dave Gerlach)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] ARM: AM43xx: PRM: fix reset handling issues
Date: Tue, 5 May 2015 11:32:26 -0500 [thread overview]
Message-ID: <5548F09A.10401@ti.com> (raw)
In-Reply-To: <1430832785-1976-1-git-send-email-t-kristo@ti.com>
Tero,
On 05/05/2015 08:33 AM, Tero Kristo wrote:
> Hi,
>
> The work done for consolidating PRM code introduced a reset issue
> on AM43xx which is visible at least with wkup-m3, and prevents
> taking the wkup-m3 core out from reset. Fixed by passing all the
> relevant PRCM data from hwmod data, which was previously partly
> omitted on OMAP4+ case.
>
> This set also removes some redundant AM33xx hwmod code and just
> re-uses the OMAP4+ version of the same.
>
> Thanks to Dave Gerlach and Anna Suman for reporting this. Dave, care
> to give this patch set a try to see if it fixes the problem you see?
>
Thanks for fixing this up, I swapped these patches for my reset patch on my
suspend branch [1] and tested the following:
am335x-gp-evm: boot and firmware loaded, suspend/resume multiple cycles
am437x-gp-evm: boot and firmware loaded, suspend/resume multiple cycles
Patches look fine to me.
Regards,
Dave
[1] https://github.com/dgerlach/linux-pm/tree/pm-ds0-v4.1-rc1-WIP
> Testing done:
> - am335x-bone: boot
> - am437x-gp-evm: boot
> - omap4-panda-es: boot, suspend/resume, cpuidle
>
> -Tero
>
next prev parent reply other threads:[~2015-05-05 16:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-05 13:33 [PATCH 0/2] ARM: AM43xx: PRM: fix reset handling issues Tero Kristo
2015-05-05 13:33 ` Tero Kristo
2015-05-05 13:33 ` [PATCH 1/2] ARM: OMAP4+: PRM: add support for passing status register/bit info to reset Tero Kristo
2015-05-05 13:33 ` Tero Kristo
2015-05-05 16:47 ` Suman Anna
2015-05-05 16:47 ` Suman Anna
2015-05-08 17:51 ` Paul Walmsley
2015-05-08 17:51 ` Paul Walmsley
2015-05-08 17:48 ` Paul Walmsley
2015-05-08 17:48 ` Paul Walmsley
2015-05-05 13:33 ` [PATCH 2/2] ARM: AM33xx+: hwmod: re-use omap4 implementations for reset functionality Tero Kristo
2015-05-05 13:33 ` Tero Kristo
2015-05-08 17:49 ` Paul Walmsley
2015-05-08 17:49 ` Paul Walmsley
2015-05-05 16:32 ` Dave Gerlach [this message]
2015-05-05 16:32 ` [PATCH 0/2] ARM: AM43xx: PRM: fix reset handling issues Dave Gerlach
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=5548F09A.10401@ti.com \
--to=d-gerlach@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
--cc=s-anna@ti.com \
--cc=t-kristo@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.