From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: am33xx: pin modes
Date: Mon, 11 Jun 2012 23:28:49 -0700 [thread overview]
Message-ID: <20120612062849.GD12766@atomide.com> (raw)
In-Reply-To: <4FD600AF.9070204@visionsystems.de>
* Yegor Yefremov <yegor_sub1@visionsystems.de> [120611 07:33]:
> Am 11.06.2012 16:04, schrieb Tony Lindgren:
> > * 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.
>
> O.K. Where can I see examples?
I posted the latest version of the driver yesterday, then the
documentation part has an example.
Here's also a little patch to make the old mux framework dump out
new format DT entries using debugfs when you examine debugfs with
cat /sys/kernel/debug/omap_mux/board/core or wkup. You probably need
to also add a call for omap3_mux_init into board-generic.c to also
initialize the old mux fwk if you want them both at the same time
for debugging. From the output you can grep for pins for each device.
Note that omap3 old mux fwk is not setting up separate core + wkup
domains in the old mux framework, so it only shows core.
Regards,
Tony
--- a/arch/arm/mach-omap2/mux.c
+++ b/arch/arm/mach-omap2/mux.c
@@ -35,9 +35,10 @@
#include <linux/irq.h>
#include <linux/interrupt.h>
-
#include <plat/omap_hwmod.h>
+#include <mach/id.h>
+
#include "control.h"
#include "mux.h"
#include "prm.h"
@@ -570,15 +571,26 @@ static inline void omap_mux_decode(struct seq_file *s, u16 val)
static int omap_mux_dbg_board_show(struct seq_file *s, void *unused)
{
struct omap_mux_partition *partition = s->private;
+ int pbase = (int)partition->base;
struct omap_mux_entry *e;
- u8 omap_gen = omap_rev() >> 28;
+
+ if (!(pbase & 0xfff))
+ pbase = 0x40;
+ else
+ pbase = 0;
+
+ seq_printf(s, "\t\tpinctrl-single,cells = <\n");
list_for_each_entry(e, &partition->muxmodes, node) {
struct omap_mux *m = &e->mux;
char m0_def[OMAP_MUX_DEFNAME_LEN];
char *m0_name = m->muxnames[0];
u16 val;
- int i, mode;
+ int padconf_offset, i, mode;
+
+ padconf_offset = m->reg_offset - pbase;
+ if (cpu_is_omap3630() && padconf_offset > 0x5ca)
+ continue;
if (!m0_name)
continue;
@@ -593,18 +605,14 @@ static int omap_mux_dbg_board_show(struct seq_file *s, void *unused)
}
val = omap_mux_read(partition, m->reg_offset);
mode = val & OMAP_MUX_MODE7;
- if (mode != 0)
- seq_printf(s, "/* %s */\n", m->muxnames[mode]);
-
- /*
- * XXX: Might be revisited to support differences across
- * same OMAP generation.
- */
- seq_printf(s, "OMAP%d_MUX(%s, ", omap_gen, m0_def);
+ seq_printf(s, "\t\t\t0x%x 0x%x\t/* %s.%s gpio%i ",
+ padconf_offset, val, m->muxnames[0], m->muxnames[mode], m->gpio);
omap_mux_decode(s, val);
- seq_printf(s, "),\n");
+ seq_printf(s, " */\n");
}
+ seq_printf(s, "\t\t>;\n");
+
return 0;
}
next prev parent reply other threads:[~2012-06-12 6:28 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
2012-06-11 14:29 ` Yegor Yefremov
2012-06-12 6:28 ` Tony Lindgren [this message]
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=20120612062849.GD12766@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 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.