On Tue, Jan 17, 2017 at 7:35 AM, Jacky Bai <ping.bai@xxxxxxx> wrote: >> Subject: Re: [PATCH v2 05/12] Document: dt: binding: imx: update pinctrl doc >> On Thu, Jan 12, 2017 at 3:57 AM, Jacky Bai <ping.bai@xxxxxxx> wrote: >> >> > Another thing is that we can use a pins-tool program developed by NXP >> > to generate the pinctrl configuration code that can be used directly >> > in dts. This tiny program can avoid pin function conflict. As on i.MX, >> > there are so may pins, each pin can be used for up 8 function. >> > Configuring the pins is a time-consuming work. This tools is very useful for >> customer to generate the dts code. >> >> I understand, but every silicon vendor has such a tool, all are different, >> proprietary and unfriendly to programmers and open source developers, who >> need to understand how the hardware is working without magic tools and >> secret data sheets to fix bugs. >> >> For the people working with maintaining the code it is paramount that DTS files >> are self-descriptive. > > OK. Thanks for your comments. Adding generic-pinconf in imx pinctrl needs some time > to finish and the legacy method still need be here even if generic-pinconf is added. > Do you plan to pick this legacy binding patch for now? As I said earlier: > atleast I need an indication from one of the i.MX maintainers how they > want to proceed. Yours, Linus Walleij -- 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
