On Wed, Dec 21, 2011 at 01:37:03AM +0000, Mark Brown wrote:
On Wed, Dec 21, 2011 at 09:25:21AM +0800, Shawn Guo wrote:
quoted
The problem is even if we have the name defined that way, it has to be
matched to the name used in mc13892 driver somehow, if we want to use
name as the key to find the regulator defined in mc13892 driver as
array mc13892_regulators[].
This doesn't seem like a problem - the most obvious thing would just be
to adjust the strings in the code to correspond to what the device tree
binding says.
Okay, that's it. Something obvious to you is not obvious to me :)
As I'm migrating an existing driver to be DT aware, I'm trying to avoid
changing any non-dt code. Your suggestion would be obvious to me if I'm
writing a new driver that only supports DT.
Anyway, I got your point, and will follow that since you seems fine
with changing non-dt code to adopt dt support.
--
Regards,
Shawn