From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] mx6q: mx6qsabrelite: add GPIO_0__CCM_CLKO and GPIO_3__CCM_CLKO2 pin mux
Date: Wed, 1 Aug 2012 15:49:54 +0200 [thread overview]
Message-ID: <20120801154954.65bcca1d@skate> (raw)
In-Reply-To: <50193267.6090504@de.bosch.com>
Le Wed, 1 Aug 2012 15:43:03 +0200,
Dirk Behme <dirk.behme@de.bosch.com> 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
next prev parent reply other threads:[~2012-08-01 13:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-01 11:05 [U-Boot] [PATCH] mx6q: mx6qsabrelite: add GPIO_0__CCM_CLKO and GPIO_3__CCM_CLKO2 pin mux Dirk Behme
2012-08-01 11:26 ` Liu Hui-R64343
2012-08-01 11:50 ` Dirk Behme
2012-08-01 12:55 ` Wolfgang Denk
2012-08-01 13:22 ` Dirk Behme
2012-08-01 13:33 ` Thomas Petazzoni
2012-08-01 13:43 ` Dirk Behme
2012-08-01 13:49 ` Thomas Petazzoni [this message]
2012-08-01 15:05 ` Fabio Estevam
2012-08-02 7:36 ` Dirk Behme
2012-08-02 7:48 ` Stefano Babic
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120801154954.65bcca1d@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.