linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Nathan Lynch <ntl@pobox.com>
To: linuxppc-dev@ozlabs.org
Subject: [PATCH 2/3] convert cpu_to_l2cache() to of_find_next_cache_node()
Date: Wed, 10 Dec 2008 18:46:05 -0600	[thread overview]
Message-ID: <1228956366-17593-2-git-send-email-ntl@pobox.com> (raw)
In-Reply-To: <1228956366-17593-1-git-send-email-ntl@pobox.com>

The smp code uses cache information to populate cpu_core_map; change
it to use common code for cache lookup.

Signed-off-by: Nathan Lynch <ntl@pobox.com>
---
 arch/powerpc/kernel/smp.c |   10 +---------
 1 files changed, 1 insertions(+), 9 deletions(-)

diff --git a/arch/powerpc/kernel/smp.c b/arch/powerpc/kernel/smp.c
index ff9f701..450865b 100644
--- a/arch/powerpc/kernel/smp.c
+++ b/arch/powerpc/kernel/smp.c
@@ -408,8 +408,6 @@ out:
 static struct device_node *cpu_to_l2cache(int cpu)
 {
 	struct device_node *np;
-	const phandle *php;
-	phandle ph;
 
 	if (!cpu_present(cpu))
 		return NULL;
@@ -418,13 +416,7 @@ static struct device_node *cpu_to_l2cache(int cpu)
 	if (np == NULL)
 		return NULL;
 
-	php = of_get_property(np, "l2-cache", NULL);
-	if (php == NULL)
-		return NULL;
-	ph = *php;
-	of_node_put(np);
-
-	return of_find_node_by_phandle(ph);
+	return of_find_next_cache_node(np);
 }
 
 /* Activate a secondary processor. */
-- 
1.5.5

  reply	other threads:[~2008-12-11  0:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-11  0:46 [PATCH 1/3] add of_find_next_cache_node() Nathan Lynch
2008-12-11  0:46 ` Nathan Lynch [this message]
2008-12-11  1:42   ` [PATCH 2/3] convert cpu_to_l2cache() to of_find_next_cache_node() Stephen Rothwell
2008-12-11  2:00     ` Nathan Lynch
2008-12-11  6:16   ` [PATCH 2/3 v2] " Nathan Lynch
2008-12-11  0:46 ` [PATCH 3/3] convert sysfs cache code " Nathan Lynch
2008-12-14 23:11 ` [PATCH 1/3] add of_find_next_cache_node() Benjamin Herrenschmidt
2008-12-14 23:19   ` Nathan Lynch
2008-12-15 22:33   ` Nathan Lynch
2008-12-15 23:33     ` Benjamin Herrenschmidt
2008-12-16  0:07       ` Nathan Lynch

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=1228956366-17593-2-git-send-email-ntl@pobox.com \
    --to=ntl@pobox.com \
    --cc=linuxppc-dev@ozlabs.org \
    /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;
as well as URLs for NNTP newsgroup(s).