From: Greg KH <greg@kroah.com>
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: Sat, 4 Nov 2006 00:22:28 -0800 [thread overview]
Message-ID: <20061104082228.GA30489@kroah.com> (raw)
In-Reply-To: <200611042122.00950.luming.yu@gmail.com>
On Sat, Nov 04, 2006 at 09:22:00PM +0800, Yu Luming wrote:
> Add output class document
>
> signed-off-by ? Luming.yu@gmail.com
> ---
> [patch 4/6] Add output class document
> video-output.txt | 34 ++++++++++++++++++++++++++++++++++
> 1 file changed, 34 insertions(+)
>
> 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 :
> +
> +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
Use a struct device instead of a struct class_device please. That will
change your tree a bit here (you will have symlinks at the top level.
Have you been working with the X developers that have been doing a lot
of work in describing and interacting with these different video
devices? I think you might want to work with them so that you don't
create an interface that will not be used by them.
thanks,
greg k-h
next prev parent reply other threads:[~2006-11-04 9:19 UTC|newest]
Thread overview: 6+ 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-04 13:22 ` Yu Luming
2006-11-02 14:04 ` Timo Hoenig
2006-11-04 8:22 ` Greg KH [this message]
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=20061104082228.GA30489@kroah.com \
--to=greg@kroah.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.