public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Renninger <trenn@suse.de>
To: Andrey Borzenkov <arvidjaar@mail.ru>
Cc: linux-acpi@vger.kernel.org
Subject: Re: Can video_detect be made __init?
Date: Wed, 12 Nov 2008 17:34:25 -0600	[thread overview]
Message-ID: <200811121734.25449.trenn@suse.de> (raw)
In-Reply-To: <200811081655.08226.arvidjaar@mail.ru>

On Saturday 08 November 2008 07:55:07 am Andrey Borzenkov wrote:
> I would add DMI entries to force vendor backlight for my system, but
> I'd really prefer they are not remain in memory forever. Is there any
> reason for the whole detection to not happen exactly once? After all,
> ACPI cannot change after boot, can it?
>
> Hmm ... actually DSDT can be loaded from initrd, so it can change ... but
> in this case we actually are just interested in DMI matching which says
> whether vendor driver is preferred or not. What would be the the best
> place to call it from?

Sorry, I only half answered the question in my previous mail.
acpi_video_backlight_support(..)
which is called by the backlight supporting drivers is going to check (when 
invoked the first time) whether general ACPI video functions are provided via 
the ACPI tables.
Advantage is that the check is only done if video.ko or vendor_laptop drivers 
are trying to be loaded. That means on a server where video.ko or 
vendor_laptop.ko are not needed, the video ACPI func detection does not take 
place.
The "disadvantage" is that it's done at driver load time and cannot be 
declared __init.

       Thomas

      parent reply	other threads:[~2008-11-12 23:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-08 13:55 Can video_detect be made __init? Andrey Borzenkov
2008-11-09 12:20 ` Thomas Renninger
2008-11-12 23:34 ` Thomas Renninger [this message]

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=200811121734.25449.trenn@suse.de \
    --to=trenn@suse.de \
    --cc=arvidjaar@mail.ru \
    --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