From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Menon, Nishanth" Subject: Re: [PATCHv2 09/19] ARM: OMAP4: PM: add errata support Date: Wed, 30 May 2012 09:45:42 -0500 Message-ID: References: <1336990730-26892-1-git-send-email-t-kristo@ti.com> <1336990730-26892-10-git-send-email-t-kristo@ti.com> <1338366759.8834.124.camel@sokoban> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Return-path: Received: from na3sys009aog120.obsmtp.com ([74.125.149.140]:45905 "EHLO na3sys009aog120.obsmtp.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751212Ab2E3OqG (ORCPT ); Wed, 30 May 2012 10:46:06 -0400 Received: by werm13 with SMTP id m13so3509585wer.15 for ; Wed, 30 May 2012 07:46:02 -0700 (PDT) In-Reply-To: <1338366759.8834.124.camel@sokoban> Sender: linux-omap-owner@vger.kernel.org List-Id: linux-omap@vger.kernel.org To: t-kristo@ti.com Cc: linux-omap@vger.kernel.org, khilman@ti.com, paul@pwsan.com, linux-arm-kernel@lists.infradead.org On Wed, May 30, 2012 at 3:32 AM, Tero Kristo wrote: > On Tue, 2012-05-29 at 15:10 -0500, Menon, Nishanth wrote: >> On Mon, May 14, 2012 at 5:18 AM, Tero Kristo wrote: >> > Added similar PM errata flag support as omap3 has. A few errata flags >> > will be added in subsequent patches. >> >> Considering that we might have erratas for future SoCs as well, >> should'nt we just >> set up a common errata flag for all SoCs and since we have i123 numbers, would >> it help being able to reuse errata flags cross SoC generations (if we need to)? > > Not sure... how quickly do we run out of bits that way? :) Also, at > least pm34xx / pm44xx erratas don't have anything in common. We can > probably re-use pm44xx erratas for omap5 though. > > One annoyance is that, the OMAP4 erratas are going to have a number of > ROM code erratas on them, which don't really have any public i123 > numbers available. >.< Sounds good to me. Regards, Nishanth Menon