All of lore.kernel.org
 help / color / mirror / Atom feed
From: andrew@lunn.ch (Andrew Lunn)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/1] ARM: kirkwood: Convert the mplcec4 board to pinctrl
Date: Mon, 19 Nov 2012 13:18:33 +0100	[thread overview]
Message-ID: <20121119121833.GI10259@lunn.ch> (raw)
In-Reply-To: <50AA2118.7050700@mpl.ch>

> > What do you see in /debug/pinctrl/f1010000.pinctrl/pinmux-pins contain?
> > 
> > Since i have a second UART on my board i have:
> > 
> > pin 13 (PIN13): f1010000.pinctrl (GPIO UNCLAIMED) (HOG) function uart1 group mpp13
> > pin 14 (PIN14): f1010000.pinctrl (GPIO UNCLAIMED) (HOG) function uart1 group mpp14
> > 
> > but i would expect to see function sdio.
> 
> No, I see
> 
> pin 12 (PIN12): (MUX UNCLAIMED) (GPIO UNCLAIMED)
> pin 13 (PIN13): (MUX UNCLAIMED) (GPIO UNCLAIMED)
> pin 14 (PIN14): (MUX UNCLAIMED) (GPIO UNCLAIMED)
> pin 15 (PIN15): (MUX UNCLAIMED) (GPIO UNCLAIMED)
> pin 16 (PIN16): (MUX UNCLAIMED) (GPIO UNCLAIMED)
> pin 17 (PIN17): (MUX UNCLAIMED) (GPIO UNCLAIMED)
> 
> However, there is a phandle in pinctrl at 10000/pmx-sdio/

Humm..

Try enabling CONFIG_DEBUG_PINCTRL. It prints out a lot of debug as the
driver loads.

       Andrew

  reply	other threads:[~2012-11-19 12:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-19 10:26 [PATCH 0/1] ARM: kirkwood: Convert the mplcec4 board to pinctrl Stefan Peter
2012-11-19 10:26 ` [PATCH 1/1] ARM: kirkwood: Convert " Stefan Peter
2012-11-19 10:44   ` Andrew Lunn
2012-11-19 11:18 ` [PATCH 0/1] ARM: kirkwood: Convert the " Andrew Lunn
2012-11-19 12:07   ` Stefan Peter
2012-11-19 12:18     ` Andrew Lunn [this message]
2012-11-19 13:01       ` Stefan Peter
2012-11-19 14:23         ` Thomas Petazzoni
2012-11-19 14:26         ` Andrew Lunn
2012-11-19 14:58           ` Stefan Peter

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=20121119121833.GI10259@lunn.ch \
    --to=andrew@lunn.ch \
    --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.