From: Timo Hoenig <thoenig@nouse.net>
To: Yu Luming <luming.yu@gmail.com>
Cc: Andrew Morton <akpm@osdl.org>, Pavel Machek <pavel@ucw.cz>,
len.brown@intel.com, Matt Domsch <Matt_Domsch@dell.com>,
Alessandro Guido <alessandro.guido@gmail.com>,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
jengelh@linux01.gwdg.de, gelma@gelma.net, ismail@pardus.org.tr,
Richard Hughes <hughsient@gmail.com>
Subject: Re: [patch 4/6] Add output class document
Date: Thu, 02 Nov 2006 15:04:29 +0100 [thread overview]
Message-ID: <1162476269.5888.17.camel@nouse.suse.de> (raw)
In-Reply-To: <200611042122.00950.luming.yu@gmail.com>
Hi,
On Sat, 2006-11-04 at 21:22 +0800, Yu Luming wrote:
> diff --git a/Documentation/video-output.txt b/Documentation/video-output.txt
> new file mode 100644
> index 0000000..71b1dba
> --- /dev/null
> +++ b/Documentation/video-output.txt
> @@ -0,0 +1,34 @@
> +
> + Video Output Switcher Control
> + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> + 2006 luming.yu@gmail.com
> +
> +The output sysfs class driver is to provide video output abstract layer that
> +can be used to hook platform specific methods to enable/disable video output
> +device through common sysfs interface. For example, on my IBM Thinkpad T42
> +aptop, acpi video driver registered its output devices and read/write method
> +for state with output sysfs class. The user interface under sysfs is :
Rephrased, s/Thinkpad/ThinkPad, s/aptop/laptop, s/acpi/ACPI, kill
whitespace in front of colon:
The output sysfs class driver provides an abstract video output layer that
can be used to hook platform specific methods to enable/disable video output
devices through a common sysfs interface. For example, on my IBM ThinkPad T42
laptop, the ACPI video driver registers its output devices and read/write methods
for 'state' with output sysfs class. The user interface under sysfs is:
The last but one sentence still sounds bogus to me, maybe someone else
has an idea.
> +linux:/sys/class/video_output # tree .
> +.
> +|-- CRT0
> +| |-- device -> ../../../devices/pci0000:00/0000:00:01.0
> +| |-- state
> +| |-- subsystem -> ../../../class/video_output
> +| `-- uevent
> +|-- DVI0
> +| |-- device -> ../../../devices/pci0000:00/0000:00:01.0
> +| |-- state
> +| |-- subsystem -> ../../../class/video_output
> +| `-- uevent
> +|-- LCD0
> +| |-- device -> ../../../devices/pci0000:00/0000:00:01.0
> +| |-- state
> +| |-- subsystem -> ../../../class/video_output
> +| `-- uevent
> +`-- TV0
> + |-- device -> ../../../devices/pci0000:00/0000:00:01.0
> + |-- state
> + |-- subsystem -> ../../../class/video_output
> + `-- uevent
> +
Thanks,
Timo
next prev parent reply other threads:[~2006-11-02 14:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-02 13:22 [patch 4/6] Add output class document Yu Luming
2006-11-02 14:04 ` Timo Hoenig [this message]
2006-11-04 8:22 ` Greg KH
2006-11-06 22:42 ` Len Brown
-- strict thread matches above, loose matches on Subject: below --
2006-11-02 13:23 Yu Luming
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=1162476269.5888.17.camel@nouse.suse.de \
--to=thoenig@nouse.net \
--cc=Matt_Domsch@dell.com \
--cc=akpm@osdl.org \
--cc=alessandro.guido@gmail.com \
--cc=gelma@gelma.net \
--cc=hughsient@gmail.com \
--cc=ismail@pardus.org.tr \
--cc=jengelh@linux01.gwdg.de \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luming.yu@gmail.com \
--cc=pavel@ucw.cz \
/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