From mboxrd@z Thu Jan 1 00:00:00 1970 From: Simon Glass Subject: Pinmux with device tree Date: Wed, 18 May 2011 09:34:45 -0700 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: devicetree-discuss-bounces+gldd-devicetree-discuss=m.gmane.org-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org Sender: devicetree-discuss-bounces+gldd-devicetree-discuss=m.gmane.org-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org To: devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org List-Id: devicetree@vger.kernel.org Hi, I see a new pinmux system in the LKML. Has anyone looked at how to represent pinmux settings in the device tree? On a related topic, the examples that are used for GPIOs assume a flags word which describes things like pull-ups, direction, etc. This seems pretty cumbersome and gets worse with pinmuxes. People editing the device trees want to see symbolic information rather than a coded number, a bit like a #define. I can see this can be done with strings but this is inefficient in time and space, and is error-prone. Is there support for this in device trees that I have missed? Regards, Simon