From: yakui_zhao <yakui.zhao@intel.com>
To: lenb@kernel.org
Cc: linux-acpi@vger.kernel.org
Subject: [PATCH 0/2]: the patch set to weaken the dependency between ACPI video driver and i915 driver
Date: Tue, 14 Apr 2009 11:04:35 +0800 [thread overview]
Message-ID: <1239678275.5564.66.camel@localhost.localdomain> (raw)
Hi, All
the following is the patch set that can weaken the dependency between ACPI video and i915
driver.
Patch 1/2: Check whether the acpi video is deferrable only when KMS is enabled
When the KMS is enabled in kernel configuration, OS will check whether the acpi video
driver is deferrable. Otherwise it will continue the current flowchart.
Patch 2/2: weaken the tight dependency between the ACPI video driver and i915 driver
Now there exists the tight dependency between the ACPI video driver and i915 driver.
If the I915 driver is compiled as built-in module and the acpi video is compiled as module,
it will fail in the kernel compilation.
At the same time the acpi video driver must be loaded in order to load
the I915 driver. It is very hack.
This patch is to weaken the dependency between the ACPI video driver and
i915 driver. But it still can do what we expected.
a. the i915/acpi_video_register is defined in the video_detect.When the video is selected,
it will be complied as built-in functions. If the video is not selected, it is defined as
inline function.
b. i915_video_register is called by i915 driver. And i915 video flag is set.
c. acpi_video_register/unregister is called by acpi video driver. The acpi video bus driver
is hooked and the ACPI video flag is set.
d. When the both flag bits are set, the acpi video bus driver will be registered.
Welcome the comments.
Best regards
Yakui
next reply other threads:[~2009-04-14 3:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-14 3:04 yakui_zhao [this message]
2009-04-14 19:35 ` [PATCH 0/2]: the patch set to weaken the dependency between ACPI video driver and i915 driver Matthew Garrett
2009-04-15 1:12 ` yakui_zhao
2009-04-15 4:53 ` Matthew Garrett
2009-04-15 13:21 ` Zhao, Yakui
2009-04-15 16:54 ` Matthew Garrett
2009-04-16 1:15 ` yakui_zhao
2009-04-15 7:35 ` Zhang Rui
2009-04-15 20:56 ` Matthew Garrett
2009-04-23 19:56 ` Len Brown
2009-04-30 20:23 ` Andrew Morton
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=1239678275.5564.66.camel@localhost.localdomain \
--to=yakui.zhao@intel.com \
--cc=lenb@kernel.org \
--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