[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4FEDD07D.3090103@freescale.com>
Date: Fri, 29 Jun 2012 10:57:49 -0500
From: Scott Wood <scottwood@...escale.com>
To: Tabi Timur-B04825 <B04825@...escale.com>
CC: Zhao Chenhui-B35336 <B35336@...escale.com>,
"linuxppc-dev@...ts.ozlabs.org" <linuxppc-dev@...ts.ozlabs.org>,
Wood Scott-B07421 <B07421@...escale.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"galak@...nel.crashing.org" <galak@...nel.crashing.org>,
Li Yang-R58472 <r58472@...escale.com>
Subject: Re: [PATCH v6 1/5] powerpc/85xx: implement hardware timebase sync
On 06/29/2012 10:39 AM, Tabi Timur-B04825 wrote:
> On Tue, Jun 26, 2012 at 5:25 AM, Zhao Chenhui
> <chenhui.zhao@...escale.com> wrote:
>> +static void mpc85xx_give_timebase(void)
>> +{
>> + unsigned long flags;
>> +
>> + local_irq_save(flags);
>> +
>> + while (!tb_req)
>> + barrier();
>
> I think tb_req and tb_valid need to be 'volatile'.
No, barrier() and mb() take care of that.
>> +static const struct of_device_id mpc85xx_smp_guts_ids[] = {
>> + { .compatible = "fsl,mpc8572-guts", },
>> + { .compatible = "fsl,p1020-guts", },
>> + { .compatible = "fsl,p1021-guts", },
>> + { .compatible = "fsl,p1022-guts", },
>> + { .compatible = "fsl,p1023-guts", },
>> + { .compatible = "fsl,p2020-guts", },
>> + {},
>> +};
>
> 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?
-Scott
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists