On Mon, Jan 13, 2014 at 12:16:10AM +0100, Linus Walleij wrote: > > I'm also surprised that you have to know multiple constants > > (mux register, input register, config register offsets) to select a > > particular pin. I would have expected that you could have one constant > > from which the driver is able to compute the other ones. > > I might have merged this but I was younger then :-/ > > Now I don't like the looks of this. I think the DT typically shall not > store register offsets and bitfield information. I think doing > so is taking away the responsibility of the driver knowing the > hardware and moving too close to Open Firmware. We only have data in device tree, and drivers, at least imx pinctrl driver, still need to know hardware for how to apply these data into hardware. As I just replied to Arnd, all the motivation of having these data in device tree is to release kernel from being bloated by those huge mount of data due to the complexity and flexibility of IMX pin controller. Shawn -- 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
