linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: device tree binding documentation outdated
Date: Thu, 26 Sep 2013 20:51:58 +0100	[thread overview]
Message-ID: <20130926195158.GS12758@n2100.arm.linux.org.uk> (raw)

Can someone please point me at the current documentation for the
iMX6DL pinctrl bindings?

I mean the stuff which looks like this:

#define MX6QDL_PAD_ENET_MDC__ESAI_TX5_RX0           0x1e8 0x5b8 0x858 0x2 0x0

which clearly doesn't match:

Required properties for pin configuration node:
- fsl,pins: two integers array, represents a group of pins mux and config
  setting. The format is fsl,pins = <PIN_FUNC_ID CONFIG>, PIN_FUNC_ID is a
  pin working on a specific function, which consists of a tuple of
  <mux_reg conf_reg input_reg mux_val input_val>.  CONFIG is the pad setting
  value like pull-up on this pin.

I thought DT was supposed to make bringing up support on new hardware
easier, but without documentation, I'm frankly stuffed with the cubox-i,
because it's impossible to work out what the right pinctrl settings
should be from what seems to be an undocumented pile of random numbers
stuffed into DT.

Thanks.

             reply	other threads:[~2013-09-26 19:51 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-26 19:51 Russell King - ARM Linux [this message]
2013-09-26 20:29 ` device tree binding documentation outdated Fabio Estevam
2013-09-26 20:59   ` Russell King - ARM Linux
2013-09-26 23:10     ` Matt Sealey
2013-09-26 23:29       ` Russell King - ARM Linux
2013-09-26 23:48         ` Matt Sealey
2013-09-27 13:15         ` Jason Cooper
2013-09-27 17:05           ` Russell King - ARM Linux
2013-09-27 18:31             ` Russell King - ARM Linux
2013-09-27 18:52               ` Fabio Estevam
2013-09-27 20:16                 ` Matt Sealey
2013-09-27 20:43                   ` Russell King - ARM Linux
2013-09-26 23:25     ` Fabio Estevam
2013-09-27 12:13       ` Russell King - ARM Linux
2013-09-27 13:26         ` Shawn Guo
2013-09-27 15:19           ` Russell King - ARM Linux
2013-09-27 15:49             ` Russell King - ARM Linux
2013-09-27 16:52             ` Matt Sealey
2013-09-27 17:49               ` Russell King - ARM Linux
2013-09-27 18:33                 ` Matt Sealey
2013-09-27 19:05                   ` Russell King - ARM Linux
2013-09-27 19:41                     ` Matt Sealey
2013-09-27 19:48                       ` Matt Sealey
2013-09-27 20:21                         ` Russell King - ARM Linux
2013-09-28  8:38                           ` Russell King - ARM Linux
2013-09-29  6:13                             ` Shawn Guo
2013-09-29  6:23                               ` Duan Fugang-B38611
2013-09-29  6:35                                 ` Shawn Guo
2013-09-29  6:47                                   ` Duan Fugang-B38611
2013-10-02 19:33                               ` Russell King - ARM Linux
2013-10-02 23:49                                 ` Russell King - ARM Linux
2013-10-03  2:21                                   ` Fabio Estevam
2013-10-04 15:45                                   ` Shawn Guo
2013-10-04 15:58                                     ` Russell King - ARM Linux
2013-09-29  5:01                         ` Shawn Guo
2013-09-27 20:18                       ` Russell King - ARM Linux
2013-09-28  3:28                       ` Fabio Estevam
2013-09-26 21:35   ` Linus Walleij
2013-09-27  2:51     ` Shawn Guo
2013-09-27  8:45       ` Russell King - ARM Linux
2013-09-27 12:28         ` Shawn Guo
2013-09-27 13:12           ` Jason Cooper
2013-09-27 13:21             ` Russell King - ARM Linux
2013-09-27 13:29               ` Linus Walleij
2013-09-27 13:31               ` Jason Cooper
2013-09-27 16:33                 ` Matt Sealey
2013-09-27 20:52                   ` Russell King - ARM Linux
2013-09-27 13:52               ` Arnaud Patard (Rtp)
2013-09-27 15:40           ` Matt Sealey
2013-09-27  9:49 ` Russell King - ARM Linux
2013-09-27 12:08   ` Sascha Hauer

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=20130926195158.GS12758@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --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).