public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: Will Deacon <will.deacon@arm.com>,
	"Rafael J . Wysocki" <rjw@rjwysocki.net>,
	Len Brown <lenb@kernel.org>, Mark Rutland <mark.rutland@arm.com>,
	Steve Capper <steve.capper@linaro.org>,
	Graeme Gregory <graeme.gregory@linaro.org>,
	linux-acpi@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	Arnd Bergmann <arnd@arndb.de>, Olof Johansson <olof@lixom.net>
Subject: Re: [PATCH] ACPI / ARM64: Remove EXPERT dependency for ACPI on ARM64
Date: Wed, 13 Apr 2016 06:25:53 +0100	[thread overview]
Message-ID: <20160413052553.GF14664@sirena.org.uk> (raw)
In-Reply-To: <20160412172315.GH8066@e104818-lin.cambridge.arm.com>

[-- Attachment #1: Type: text/plain, Size: 1488 bytes --]

On Tue, Apr 12, 2016 at 06:23:15PM +0100, Catalin Marinas wrote:

> I'm fine with dropping the EXPERT dependency (of course, not a cc
> stable). While arm64 ACPI is not "done" yet (nor is DT; there are
> important ongoing developments like PCIe, IORT), I think the core arm64
> ACPI support passed the EXPERT stage. I also don't think a default y
> would imply any maintainer endorsement; vendors targeting ACPI are
> already doing this for various reasons (distro requirement, certain ACPI

So you're OK with the current patch?

> features like RAS). But, hopefully, it will encourage more vendors to
> start upstreaming their ACPI-related patches.

Yes, and also help include ACPI systems in the work we're doing testing
things upstream.

> However, building ACPI by default on arm64 doesn't mean that we can
> ignore potential misuses like PRP0001+_DSD blindly following DT
> (mis)concepts, breaking compatibility with older/newer firmware (this
> goes in both directions) or using ACPI for SoCs where it is clearly not
> suitable (e.g. non-SBSA). Such patches should be NAK'ed accordingly.

Yes, I'm very concerned about some of the activity I'm seeing there
myself - it does seem likely that we're going to have to extend ACPI for
arm64 SoCs simply because things like SBSA are so bare bones but we need
to pay attention to what's going on there to promote best practices and
try to get people producing firmwares that make well thought through
decisions regarding their ACPI usage.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

  reply	other threads:[~2016-04-13  5:26 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-30 17:58 [PATCH] ACPI / ARM64: Remove EXPERT dependency for ACPI on ARM64 Mark Brown
2016-03-30 18:02 ` G Gregory
2016-03-30 19:25 ` Ard Biesheuvel
2016-03-30 19:35 ` Al Stone
2016-03-31  3:44 ` Hanjun Guo
2016-03-31 12:04   ` Rafael J. Wysocki
2016-03-31 12:36     ` Will Deacon
2016-03-31 12:47       ` Rafael J. Wysocki
2016-03-31 13:20       ` Ard Biesheuvel
2016-03-31 13:38         ` Will Deacon
2016-03-31 14:48           ` Ard Biesheuvel
2016-03-31 16:39             ` Mark Brown
2016-03-31 15:28       ` Mark Brown
2016-04-12 17:23 ` Catalin Marinas
2016-04-13  5:25   ` Mark Brown [this message]
2016-04-13  8:51     ` Catalin Marinas
2016-04-13 12:49       ` Mark Brown
2016-04-14 18:02   ` Olof Johansson
2016-04-14 18:25     ` Mark Brown
2016-04-14 18:49       ` Olof Johansson
2016-04-14 18:56         ` Mark Brown

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=20160413052553.GF14664@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=arnd@arndb.de \
    --cc=catalin.marinas@arm.com \
    --cc=graeme.gregory@linaro.org \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=mark.rutland@arm.com \
    --cc=olof@lixom.net \
    --cc=rjw@rjwysocki.net \
    --cc=steve.capper@linaro.org \
    --cc=will.deacon@arm.com \
    /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