Date: Thu, 19 Jun 2003 09:46:19 -0700 (PDT)
From: Patrick Mochel <mochel@osdl.org>
To: "Kevin P. Fleming" <kpfleming@cox.net>
cc: linux-kernel@vger.kernel.org
Subject: Re: Flaw in the driver-model implementation of attributes
In-Reply-To: <3EF101E4.3030900@cox.net>
Message-ID: <Pine.LNX.4.44.0306190943110.955-100000@cherise>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1205
Lines: 32


> > What is a sysfs "class", as in /sys/class/...?
> 
> It is an abstraction. It is a group of objects that implement common 
> functionality, and have common attributes and behaviors.

Not quite. A class represents a class of devices, or the function that a 
device performs, e.g. disk or sound. 

> > What do sysfs classes have in common? How is
> > a /sys/class/ different from a /sys/devices,
> > /sys/bus, etc?
> 
> /sys/bus, /sys/block are just special-case classes that get their own 
> top-level directory. They could just easily have been put under 
> /sys/class/block, /sys/class/bus.

No. If you want to go that far, 'devices' could go under there as well, 
and we'd eventually just have one top-level directory: /sys/class :) 

The top-level directories in sysfs represent classes of objects, not 
necessarily tied to any driver model concepts. The reason it's so 
driver-model heavy now is because that's how the whole thing originated. 


	-pat

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/