On Mon, Aug 19, 2013 at 11:52:01AM +0100, Mark Brown wrote: > On Mon, Aug 19, 2013 at 11:01:43AM +0100, Mark Rutland wrote: > > On Mon, Aug 19, 2013 at 10:50:43AM +0100, Nicolin Chen wrote: > > > > The phrase "user-visible" is being used in many current docs, I don't > > > dare to change it unless a sage gives me a suggestion. > > > I can see that there is entrenched usage, but this really seems to be > > embedding Linux-specific implementation details into the dt. I don't see > > why the driver cannot select a sensible name, but perhaps I'm missing > > something. > > > Mark, is there any reason we need to handle the user-visible name of the > > device this way? > > This is intended to allow userspace to distinguish between systems that > are electrically identical but physically distinct, for example when > multiple systems are derived from the same reference design. I see. Surely if there's some meaning imparted to userspace by the model name, there's a contract there that we should document (the set of valid model names and what they correspond to)? I'm not sure I understand why userspace needs to know what the system is if we've adequately described how it's wired and what its capabilities are. However, I'm not at all familiar with the way we handle audio, so please forgive my naivety there :) Thanks, Mark. -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
