All of lore.kernel.org
 help / color / mirror / Atom feed
From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: acpi: add a Kconfig option to prefer ACPI boot over DT
Date: Tue, 12 Apr 2016 14:35:55 +0100	[thread overview]
Message-ID: <20160412133555.GD8066@e104818-lin.cambridge.arm.com> (raw)
In-Reply-To: <CAKv+Gu-XYoyRkfMtdSARW0mf5dbztWbjM7hps4yBS6O1hKfRqg@mail.gmail.com>

On Tue, Apr 12, 2016 at 03:19:58PM +0200, Ard Biesheuvel wrote:
> On 12 April 2016 at 15:07, Catalin Marinas <catalin.marinas@arm.com> wrote:
> > On Mon, Apr 11, 2016 at 01:19:28PM +0200, Ard Biesheuvel wrote:
> >> If both ACPI and DT platform descriptions are available, and the
> >> kernel was configured at build time to support both flavours, the
> >> default policy in absence of a acpi=[off|force] kernel command line
> >> parameter is to prefer DT over ACPI.
> >>
> >> This adds an option to invert that default policy, and prefer ACPI
> >> over DT instead. Note that this policy is still superseded by the
> >> value of the acpi= command line parameter.
> >
> > Why do we need another method to specify an ACPI boot? I thought those
> > vendors going for ACPI wouldn't be bothered with DT anyway.
> >
> > I'm not keen on having kernel builds with different behavior in respect
> > of whether ACPI or DT is preferred.
> 
> How about adding support for acpi=on then? Currently, we only have
> acpi=off or acpi=force, and there is no way (i.e., for a distro
> installer) to boot via ACPI if it can but fall back to DT otherwise.
> Some enterprise features (like RAS) depend on ACPI boot so it may
> simply preferred but not mandated in some cases.

Since this is a distro preference, I would rather have an acpi=on
option.

-- 
Catalin

  reply	other threads:[~2016-04-12 13:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-11 11:19 [PATCH] arm64: acpi: add a Kconfig option to prefer ACPI boot over DT Ard Biesheuvel
2016-04-11 12:01 ` Graeme Gregory
2016-04-11 23:53   ` Roy Franz
2016-04-12 13:07 ` Catalin Marinas
2016-04-12 13:19   ` Ard Biesheuvel
2016-04-12 13:35     ` Catalin Marinas [this message]
2016-04-12 19:41       ` Roy Franz (HPE)
2016-04-13 13:59         ` Catalin Marinas
2016-04-13 17:21           ` Roy Franz
2016-04-14 16:46             ` Catalin Marinas

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=20160412133555.GD8066@e104818-lin.cambridge.arm.com \
    --to=catalin.marinas@arm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.