[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120119103112.GD22818@atomide.com>
Date: Thu, 19 Jan 2012 02:31:13 -0800
From: Tony Lindgren <tony@...mide.com>
To: Grant Likely <grant.likely@...retlab.ca>
Cc: Shawn Guo <shawn.guo@...aro.org>,
"linus.walleij@...ricsson.com" <linus.walleij@...ricsson.com>,
"devicetree-discuss@...ts.ozlabs.org"
<devicetree-discuss@...ts.ozlabs.org>,
"s.hauer@...gutronix.de" <s.hauer@...gutronix.de>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"rob.herring@...xeda.com" <rob.herring@...xeda.com>,
"kernel@...gutronix.de" <kernel@...gutronix.de>,
"cjb@...top.org" <cjb@...top.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
Dong Aisheng <dongas86@...il.com>
Subject: Re: Pinmux bindings proposal
* Grant Likely <grant.likely@...retlab.ca> [120118 11:48]:
> On Wed, Jan 18, 2012 at 07:32:56AM -0800, Tony Lindgren wrote:
> >
> > But then the .dts file becomes an unreadable matrix unless we have
> > a preprocessor..
>
> One node per pin does get excessive in a hurry. I prefer the one node
> per pin controller. Tools can be written to make writing the
> definition easier.
OK that's fine with me. It would be nice to have the .dts readable
too, so I'd prefer a preprocessor over a .dts generation tool to
keep the .dts files readable. Bugs in .dts file can be a big pain
to debug it seems.
Regards,
Tony
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists