All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] dm: pinctrl: Prevent (re-)configuring pins when already done before relocation
Date: Thu, 27 Dec 2018 10:47:33 -0500	[thread overview]
Message-ID: <20181227154733.GI16433@bill-the-cat> (raw)
In-Reply-To: <20181218113050.6115-1-lukma@denx.de>

On Tue, Dec 18, 2018 at 12:30:50PM +0100, Lukasz Majewski wrote:

> This commit prevents from re-configuring pins if those were configured
> before relocation.
> 
> Some pins - like UART or DDR must be setup before relocation
> (as they have 'u-boot,dm-pre-reloc' property set in DTS). Without this
> change, those pins are re-configured after relocation (pre_reloc_only = 0,
> so we do not "continue").
> Such behavior may be a problem for DDR PAD configuration, as they might
> be already leveled/tuned with original setup).
> 
> Signed-off-by: Lukasz Majewski <lukma@denx.de>

Applied to u-boot/master, thanks!

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20181227/6cbec077/attachment.sig>

  reply	other threads:[~2018-12-27 15:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-18 11:30 [U-Boot] [PATCH] dm: pinctrl: Prevent (re-)configuring pins when already done before relocation Lukasz Majewski
2018-12-27 15:47 ` Tom Rini [this message]
2019-01-08 17:49   ` [U-Boot] " Alex Kiernan
2019-01-08 22:52     ` Lukasz Majewski
2019-01-08 23:13       ` Alex Kiernan
2019-01-08 23:24         ` Lukasz Majewski
2019-01-12  9:30           ` Alex Kiernan
2019-01-12 21:45             ` Lukasz Majewski
2019-01-16 21:35               ` Simon Glass

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=20181227154733.GI16433@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    /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.