On 21/07/10 02:13, MyungJoo Ham wrote: > On Wed, Jul 21, 2010 at 9:36 AM, Ben Dooks <ben@xxxxxxxxxxxx> wrote: >> On 07/19/10 06:31, MyungJoo Ham wrote: >>> >>> Early S5PC110 (EVT0) chip had some issues required workaround from a >>> kernel. We can add such workaround codes with this Kconfig entry. >>> >>> Signed-off-by: MyungJoo Ham<myungjoo.ham@xxxxxxxxxxx> >>> Signed-off-by: Kyungmin Park<kyungmin.park@xxxxxxxxxxx> >>> --- >>> arch/arm/mach-s5pv210/Kconfig | 7 +++++++ >>> 1 files changed, 7 insertions(+), 0 deletions(-) >>> >>> diff --git a/arch/arm/mach-s5pv210/Kconfig b/arch/arm/mach-s5pv210/Kconfig >>> index 631019a..18802e7 100644 >>> --- a/arch/arm/mach-s5pv210/Kconfig >>> +++ b/arch/arm/mach-s5pv210/Kconfig >>> @@ -101,4 +101,11 @@ config MACH_SMDKC110 >>> Machine support for Samsung SMDKC110 >>> S5PC110(MCP) is one of package option of S5PV210 >>> >>> +config S5PC110_EVT0_WORKAROUND >>> + bool "S5PC110 Early Chip Workaround (EVT0)" >>> + help >>> + Early S5PC110 (so called EVT0) has errata items that should be >>> + addressed; otherwise the kernel may panic or be locked up. >>> Enable >>> + this option to execute workaround instructions. >>> + >>> endif >> >> What happens for non EVT0, is the a performance issue or is it exclusive? >> > > This S5PC110_EVT0_WORKAROUND addresses issues (erratic behaviors, not > performance issues) of "EVT-0" revisions, which is exclusive for these > EVT-0 only. They do not apply to the later (EVT-1 and so on) chips. Ok, so does the fix work for just EVT0? Does it exclude supporting other EVT sillicon as well? -- Ben -- To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
 |