From: Nathan Fontenot <nfont@linux.vnet.ibm.com>
To: Tyrel Datwyler <tyreld@linux.vnet.ibm.com>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v2 1/3] powerpc/pseries: Device tree should only be updated once after suspend/migrate
Date: Tue, 28 Jan 2014 13:44:39 -0600 [thread overview]
Message-ID: <52E808A7.7090006@linux.vnet.ibm.com> (raw)
In-Reply-To: <1390420717-23907-2-git-send-email-tyreld@linux.vnet.ibm.com>
On 01/22/2014 01:58 PM, Tyrel Datwyler wrote:
> From: Haren Myneni <hbabu@us.ibm.com>
>
> From: Haren Myneni <hbabu@us.ibm.com>
>
> The current code makes rtas calls for update-nodes, activate-firmware and then
> update-nodes again. The FW provides the same data for both update-nodes calls.
> As a result a proc entry exists error is reported for the second update while
> adding device nodes.
>
> This patch makes a single rtas call for update-nodes after activating the FW.
> It also add rtas_busy delay for the activate-firmware rtas call.
>
> Signed-off-by: Haren Myneni <hbabu@us.ibm.com>
> Signed-off-by: Tyrel Datwyler <tyreld@linux.vnet.ibm.com>
Acked-by: Nathan fontenot <nfont@linux.vnet.ibm.com>
> ---
> arch/powerpc/platforms/pseries/mobility.c | 26 ++++++++++----------------
> 1 file changed, 10 insertions(+), 16 deletions(-)
>
> diff --git a/arch/powerpc/platforms/pseries/mobility.c b/arch/powerpc/platforms/pseries/mobility.c
> index cde4e0a..bde7eba 100644
> --- a/arch/powerpc/platforms/pseries/mobility.c
> +++ b/arch/powerpc/platforms/pseries/mobility.c
> @@ -290,13 +290,6 @@ void post_mobility_fixup(void)
> int rc;
> int activate_fw_token;
>
> - rc = pseries_devicetree_update(MIGRATION_SCOPE);
> - if (rc) {
> - printk(KERN_ERR "Initial post-mobility device tree update "
> - "failed: %d\n", rc);
> - return;
> - }
> -
> activate_fw_token = rtas_token("ibm,activate-firmware");
> if (activate_fw_token == RTAS_UNKNOWN_SERVICE) {
> printk(KERN_ERR "Could not make post-mobility "
> @@ -304,16 +297,17 @@ void post_mobility_fixup(void)
> return;
> }
>
> - rc = rtas_call(activate_fw_token, 0, 1, NULL);
> - if (!rc) {
> - rc = pseries_devicetree_update(MIGRATION_SCOPE);
> - if (rc)
> - printk(KERN_ERR "Secondary post-mobility device tree "
> - "update failed: %d\n", rc);
> - } else {
> + do {
> + rc = rtas_call(activate_fw_token, 0, 1, NULL);
> + } while (rtas_busy_delay(rc));
> +
> + if (rc)
> printk(KERN_ERR "Post-mobility activate-fw failed: %d\n", rc);
> - return;
> - }
> +
> + rc = pseries_devicetree_update(MIGRATION_SCOPE);
> + if (rc)
> + printk(KERN_ERR "Post-mobility device tree update "
> + "failed: %d\n", rc);
>
> return;
> }
>
next prev parent reply other threads:[~2014-01-28 19:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-22 19:58 [PATCH v2 0/3] powerpc/pseries: fix issues in suspend/resume code Tyrel Datwyler
2014-01-22 19:58 ` [PATCH v2 1/3] powerpc/pseries: Device tree should only be updated once after suspend/migrate Tyrel Datwyler
2014-01-28 19:44 ` Nathan Fontenot [this message]
2014-01-22 19:58 ` [PATCH v2 2/3] powerpc/pseries: Update dynamic cache nodes for suspend/resume operation Tyrel Datwyler
2014-01-28 19:41 ` Nathan Fontenot
2014-01-22 19:58 ` [PATCH v2 3/3] powerpc/pseries: Report in kernel device tree update to drmgr Tyrel Datwyler
2014-01-28 19:45 ` Nathan Fontenot
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=52E808A7.7090006@linux.vnet.ibm.com \
--to=nfont@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=tyreld@linux.vnet.ibm.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.