linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: s.hauer@pengutronix.de (Sascha Hauer)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 7/8] ARM: dts: imx: add IMX50 SoC device tree bindings
Date: Tue, 22 Oct 2013 23:57:47 +0200	[thread overview]
Message-ID: <20131022215747.GC31304@pengutronix.de> (raw)
In-Reply-To: <CAHCPf3tLovKaCWAQn13c+ifvzQH4ojcXyevYxbh018XYYK=xJA@mail.gmail.com>

On Tue, Oct 22, 2013 at 03:08:43PM -0500, Matt Sealey wrote:
> On Tue, Oct 22, 2013 at 7:35 AM, Sascha Hauer <s.hauer@pengutronix.de> wrote:
> > On Fri, Oct 18, 2013 at 04:04:19PM +1000, gerg at uclinux.org wrote:
> >> From: Greg Ungerer <gerg@uclinux.org>
> >>
> >> Create device tree bindings for the Freescale IMX50 SoC. This was based on
> >> the IMX53 bindings with changes made as necessary.
> >>
> >> Signed-off-by: Greg Ungerer <gerg@uclinux.org>
> >> ---
> >> +
> >> +                     iomuxc: iomuxc at 53fa8000 {
> >> +                             compatible = "fsl,imx50-iomuxc";
> >> +                             reg = <0x53fa8000 0x4000>;
> >> +
> >> +                             fec {
> >> +                                     pinctrl_fec_1: fecgrp-1 {
> >> +                                             fsl,pins = <
> >> +                                                     MX50_PAD_SSI_RXFS__FEC_MDC      0x80
> >> +                                                     MX50_PAD_SSI_RXC__FEC_MDIO      0x80
> >> +                                                     MX50_PAD_DISP_D0__FEC_TX_CLK    0x80
> >> +                                                     MX50_PAD_DISP_D1__FEC_RX_ERR    0x80
> >> +                                                     MX50_PAD_DISP_D2__FEC_RX_DV     0x80
> >> +                                                     MX50_PAD_DISP_D3__FEC_RDATA_1   0x80
> >> +                                                     MX50_PAD_DISP_D4__FEC_RDATA_0   0x80
> >> +                                                     MX50_PAD_DISP_D5__FEC_TX_EN     0x80
> >> +                                                     MX50_PAD_DISP_D6__FEC_TDATA_1   0x80
> >> +                                                     MX50_PAD_DISP_D7__FEC_TDATA_0   0x80
> >> +                                             >;
> >> +                                     };
> >> +
> >
> > Shawn recently removed the pinctrl groups here and referenced to this
> > node by doing
> >
> > &iomuxc {
> >         fec {
> >                 ...
> >         };
> > };
> >
> >> +                             cspi {
> >> +                                     pinctrl_cspi_1: cspigrp-1 {
> >> +                                             fsl,pins = <
> >> +                                                     MX50_PAD_CSPI_SCLK__CSPI_SCLK   0
> >
> > 0 is definitely wrong here. We have 0x80000000 for "Don't touch
> > padctrl", but otherwise this should contain some real padctrl settings.
> 
> A more pressing question is in what world did the bootloader not
> already set these pins up and if they are already set up, why are they
> loitering in the device tree?

Having NO_PAD_CTRL in the devicetree doesn't make sense, you're right.
Either a pin has to be configured by the bootloader completely or not at
all. Having the mux configured by the kernel and the drive strength by
the bootloader is broken by design. All pins should have a complete
padctrl setup and NO_PAD_CTRL should be dropped.

Sascha

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

  reply	other threads:[~2013-10-22 21:57 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-18  6:04 [PATCH 0/8] ARM: imx: add IMX50 SoC support gerg at uclinux.org
2013-10-18  6:04 ` [PATCH 1/8] ARM: imx: add debug uart support for IMX50 SoC gerg at uclinux.org
2013-10-18  6:04 ` [PATCH 2/8] ARM: imx: add clocking support code for the " gerg at uclinux.org
2013-10-22 12:27   ` Sascha Hauer
2013-10-23  3:19     ` Greg Ungerer
2013-10-23  9:19   ` Jason Cooper
2013-10-23 12:44     ` Greg Ungerer
2013-10-23 13:42       ` Jason Cooper
2013-10-24 15:11   ` Shawn Guo
2013-10-18  6:04 ` [PATCH 3/8] ARM: imx: add pinctrl " gerg at uclinux.org
2013-10-24 15:16   ` Shawn Guo
2013-10-18  6:04 ` [PATCH 4/8] ARM: imx: add support code for IMX50 based machines gerg at uclinux.org
2013-10-24 11:11   ` Rob Herring
2013-10-28  6:38     ` Greg Ungerer
2013-10-28 19:57       ` Rob Herring
2013-10-18  6:04 ` [PATCH 5/8] ARM: imx: allow configuration of the IMX50 SoC gerg at uclinux.org
2013-10-24 15:17   ` Shawn Guo
2013-10-18  6:04 ` [PATCH 6/8] ARM: dts: imx: add device tree pin definitions for the IMX50 gerg at uclinux.org
2013-10-18  6:04 ` [PATCH 7/8] ARM: dts: imx: add IMX50 SoC device tree bindings gerg at uclinux.org
2013-10-22 12:35   ` Sascha Hauer
2013-10-22 20:08     ` Matt Sealey
2013-10-22 21:57       ` Sascha Hauer [this message]
2013-10-22 22:42         ` Benoît Thébaudeau
2013-10-22 23:06           ` Matt Sealey
2013-10-23  0:17             ` Benoît Thébaudeau
2013-10-23  5:55               ` Greg Ungerer
2013-10-24 21:13               ` Matt Sealey
2013-10-23  5:40     ` Greg Ungerer
2013-10-24 15:26   ` Shawn Guo
2013-10-18  6:04 ` [PATCH 8/8] ARM: dts: imx: add device tree support for Freescale imx50evk board gerg at uclinux.org
2013-10-24 15:29   ` Shawn Guo
2013-10-23  9:14 ` [PATCH 0/8] ARM: imx: add IMX50 SoC support Jason Cooper
2013-10-23 12:39   ` Greg Ungerer
2013-10-24 15:00 ` Shawn Guo
2013-10-25 12:53   ` Greg Ungerer

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=20131022215747.GC31304@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --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).