linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Len Brown <lenb@kernel.org>
To: Alan Hourihane <alanh@fairlite.demon.co.uk>
Cc: linux-acpi@vger.kernel.org
Subject: Re: obtaining acpi details outside of drivers/acpi
Date: Thu, 6 Sep 2007 07:43:41 -0400	[thread overview]
Message-ID: <200709060743.42060.lenb@kernel.org> (raw)
In-Reply-To: <1189073769.7969.32.camel@localhost>

Hi Alan,

Yes, pathnames are arbitrary, don't use them.

Look in drivers/acpi/video.c for acpi_video_bus_check()
As the video device has no HID, this routine is basically
used to check all the drivers in the tree if they have _DOD
and the other stuff a video device should have.

BTW. I'm curious what you are trying to do.
There is actually quite a bit of movement in this code right now.

cheers,
-Len

On Thursday 06 September 2007 06:16, Alan Hourihane wrote:
> I'm looking at the currently exported function calls to other kernel
> modules to obtain ACPI data.
> 
> For example, if I want to access _DOD for graphics, the pathname would
> be something like...
> 
> \\_SB_.PCI0.GFX0._DOD
> 
> And I'm currently doing this...
> 
> 	status = acpi_evaluate_object(NULL, PATHNAME, NULL, &buffer);
> 
> where PATHNAME is the path above.
> 
> But there's no guarantees that it's called PCI0, or even GFX0.
> 
> What's the best way to search the namespace and get this data ??
> 
> Alan.
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

  reply	other threads:[~2007-09-06 11:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-06 10:16 obtaining acpi details outside of drivers/acpi Alan Hourihane
2007-09-06 11:43 ` Len Brown [this message]
2007-09-06 11:47   ` Alan Hourihane
2007-09-06 13:22     ` Len Brown
2007-09-06 13:27       ` Alexey Starikovskiy
2007-09-06 13:53       ` Alan Hourihane
2007-09-06 13:57         ` Alan Hourihane
2007-09-06 14:17         ` Alexey Starikovskiy
2007-09-06 14:33           ` Alan Hourihane

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=200709060743.42060.lenb@kernel.org \
    --to=lenb@kernel.org \
    --cc=alanh@fairlite.demon.co.uk \
    --cc=linux-acpi@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).