From: Aaron Lu <aaron.lu@intel.com>
To: Alex Hung <alex.hung@canonical.com>
Cc: rui.zhang@intel.com, rjw@rjwysocki.net, lenb@kernel.org,
linux-acpi@vger.kernel.org
Subject: Re: [PATCH] ACPI:video: skip evaluating _DOD when it does not exist
Date: Fri, 3 Jun 2016 14:04:03 +0800 [thread overview]
Message-ID: <20160603060401.GA8618@aaronlu.sh.intel.com> (raw)
In-Reply-To: <1464335226-11212-1-git-send-email-alex.hung@canonical.com>
On Fri, May 27, 2016 at 03:47:06PM +0800, Alex Hung wrote:
> Some system supports hybrid graphics and its discrete VGA
> does not have any connectors and therefore has no _DOD method.
>
> Signed-off-by: Alex Hung <alex.hung@canonical.com>
> ---
> drivers/acpi/acpi_video.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/acpi/acpi_video.c b/drivers/acpi/acpi_video.c
> index 5fdac39..549cdbe 100644
> --- a/drivers/acpi/acpi_video.c
> +++ b/drivers/acpi/acpi_video.c
> @@ -1211,6 +1211,9 @@ static int acpi_video_device_enumerate(struct acpi_video_bus *video)
> union acpi_object *dod = NULL;
> union acpi_object *obj;
>
> + if (!video->cap._DOD)
> + return AE_NOT_EXIST;
> +
> status = acpi_evaluate_object(video->device->handle, "_DOD", NULL, &buffer);
> if (!ACPI_SUCCESS(status)) {
> ACPI_EXCEPTION((AE_INFO, status, "Evaluating _DOD"));
Is the patch supposed to avoid the above error message?
I'm OK with the patch though, it's just not clear to me the point since
the acpi_evaluate_object should probably also return AE_NOT_EXIST.
Thanks,
Aaron
next prev parent reply other threads:[~2016-06-03 6:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-27 7:47 [PATCH] ACPI:video: skip evaluating _DOD when it does not exist Alex Hung
2016-06-03 6:04 ` Aaron Lu [this message]
2016-06-06 1:36 ` Alex Hung
2016-06-06 1:52 ` Aaron Lu
2016-06-23 0:32 ` 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=20160603060401.GA8618@aaronlu.sh.intel.com \
--to=aaron.lu@intel.com \
--cc=alex.hung@canonical.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=rui.zhang@intel.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