public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: ben@simtec•co.uk (Ben Dooks)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH v3 1/7] ARM: S5PV210: Add a Kconfig entry	"S5PC110_EVT0_WORKAROUND"
Date: Wed, 21 Jul 2010 01:36:55 +0100	[thread overview]
Message-ID: <4C464127.5040405@simtec.co.uk> (raw)
In-Reply-To: <1279517483-22751-2-git-send-email-myungjoo.ham@samsung.com>

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@samsung•com>
> Signed-off-by: Kyungmin Park<kyungmin.park@samsung•com>
> ---
>   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?

-- 
Ben Dooks, Design & Software Engineer, Simtec Electronics

http://www.simtec.co.uk/

  parent reply	other threads:[~2010-07-21  0:36 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-19  5:31 [PATCH v3 0/7] ARM: S5PV210: CPUFREQ Initial Support MyungJoo Ham
2010-07-19  5:31 ` [PATCH v3 1/7] ARM: S5PV210: Add a Kconfig entry "S5PC110_EVT0_WORKAROUND" MyungJoo Ham
2010-07-19  5:31   ` [PATCH v3 2/7] ARM: Samsung SoC: added hclk/pclk info to s3c_freq for s5pv210 cpu-freq MyungJoo Ham
2010-07-19  5:31     ` [PATCH v3 3/7] ARM: S5P: Added default pll values for APLL 800/1000MHz MyungJoo Ham
2010-07-19  5:31       ` [PATCH v3 4/7] ARM: S5P: Virtual Addresses for DMCx registers MyungJoo Ham
2010-07-19  5:31         ` [PATCH v3 5/7] ARM: S5PV210: macros for clock registers at regs-clock.h MyungJoo Ham
2010-07-19  5:31           ` [PATCH v3 6/7] ARM: S5PV210: Access for DMCx registers MyungJoo Ham
2010-07-19  5:31             ` [PATCH v3 7/7] ARM: S5PV210: Initial CPUFREQ Support MyungJoo Ham
2010-07-19  8:47               ` Mark Brown
2010-07-20  0:37               ` Kukjin Kim
2010-07-20  7:00                 ` MyungJoo Ham
2010-07-21  0:38           ` [PATCH v3 5/7] ARM: S5PV210: macros for clock registers at regs-clock.h Ben Dooks
2010-07-21  2:03             ` MyungJoo Ham
2010-07-21  0:37       ` [PATCH v3 3/7] ARM: S5P: Added default pll values for APLL 800/1000MHz Ben Dooks
2010-07-21  1:28         ` MyungJoo Ham
2010-07-19  7:59   ` [PATCH v3 1/7] ARM: S5PV210: Add a Kconfig entry "S5PC110_EVT0_WORKAROUND" Kukjin Kim
2010-07-19  8:09     ` Kyungmin Park
2010-07-21  0:36   ` Ben Dooks [this message]
2010-07-21  1:13     ` MyungJoo Ham
2010-07-21 11:47       ` Ben Dooks
2010-07-21 13:51         ` Kyungmin Park
2010-07-22  0:57         ` MyungJoo Ham

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=4C464127.5040405@simtec.co.uk \
    --to=ben@simtec$(echo .)co.uk \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox