public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: Will Deacon <will.deacon@arm.com>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Steve Capper <steve.capper@linaro.org>,
	Graeme Gregory <graeme.gregory@linaro.org>,
	Catalin Marinas <catalin.marinas@arm.com>,
	"Rafael J . Wysocki" <rjw@rjwysocki.net>,
	ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
	Hanjun Guo <guohanjun@huawei.com>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	Len Brown <lenb@kernel.org>
Subject: Re: [PATCH] ACPI / ARM64: Remove EXPERT dependency for ACPI on ARM64
Date: Thu, 31 Mar 2016 09:39:19 -0700	[thread overview]
Message-ID: <20160331163919.GC2350@sirena.org.uk> (raw)
In-Reply-To: <CAKv+Gu_TfX8aOXig63gWH535he-dPiMr14ig7bUL+LJC_n3=9Q@mail.gmail.com>

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

On Thu, Mar 31, 2016 at 04:48:44PM +0200, Ard Biesheuvel wrote:
> On 31 March 2016 at 15:38, Will Deacon <will.deacon@arm.com> wrote:

> > I'd really like to get away from the concept of ACPI-only systems. Would
> > we reject a .dtb contribution for such a machine?

> Absolutely not, and I expect such contributions will appear sooner
> rather than later.

> But the point of ACPI is the abstraction, and the ridiculous churn in
> DTB's carried in mainline clearly shows the need for that*. So there
> will be ACPI-only systems because the drivers are coded against the
> abstracted interface, and DT is simply not a drop-in replacement in
> that case.

It's also worth remembering that just because we have a DT in tree that
doesn't mean that people running actual systems are going to use it.
For some systems there will be a user community that wants to do that
but that won't be universal, there are going to be people who just use
the default firmware.

> > I understand that, but I still think that removing the dependency on
> > EXPERT is indicative of saying "this stuff is good to be used by the
> > masses", irrespective of a cmdline option. Maybe that's true, but it's
> > not immediately obvious to me, with all the patches in flight.

> Well, we are not cc'ing to stable, are we? Or do you think the current
> stuff is so broken that we should even protect users of the upstream
> HEAD branch against it?

Like I said in the other mail I'm also just not sure that this is
something that people deciding what firmware to ship on their systems
are paying much attention to.  People are coming to their own assessment
based on their own testing and other factors.  Where I see this having
an impact is more on having the rest of the upstream community keeping
an eye on what the ACPI people are doing.

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

  reply	other threads:[~2016-03-31 16:39 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 [this message]
2016-03-31 15:28       ` Mark Brown
2016-04-12 17:23 ` Catalin Marinas
2016-04-13  5:25   ` Mark Brown
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=20160331163919.GC2350@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=ard.biesheuvel@linaro.org \
    --cc=catalin.marinas@arm.com \
    --cc=graeme.gregory@linaro.org \
    --cc=guohanjun@huawei.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=mark.rutland@arm.com \
    --cc=rafael@kernel.org \
    --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