From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: am33xx: pin modes
Date: Mon, 11 Jun 2012 07:04:17 -0700 [thread overview]
Message-ID: <20120611140417.GC12766@atomide.com> (raw)
In-Reply-To: <1BAFE6F6C881BF42822005164F1491C33EA1E6F0@DBDE01.ent.ti.com>
* Hebbar, Gururaja <gururaja.hebbar@ti.com> [120611 06:48]:
> On Mon, Jun 11, 2012 at 17:49:52, Yegor Yefremov wrote:
> > I'm working with Koen's repo (https://github.com/koenkooi/linux.git) and have a question. There are two places, where pin's function is defined:
> >
> >
> > arch/arm/mach-omap2/mux33xx.c:
> > static struct omap_mux __initdata am33xx_muxmodes[] = {
> > /**/ _AM33XX_MUXENTRY(GPMC_AD0, 0,
> > "gpmc_ad0", "mmc1_dat0", NULL, NULL,
> > NULL, NULL, NULL, "gpio1_0"),
> >
>
> This is the big AM33XX pin mux super set table. Here, Entire Mux entries for AM335x SOC
> are defined.
Please note that we're moving to the generic pinctrl framework,
and using device tree and pinctrl-single driver. So the old style
pinmux data or board-*.c files will not get merged upstream.
Regards,
Tony
next prev parent reply other threads:[~2012-06-11 14:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-11 12:19 am33xx: pin modes Yegor Yefremov
2012-06-11 13:40 ` Hebbar, Gururaja
2012-06-11 14:04 ` Tony Lindgren [this message]
2012-06-11 14:29 ` Yegor Yefremov
2012-06-12 6:28 ` Tony Lindgren
2012-06-11 14:27 ` Yegor Yefremov
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=20120611140417.GC12766@atomide.com \
--to=tony@atomide.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).