Kumar Gala wrote:

I guess my gripe is about proposing a solution and not willing to  
extend it in light of people providing issues with it. 

I'm perfectly willing to extend it if you let me know what you think is 
needed, rather than just saying "switches and muxes".  What 
*specifically* would they need beyond what I proposed?

Last time I  
check we don't put things into the kernel w/o any review and if  people 
have issues that are reasonable they get hashed out.  It seems  that the 
onus is on the initial submitter to either show that what  they are 
providing is sufficient and w/o issue or incorporate the  feedback.

Give me something I can incorporate, then.  My gripe is when the 
feedback is "don't bother" based on unspecified problems with a 
configuration more complex than what it was intended to address (but 
still, AFAICT, not outside its ability to address).

More specifically, we have a way to specify what devices are connect  on 
I2C today.  I'm not convinced there is any value in creating yet  
another mechanism, especially in an interface that in theory should  be 
linux agnostic.

We had a way to specify platform devices before, too.  If the device 
tree isn't worthwhile for i2c devices, why is it worthwhile for soc 
devices?  It seems to me that non-probable chips like i2c devices are 
precisely the kind of thing that the device tree is useful for.

-Scott