On 10/02/2013 11:33 AM, Mauro Carvalho Chehab wrote: ... > Well, from userspace PoV, it should have just one devnode for each > TX/RX. I'm fine with that. > So, if the device has N TX and/or RX simultaneous connections, it should > be exposing N device nodes, and the DT should for it should have N entries, > one for each. DT is based on the actual HW construction, not how a particular OS wants to expose that HW through its APIs. If there is a single HW block, there should be a single DT node, even if that HW block supports multiple channels. In some circumstances, it might make sense for the single top-level node that represents the HW-block to have child nodes that represent the channels, depending on what exactly the HW is doing and whether this level of detail is useful in DT. I would qualify this as rare though. -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
