All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olof Johansson <olof@lixom.net>
To: Mark Brown <broonie@kernel.org>
Cc: "Rafael J . Wysocki" <rjw@rjwysocki.net>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Len Brown <lenb@kernel.org>, Will Deacon <will.deacon@arm.com>,
	Mark Rutland <mark.rutland@arm.com>,
	Steve Capper <steve.capper@linaro.org>,
	Graeme Gregory <graeme.gregory@linaro.org>,
	"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"arm@kernel.org" <arm@kernel.org>
Subject: Re: [PATCH 2/3] ACPI / ARM64: Remove EXPERT dependency for ACPI on ARM64
Date: Fri, 15 Apr 2016 10:48:50 -0700	[thread overview]
Message-ID: <CAOesGMg5E4bcwQgt4+9JkLwmcZ_sj9sCE8ya50MEDQiizN-YUg@mail.gmail.com> (raw)
In-Reply-To: <1460706823-16566-2-git-send-email-broonie@kernel.org>

On Fri, Apr 15, 2016 at 12:53 AM, Mark Brown <broonie@kernel.org> wrote:
> When ACPI was originally merged for arm64 it had only been tested on
> emulators and not on real physical platforms and no platforms were
> relying on it.  This meant that there were concerns that there might be
> serious issues attempting to use it on practical systems so it had a
> dependency on EXPERT added to warn people that it was in an early stage
> of development with very little practical testing.  Since then things
> have moved on a bit.  We have seen people testing on real hardware and
> now have people starting to produce some platforms (the most prominent
> being the 96boards Cello) which only have ACPI support and which build
> and run to some useful extent with mainline.
>
> This is not to say that ACPI support or support for these systems is
> completely done, there are still areas being worked on such as PCI, but
> at this point it seems that we can be reasonably sure that ACPI will be
> viable for use on ARM64 and that the already merged support works for
> the cases it handles.  For the AMD Seattle based platforms support
> outside of PCI has been fairly complete in mainline a few releases now.
>
> This is also not to say that we don't have vendors working with ACPI who
> are trying do things that we would not consider optimal but it does not
> appear that the EXPERT dependency is having a substantial impact on
> these vendors.
>
> Given all this it seems that at this point the EXPERT dependency mainly
> creates inconvenience for users with systems that are doing the right
> thing and gets in the way of including the ACPI code in the testing that
> people are doing on mainline.  Removing it should help our ongoing
> testing cover those platforms with only ACPI support and help ensure
> that when ACPI code is merged any problems it causes for other users are
> more easily discovered.
>
> Signed-off-by: Mark Brown <broonie@kernel.org>
> Acked-by: Graeme Gregory <graeme.gregory@linaro.org>
> Acked-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
> Reviewed-by: Al Stone <ahs3@redhat.com>
> Acked-by: Hanjun Guo <hanjun.guo@linaro.org>
> Acked-by: Catalin Marinas <catalin.marinas@arm.com>

Acked-by: Olof Johansson <olof@lixom.net>


-Olof

WARNING: multiple messages have this Message-ID (diff)
From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/3] ACPI / ARM64: Remove EXPERT dependency for ACPI on ARM64
Date: Fri, 15 Apr 2016 10:48:50 -0700	[thread overview]
Message-ID: <CAOesGMg5E4bcwQgt4+9JkLwmcZ_sj9sCE8ya50MEDQiizN-YUg@mail.gmail.com> (raw)
In-Reply-To: <1460706823-16566-2-git-send-email-broonie@kernel.org>

On Fri, Apr 15, 2016 at 12:53 AM, Mark Brown <broonie@kernel.org> wrote:
> When ACPI was originally merged for arm64 it had only been tested on
> emulators and not on real physical platforms and no platforms were
> relying on it.  This meant that there were concerns that there might be
> serious issues attempting to use it on practical systems so it had a
> dependency on EXPERT added to warn people that it was in an early stage
> of development with very little practical testing.  Since then things
> have moved on a bit.  We have seen people testing on real hardware and
> now have people starting to produce some platforms (the most prominent
> being the 96boards Cello) which only have ACPI support and which build
> and run to some useful extent with mainline.
>
> This is not to say that ACPI support or support for these systems is
> completely done, there are still areas being worked on such as PCI, but
> at this point it seems that we can be reasonably sure that ACPI will be
> viable for use on ARM64 and that the already merged support works for
> the cases it handles.  For the AMD Seattle based platforms support
> outside of PCI has been fairly complete in mainline a few releases now.
>
> This is also not to say that we don't have vendors working with ACPI who
> are trying do things that we would not consider optimal but it does not
> appear that the EXPERT dependency is having a substantial impact on
> these vendors.
>
> Given all this it seems that at this point the EXPERT dependency mainly
> creates inconvenience for users with systems that are doing the right
> thing and gets in the way of including the ACPI code in the testing that
> people are doing on mainline.  Removing it should help our ongoing
> testing cover those platforms with only ACPI support and help ensure
> that when ACPI code is merged any problems it causes for other users are
> more easily discovered.
>
> Signed-off-by: Mark Brown <broonie@kernel.org>
> Acked-by: Graeme Gregory <graeme.gregory@linaro.org>
> Acked-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
> Reviewed-by: Al Stone <ahs3@redhat.com>
> Acked-by: Hanjun Guo <hanjun.guo@linaro.org>
> Acked-by: Catalin Marinas <catalin.marinas@arm.com>

Acked-by: Olof Johansson <olof@lixom.net>


-Olof

  parent reply	other threads:[~2016-04-15 17:48 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-15  7:53 [PATCH 1/3] ACPI / ARM64: Don't enable ACPI by default on ARM64 Mark Brown
2016-04-15  7:53 ` Mark Brown
2016-04-15  7:53 ` [PATCH 2/3] ACPI / ARM64: Remove EXPERT dependency for ACPI " Mark Brown
2016-04-15  7:53   ` Mark Brown
2016-04-15 16:19   ` Roy Franz (HPE)
2016-04-15 16:19     ` Roy Franz (HPE)
2016-04-15 17:48   ` Olof Johansson [this message]
2016-04-15 17:48     ` Olof Johansson
2016-04-20 16:30   ` Timur Tabi
2016-04-20 16:30     ` Timur Tabi
2016-04-15  7:53 ` [PATCH 3/3] arm64: defconfig: Enable ACPI Mark Brown
2016-04-15  7:53   ` Mark Brown
2016-04-15  8:42   ` Catalin Marinas
2016-04-15  8:42     ` Catalin Marinas
2016-04-15  9:04   ` Hanjun Guo
2016-04-15  9:04     ` Hanjun Guo
2016-04-15 16:17   ` Roy Franz (HPE)
2016-04-15 16:17     ` Roy Franz (HPE)
2016-04-15  8:42 ` [PATCH 1/3] ACPI / ARM64: Don't enable ACPI by default on ARM64 Catalin Marinas
2016-04-15  8:42   ` Catalin Marinas
2016-04-15  9:03 ` Hanjun Guo
2016-04-15  9:03   ` Hanjun Guo
2016-04-15 17:48 ` Olof Johansson
2016-04-15 17:48   ` Olof Johansson
2016-04-16 15:11 ` Sergei Shtylyov
2016-04-16 15:11   ` Sergei Shtylyov
2016-04-21  0:10 ` Rafael J. Wysocki
2016-04-21  0:10   ` Rafael J. Wysocki

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=CAOesGMg5E4bcwQgt4+9JkLwmcZ_sj9sCE8ya50MEDQiizN-YUg@mail.gmail.com \
    --to=olof@lixom.net \
    --cc=arm@kernel.org \
    --cc=broonie@kernel.org \
    --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=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 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.