From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Petazzoni Date: Wed, 1 Aug 2012 15:49:54 +0200 Subject: [U-Boot] [PATCH] mx6q: mx6qsabrelite: add GPIO_0__CCM_CLKO and GPIO_3__CCM_CLKO2 pin mux In-Reply-To: <50193267.6090504@de.bosch.com> References: <1343819151-29871-1-git-send-email-dirk.behme@de.bosch.com> <5019180C.4060109@de.bosch.com> <20120801125520.1975A203B37@gemini.denx.de> <50192D96.60902@de.bosch.com> <20120801153329.67407b1c@skate> <50193267.6090504@de.bosch.com> Message-ID: <20120801154954.65bcca1d@skate> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Le Wed, 1 Aug 2012 15:43:03 +0200, Dirk Behme a ?crit : > > The kernel has a pinctrl driver for i.MX 6, so I would rather suggest > > to fix your imx6q-sabrelite.dts Device Tree source file so that the > > audio device is properly associated with the correct pinmux > > configuration. > > I'm using > > http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commitdiff;h=b7879fe6dad97ce08e8df0bf8d408942c436d358 > > > Each device can have a pinctrl-0 DT property, which points to one or > > more pinmux configurations that are defined in imx6q.dtsi file. You can > > add additional pinmux configurations here if needed. > > Sounds like the above is incomplete, then? Yes. If this device needs certain pins to be muxed in a certain configuration, then it needs: pinctrl-names = "default"; pinctrl-0 = <&pinctrl_some_config_name>; And then in the imx6q.dtsi, the pinctrl_some_config_name pinctrl configuration needs to be defined. But I guess this starts to be a bit off-topic for the U-Boot list. What about raising the issue with i.MX 6 kernel maintainers on LAKML instead? Best regards, Thomas -- Thomas Petazzoni, Free Electrons Kernel, drivers, real-time and embedded Linux development, consulting, training and support. http://free-electrons.com