From: Milton Miller <miltonm@bga.com>
To: Olof Johansson <olof@lixom.net>
Cc: ppcdev <linuxppc-dev@ozlabs.org>
Subject: Re: [PATCH] powerpc: Add workaround for MPICs with broken register reads
Date: Thu, 6 Sep 2007 09:55:21 -0500 [thread overview]
Message-ID: <d62ce2299f9d423f95cd8ee50b3b7cff@bga.com> (raw)
In-Reply-To: <20070905024417.GE27139@lixom.net>
On Wed Sep 5 12:44:17 EST 2007, Olof Johansson wrote:
> diff --git a/arch/powerpc/platforms/Kconfig
> b/arch/powerpc/platforms/Kconfig
> index 041df77..b9f1efa 100644
> --- a/arch/powerpc/platforms/Kconfig
> +++ b/arch/powerpc/platforms/Kconfig
> @@ -137,6 +137,10 @@ config MPIC_U3_HT_IRQS
> depends on PPC_MAPLE
> default y
>
> +config MPIC_BROKEN_REGREAD
> + bool
> + depends on PPC_PASEMI
> +
> config IBMVIO
> depends on PPC_PSERIES || PPC_ISERIES
> bool
> diff --git a/arch/powerpc/platforms/pasemi/Kconfig
> b/arch/powerpc/platforms/pasemi/Kconfig
> index 95cd90f..117d90a 100644
> --- a/arch/powerpc/platforms/pasemi/Kconfig
> +++ b/arch/powerpc/platforms/pasemi/Kconfig
> @@ -5,6 +5,7 @@ config PPC_PASEMI
> select MPIC
> select PPC_UDBG_16550
> select PPC_NATIVE
> + select MPIC_BROKEN_REGREAD
> help
> This option enables support for PA Semi's PWRficient line
> of SoC processors, including PA6T-1682M
Since you are using select (and not default y), instead of the depends
on PPC_PASEMI how about adding a short description of what the config
does as help text, in case some future mpic has a similar bug?
milton
next prev parent reply other threads:[~2007-09-06 14:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-05 2:44 [PATCH] powerpc: Add workaround for MPICs with broken register reads Olof Johansson
2007-09-06 14:55 ` Milton Miller [this message]
2007-09-07 9:16 ` Olof Johansson
2007-09-07 9:21 ` [PATCH v2] " Olof Johansson
2007-09-07 14:11 ` Milton Miller
2007-09-07 19:12 ` Olof Johansson
2007-09-07 19:13 ` [PATCH v3] " Olof Johansson
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=d62ce2299f9d423f95cd8ee50b3b7cff@bga.com \
--to=miltonm@bga.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=olof@lixom.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).