On Wed, Jan 12, 2011 at 11:04:10AM +0100, Naveen Kumar GADDIPATI wrote: > >> >On Wed, Jan 12, 2011 at 12:05:26PM +0530, Naveen Kumar G wrote: > >So who/what cares about I2C device name? I do not see how this help > >anything, but it does make device's name differ from its sysfs name. > >I believe that driver should only alter names of objects they create and > >leave other objects alone. > In our regulator driver platform data, we used to differentiate with device name, > which is more readable than the client device name. That is why we are sending it through platform data. > If you are not preferable to use this, we could change it to client device name. This is not what the regulator API is expecting you to do. The regulator API is expecting you to use whatever the device name the bus/device model ends up giving you by default is. If you want to assign other device names for readability or similar reasons that's another issue which should be taken up with the device core guys. -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
