From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ch1outboundpool.messaging.microsoft.com (ch1ehsobe003.messaging.microsoft.com [216.32.181.183]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.global.frontbridge.com", Issuer "Microsoft Secure Server Authority" (not verified)) by ozlabs.org (Postfix) with ESMTPS id 8BBF2B6F9D for ; Sat, 30 Jun 2012 02:11:03 +1000 (EST) Message-ID: <4FEDD383.40804@freescale.com> Date: Fri, 29 Jun 2012 11:10:43 -0500 From: Scott Wood MIME-Version: 1.0 To: Timur Tabi Subject: Re: [PATCH v6 1/5] powerpc/85xx: implement hardware timebase sync References: <1340706359-9455-1-git-send-email-chenhui.zhao@freescale.com> <4FEDD07D.3090103@freescale.com> <4FEDD1F0.1060000@freescale.com> In-Reply-To: <4FEDD1F0.1060000@freescale.com> Content-Type: text/plain; charset="UTF-8" Cc: Wood Scott-B07421 , Li Yang-R58472 , Zhao Chenhui-B35336 , "linux-kernel@vger.kernel.org" , "linuxppc-dev@lists.ozlabs.org" List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , 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