Grant Likely wrote:
On 1/3/08, Scott Wood scottwood@freescale.com wrote:
Grant Likely wrote:
On 1/3/08, Timur Tabi timur@freescale.com wrote:
Grant Likely wrote:
Why not be a child of the i2c bus with a phandle to the ssi bus?
Because when I probe the SSI node, I want to know what the attached codec is. So if anything, I would need a pointer from the SSI bus *to* the respective child on the I2C bus.
That's fine too (it's what is done with Ethernet PHYs). My preference is the other way around, but it's not a big issue in this case.
I'd just link in both directions, and let software follow it in whichever direction it prefers.
Gah! Don't do that! Then you need to maintain both directions in the dts file.
So? What's wrong with that?
Software is good at generating reverse mappings.
What software would that be? Currently, there is no software that will do that? Or are you saying that you want my driver to search the entire device tree until it finds the reverse mapping? I don't think *that* is a good idea.
Don't put that burden on the dts author.
As the DTS author in question, I hereby declare that such a requirement is not a burden in the slightest. Thank you.