From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: Dead Kconfig Option OMAP4_ERRATA_I688
Date: Wed, 25 Feb 2015 09:14:51 -0800 [thread overview]
Message-ID: <20150225171451.GQ11056@atomide.com> (raw)
In-Reply-To: <CABv5NL-bnfV0BoH+G=nX+1eo6xeT_LN8dOFtSnwvdpcvjJhUFQ@mail.gmail.com>
Hi,
Adding Santosh to Cc on this one.
* Stefan Hengelein <stefan.hengelein@fau.de> [150225 09:13]:
> During the research for my masters thesis i came across the
> OMAP4_ERRATA_I688 option and realized, it is never possible to enable
> this option.
>
> The a62a6e98 commit added the "&& !ARCH_MULTIPLATFORM" dependency to
> disable this option for multiplatforms. However, because of enclosing
> dependencies, this option isn't available for non-MULTIPLATFORM
> configurations either.
Yes there is no clean way currently to enable this errata for
multiplatform.
> CONFIG_OMAP4_ERRATA_I688 is defined in the menu "TI OMAP/AM/DM/DRA
> Family" which depends on ARCH_MULTI_V6 || ARCH_MULTI_V7. (in
> arch/arm/mach-omap2/Kconfig)
>
> ARCH_MULTI_V6 and ARCH_MULTI_V7 however are defined in the menu
> "Multiple platform selection" which depends on ARCH_MULTIPLATFORM (in
> arch/arm/Kconfig)
>
> Which is a contradiction.
>
> There are no selects on OMAP4_ERRATA_I688, which would ignore
> dependencies, either.
>
> The question is:
> Was disabling this option for non-MULTIPLATFORM configurations also intentional?
>
> i have added a minimal example of the problem.
>From what I remember the plan was to try to come up with a
multiplatform friendly way of doing this errata. Santosh,
any suggestions here? Should we just remove the code as it
seems nobody has complained about it for a few years now?
Regards,
Tony
next prev parent reply other threads:[~2015-02-25 17:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-25 17:10 Dead Kconfig Option OMAP4_ERRATA_I688 Stefan Hengelein
2015-02-25 17:14 ` Tony Lindgren [this message]
2015-02-25 17:24 ` santosh shilimkar
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=20150225171451.GQ11056@atomide.com \
--to=tony@atomide.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).