All of lore.kernel.org
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: Timur Tabi <b04825@freescale.com>
Cc: Wood Scott-B07421 <B07421@freescale.com>,
	Li Yang-R58472 <r58472@freescale.com>,
	Zhao Chenhui-B35336 <B35336@freescale.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH v6 1/5] powerpc/85xx: implement hardware timebase sync
Date: Fri, 29 Jun 2012 11:10:43 -0500	[thread overview]
Message-ID: <4FEDD383.40804@freescale.com> (raw)
In-Reply-To: <4FEDD1F0.1060000@freescale.com>

On 06/29/2012 11:04 AM, Timur Tabi wrote:
> Scott Wood wrote:
> 
>>> I wonder if it's possible to dynamically generate the compatible
>>> string by using the SOC name?
>>
>> Where are you going to get the SoC name from?
> 
> Well, that is why I said "I wonder".   I'm disappointed that the "cpus"
> node doesn't help much.  You'd think the name of the CPU would be in the
> CPU node somewhere.

The SoC is not the CPU.  The CPU is e500v2.

Why is this different from anywhere else where we have a list of
compatibles to match, often based on various SoCs?  Note that we
explicitly want to match only certain SoCs here.

-Scott

WARNING: multiple messages have this Message-ID (diff)
From: Scott Wood <scottwood@freescale.com>
To: Timur Tabi <b04825@freescale.com>
Cc: Zhao Chenhui-B35336 <B35336@freescale.com>,
	"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
	Wood Scott-B07421 <B07421@freescale.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"galak@kernel.crashing.org" <galak@kernel.crashing.org>,
	Li Yang-R58472 <r58472@freescale.com>
Subject: Re: [PATCH v6 1/5] powerpc/85xx: implement hardware timebase sync
Date: Fri, 29 Jun 2012 11:10:43 -0500	[thread overview]
Message-ID: <4FEDD383.40804@freescale.com> (raw)
In-Reply-To: <4FEDD1F0.1060000@freescale.com>

On 06/29/2012 11:04 AM, Timur Tabi wrote:
> Scott Wood wrote:
> 
>>> I wonder if it's possible to dynamically generate the compatible
>>> string by using the SOC name?
>>
>> Where are you going to get the SoC name from?
> 
> Well, that is why I said "I wonder".   I'm disappointed that the "cpus"
> node doesn't help much.  You'd think the name of the CPU would be in the
> CPU node somewhere.

The SoC is not the CPU.  The CPU is e500v2.

Why is this different from anywhere else where we have a list of
compatibles to match, often based on various SoCs?  Note that we
explicitly want to match only certain SoCs here.

-Scott


  reply	other threads:[~2012-06-29 16:11 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-26 10:25 [PATCH v6 1/5] powerpc/85xx: implement hardware timebase sync Zhao Chenhui
2012-06-26 10:25 ` Zhao Chenhui
2012-06-26 10:25 ` [PATCH v6 2/5] powerpc/85xx: add HOTPLUG_CPU support Zhao Chenhui
2012-06-26 10:25   ` Zhao Chenhui
2012-06-26 10:25 ` [PATCH v6 3/5] powerpc/85xx: add sleep and deep sleep support Zhao Chenhui
2012-06-26 10:25   ` Zhao Chenhui
2012-07-13 12:27   ` Kumar Gala
2012-07-13 12:27     ` Kumar Gala
2012-06-26 10:25 ` [PATCH v6 4/5] fsl_pmc: Add API to enable device as wakeup event source Zhao Chenhui
2012-06-26 10:25   ` Zhao Chenhui
2012-06-26 10:25 ` [PATCH v6 5/5] powerpc/85xx: add support to JOG feature using cpufreq interface Zhao Chenhui
2012-06-26 10:25   ` Zhao Chenhui
2012-06-26 14:03 ` [PATCH v6 1/5] powerpc/85xx: implement hardware timebase sync Kumar Gala
2012-06-26 14:03   ` Kumar Gala
2012-06-26 21:45   ` Scott Wood
2012-06-26 21:45     ` Scott Wood
2012-06-26 22:10     ` Benjamin Herrenschmidt
2012-06-26 22:10       ` Benjamin Herrenschmidt
2012-06-27 10:10   ` Zhao Chenhui
2012-06-27 10:10     ` Zhao Chenhui
2012-06-26 22:10 ` Benjamin Herrenschmidt
2012-06-26 22:10   ` Benjamin Herrenschmidt
2012-06-27 10:21   ` Zhao Chenhui
2012-06-27 10:21     ` Zhao Chenhui
2012-06-27 11:48     ` Benjamin Herrenschmidt
2012-06-27 11:48       ` Benjamin Herrenschmidt
2012-06-28  3:38       ` Zhao Chenhui
2012-06-28  3:38         ` Zhao Chenhui
2012-06-28 10:50         ` Benjamin Herrenschmidt
2012-06-28 10:50           ` Benjamin Herrenschmidt
2012-06-28 18:30           ` Kumar Gala
2012-06-28 18:30             ` Kumar Gala
2012-06-29 10:33             ` Zhao Chenhui-B35336
2012-06-29 10:33               ` Zhao Chenhui-B35336
2012-07-02 10:44           ` Zhao Chenhui
2012-07-02 10:44             ` Zhao Chenhui
2012-06-29 15:39 ` Tabi Timur-B04825
2012-06-29 15:39   ` Tabi Timur-B04825
2012-06-29 15:57   ` Scott Wood
2012-06-29 15:57     ` Scott Wood
2012-06-29 16:04     ` Timur Tabi
2012-06-29 16:04       ` Timur Tabi
2012-06-29 16:10       ` Scott Wood [this message]
2012-06-29 16:10         ` Scott Wood
2012-06-29 16:12         ` Timur Tabi
2012-06-29 16:12           ` Timur Tabi
2012-06-29 17:10           ` Scott Wood
2012-06-29 17:10             ` Scott Wood
2012-07-02 10:10   ` Zhao Chenhui
2012-07-02 10:10     ` Zhao Chenhui

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=4FEDD383.40804@freescale.com \
    --to=scottwood@freescale.com \
    --cc=B07421@freescale.com \
    --cc=B35336@freescale.com \
    --cc=b04825@freescale.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=r58472@freescale.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.