linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: u.kleine-koenig@pengutronix.de (Uwe Kleine-König)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/6] ARM: dts: imx25: substitute NO_PAD_CTL by the respective reset value
Date: Mon, 11 Jul 2016 09:37:22 +0200	[thread overview]
Message-ID: <20160711073721.GM16643@pengutronix.de> (raw)
In-Reply-To: <CAOMZO5A=6HLPacwp0seBn_s+AVF7zaUjUO8wOb1WoyvU1JrH7A@mail.gmail.com>

Hello Fabio,

On Sun, Jul 10, 2016 at 04:10:12PM -0300, Fabio Estevam wrote:
> On Sun, Jul 10, 2016 at 7:07 AM, Uwe Kleine-K?nig <uwe@kleine-koenig.org> wrote:
> 
> >  arch/arm/boot/dts/imx25-eukrea-cpuimx25.dtsi       | 18 +++----
> >  .../imx25-eukrea-mbimxsd25-baseboard-cmo-qvga.dts  |  2 +-
> > diff --git a/arch/arm/boot/dts/imx25-pdk.dts b/arch/arm/boot/dts/imx25-pdk.dts
> > index c823e45a7a01..643d083951ef 100644
> > --- a/arch/arm/boot/dts/imx25-pdk.dts
> > +++ b/arch/arm/boot/dts/imx25-pdk.dts
> 
> >         pinctrl_fec: fecgrp {
> >                 fsl,pins = <
> > -                       MX25_PAD_FEC_MDC__FEC_MDC               0x80000000
> > +                       MX25_PAD_FEC_MDC__FEC_MDC               0x00000060
> >                         MX25_PAD_FEC_MDIO__FEC_MDIO             0x400001e0
> > -                       MX25_PAD_FEC_TDATA0__FEC_TDATA0         0x80000000
> > -                       MX25_PAD_FEC_TDATA1__FEC_TDATA1         0x80000000
> > -                       MX25_PAD_FEC_TX_EN__FEC_TX_EN           0x80000000
> > -                       MX25_PAD_FEC_RDATA0__FEC_RDATA0         0x80000000
> > -                       MX25_PAD_FEC_RDATA1__FEC_RDATA1         0x80000000
> > -                       MX25_PAD_FEC_RX_DV__FEC_RX_DV           0x80000000
> > -                       MX25_PAD_FEC_TX_CLK__FEC_TX_CLK         0x1c0
> > -                       MX25_PAD_A17__GPIO_2_3                  0x80000000
> > -                       MX25_PAD_D12__GPIO_4_8                  0x80000000
> > +                       MX25_PAD_FEC_TDATA0__FEC_TDATA0         0x00000060
> > +                       MX25_PAD_FEC_TDATA1__FEC_TDATA1         0x00000060
> > +                       MX25_PAD_FEC_TX_EN__FEC_TX_EN           0x00000060
> > +                       MX25_PAD_FEC_RDATA0__FEC_RDATA0         0x000000c1
> > +                       MX25_PAD_FEC_RDATA1__FEC_RDATA1         0x000000c0
> > +                       MX25_PAD_FEC_RX_DV__FEC_RX_DV           0x000000c0
> > +                       MX25_PAD_FEC_TX_CLK__FEC_TX_CLK         0x000001c0
> > +                       MX25_PAD_A17__GPIO_2_3                  0x00000000
> > +                       MX25_PAD_D12__GPIO_4_8                  0x000000a1
> 
> Looking at the mx25pdk U-boot source code we see that FEC pins are not
> configured as per the default power-on reset values, so this changes
> the behavior.
> 
> >         pinctrl_i2c1: i2c1grp {
> >                 fsl,pins = <
> > -                       MX25_PAD_I2C1_CLK__I2C1_CLK             0x80000000
> > -                       MX25_PAD_I2C1_DAT__I2C1_DAT             0x80000000
> > +                       MX25_PAD_I2C1_CLK__I2C1_CLK             0x000000a8
> > +                       MX25_PAD_I2C1_DAT__I2C1_DAT             0x000000a8
> 
> Same happens with I2C pins.
> 
> To stay in the safe side I would only change the pins that have GPIO
> functionality in this patch.
> 
> Then we could later change each 0x80000000 occurrance by replacing it
> with the actual PAD register value instead of the power on defaults.

Why later?

Best regards
Uwe

-- 
Pengutronix e.K.                           | Uwe Kleine-K?nig            |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |

  reply	other threads:[~2016-07-11  7:37 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-10 10:07 [PATCH 0/6] ARM: dts: imx cleanups Uwe Kleine-König
2016-07-10 10:07 ` [PATCH 1/6] ARM: dts: drop function device nodes for pinctrl-imx nodes Uwe Kleine-König
2016-07-10 10:07 ` [PATCH 2/6] ARM: dts: imx25: don't configure reserved pad settings Uwe Kleine-König
2016-07-10 10:07 ` [PATCH 3/6] ARM: dts: imx25: substitute NO_PAD_CTL by the respective reset value Uwe Kleine-König
2016-07-10 19:10   ` Fabio Estevam
2016-07-11  7:37     ` Uwe Kleine-König [this message]
2016-07-11 10:56       ` Fabio Estevam
2016-07-12  7:38         ` Uwe Kleine-König
2016-07-12 15:15           ` Fabio Estevam
2016-07-12 18:32             ` Fabio Estevam
2016-07-12 19:15               ` Uwe Kleine-König
2016-07-12 20:30                 ` Fabio Estevam
2016-07-12 20:40                   ` Fabio Estevam
2016-07-13  6:25                     ` Uwe Kleine-König
2016-07-13 16:18                       ` Fabio Estevam
2016-07-14 17:04                       ` Fabio Estevam
2016-07-14 18:34                         ` Uwe Kleine-König
2016-07-14 19:16                           ` Fabio Estevam
2016-07-14 19:21                             ` Uwe Kleine-König
2016-07-10 10:07 ` [PATCH 4/6] ARM: dts: imx6q: don't configure reserved pad settings Uwe Kleine-König
2016-07-10 10:07 ` [PATCH 5/6] ARM: dts: imx: fix polarity of fec reset gpios Uwe Kleine-König
2016-07-10 10:07 ` [PATCH 6/6] ARM: dts: imx6-wandboard: substitute NO_PAD_CTL by the respective reset value Uwe Kleine-König

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=20160711073721.GM16643@pengutronix.de \
    --to=u.kleine-koenig@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).