On 2/28/2011 3:06 PM, Russell King - ARM Linux wrote: > On Mon, Feb 28, 2011 at 02:38:32PM +0100, Cousson, Benoit wrote: >> On 2/28/2011 1:13 PM, Russell King - ARM Linux wrote: >>> On Mon, Feb 28, 2011 at 02:10:26PM +0200, Tomi Valkeinen wrote: >>>> On Mon, 2011-02-28 at 05:36 -0600, Cousson, Benoit wrote: >>>>> Cannot you use a device hierarchy then to do that? >>>>> omap_dss/core >>>>> omap_dss/dsi >>>>> omap_dss/venc >>>>> >>>>> This is moreover the way the HW is done. >>>> >>>> Hmm, how would that work? The devices are platform devices, and they >>>> have a unique global name, which is used to match the driver for the >>>> device. >>> >>> And not forgetting that '/' is not permitted in device or driver names. >> >> I was not really considering naming the device with a '/'. The idea is >> that the devices will not longer be flat platform devices but something >> like dss devices that will have have a omap_dss parent. >> >> I do not know if that makes sense to store some kind of hierarchy in the >> device model, but encoding the hierarchy in the name like it is proposed >> looks like a hack to me. > > Try: > > tree -d /sys/devices/pci0000\:00 > > on your PC, taking special note of how pci-to-pci bridges are handled. Here it is, but I'm not sure to understand how it is really done :-( /sys/devices/pci0000:00 âââ 0000:00:00.0 â âââ firmware_node -> ../../LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/PNP0C02:00 â âââ power â âââ subsystem -> ../../../bus/pci âââ 0000:00:02.0 â âââ 0000:00:02.0:pcie01 â â âââ power â â âââ subsystem -> ../../../../bus/pci_express â âââ 0000:00:02.0:pcie02 â â âââ driver -> ../../../../bus/pci_express/drivers/aer â â âââ power â â âââ subsystem -> ../../../../bus/pci_express â âââ 0000:06:00.0 â â âââ 0000:06:00.0:pcie12 â â â âââ power â â â âââ subsystem -> ../../../../../bus/pci_express â â âââ 0000:07:00.0 â â â âââ 0000:07:00.0:pcie22 â â â â âââ power â â â â âââ subsystem -> ../../../../../../bus/pci_express â â â âââ 0000:08:00.0 â â â â âââ 0000:09:00.0 â â â â â âââ driver -> ../../../../../../../bus/pci/drivers/bnx2 â â â â â âââ net â â â â â â âââ eth1 â â â â â â âââ device -> ../../../0000:09:00.0 â â â â â â âââ power â â â â â â âââ statistics â â â â â â âââ subsystem -> ../../../../../../../../../class/net â â â â â âââ power â â â â â âââ subsystem -> ../../../../../../../bus/pci â â â â âââ pci_bus â â â â â âââ 0000:09 â â â â â âââ device -> ../../../0000:08:00.0 â â â â â âââ power â â â â â âââ subsystem -> ../../../../../../../../class/pci_bus â â â â âââ power â â â â âââ subsystem -> ../../../../../../bus/pci â â â âââ driver -> ../../../../../bus/pci/drivers/pcieport â â â âââ pci_bus â â â â âââ 0000:08 â â â â âââ device -> ../../../0000:07:00.0 â â â â âââ power â â â â âââ subsystem -> ../../../../../../../class/pci_bus â â â âââ power â â â âââ subsystem -> ../../../../../bus/pci ... -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
