From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/4] efikamx: remove drive strength hack from early_init_f and move it to the DCD
Date: Sat, 18 Aug 2012 01:39:04 +0200 [thread overview]
Message-ID: <201208180139.05038.marex@denx.de> (raw)
In-Reply-To: <CAKGA1bmD+SHsbr6mhwY4JUgFnMxi+XhTeGaBLWpbET1dE580+A@mail.gmail.com>
Dear Matt Sealey,
> On Fri, Aug 17, 2012 at 4:03 PM, Marek Vasut <marex@denx.de> wrote:
> > Dear Matt Sealey,
> >
> >> The i.MX Boot ROM lets us set up certain registers before U-Boot even
> >> gets executed. Rather than setting up DDR, putting U-Boot in place, and
> >> getting into pre-relocation init to set up DDR again, just do it once
> >> in the correct place. This also solves an issue where the Smarttop DDR
> >> pad settings were being applied on Smartbook.
> >>
> >> While we're at it, configure PCBID0,1,2 and the LED GPIO since we've
> >> still got room in the DCD to do so.
> >
> > [...]
> >
> >> diff --git a/board/genesi/mx51_efikamx/imximage_mx.cfg
> >> b/board/genesi/mx51_efikamx/imximage_mx.cfg index 6fe0ff9..ac9aa9a
> >> 100644 --- a/board/genesi/mx51_efikamx/imximage_mx.cfg
> >> +++ b/board/genesi/mx51_efikamx/imximage_mx.cfg
> >> @@ -1,7 +1,7 @@
> >>
> >> #
> >>
> >> +# Copyright (C) 2009 Pegatron Corporation
> >>
> >> # Copyright (C) 2010 Marek Vasut <marek.vasut@gmail.com>
> >>
> >> -#
> >> -# BASED ON: imx51evk
> >
> > Adding and removing these at will won't work I'm afraid.
> >
> >> +# Copyright (C) 2009-2012 Genesi USA, Inc.
> >>
> >> #
> >> # (C) Copyright 2009
> >> # Stefano Babic DENX Software Engineering sbabic at denx.de.
> >>
> >> @@ -43,48 +43,44 @@ BOOT_FROM spi
> >>
> >> # Address absolute address of the register
> >> # value value to be stored in the register
> >
> > So what is the actual change in the file? You replaced it with different
> > file, which makes it hard to review particular changes made.
>
> Uhh no I edited each line manually and moved the comments to make it
> more readable. The actual changes is I reviewed the drive strength set
> function in efikamx.c and moved all the settings (minus any
> erroneously set bits and reproduced settings) into the DATA lines
> where necessary.
Maybe splitting it into smaller patches then won't hurt, with proper description
etc.
> It's the same file but git doesn't do line-by-line diffs very well, it
> just seems to batch things into sections. I agree though I broke the
> copyright stuff, I got forced to use vim for about 10 minutes and I
> may have been a little heavy-handed :)
Definitelly
Best regards,
Marek Vasut
next prev parent reply other threads:[~2012-08-17 23:39 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-17 18:19 [U-Boot] [PATCH 0/4] efikamx: update Efika MX support Matt Sealey
2012-08-17 18:19 ` [U-Boot] [PATCH 1/4] efikamx: move efikamx into a new directory in preparation for new boards Matt Sealey
2012-08-17 21:01 ` Marek Vasut
2012-08-17 22:21 ` Matt Sealey
2012-08-17 18:19 ` [U-Boot] [PATCH 2/4] efikamx: remove drive strength hack from early_init_f and move it to the DCD Matt Sealey
2012-08-17 21:03 ` Marek Vasut
2012-08-17 22:05 ` Matt Sealey
2012-08-17 23:39 ` Marek Vasut [this message]
2012-08-18 15:34 ` Stefano Babic
2012-08-18 21:11 ` Matt Sealey
2012-08-18 22:29 ` Marek Vasut
2012-08-18 22:56 ` stefano babic
2012-08-20 16:34 ` Matt Sealey
2012-08-18 22:39 ` stefano babic
2012-08-17 18:19 ` [U-Boot] [PATCH 3/4] efikamx: update to Efika MX Smarttop and Smartbook boards Matt Sealey
2012-08-17 19:29 ` Benoît Thébaudeau
2012-08-17 20:10 ` Matt Sealey
2012-08-17 21:07 ` Marek Vasut
2012-08-17 22:17 ` Matt Sealey
2012-08-17 23:38 ` Marek Vasut
2012-08-18 15:50 ` Stefano Babic
2012-08-18 21:02 ` Matt Sealey
2012-08-18 22:26 ` Marek Vasut
2012-08-20 16:19 ` Matt Sealey
2012-08-21 2:21 ` Marek Vasut
2012-08-18 22:31 ` stefano babic
2012-08-17 18:19 ` [U-Boot] [PATCH 4/4] efikamx: port USB setup to new iomux model Matt Sealey
2012-08-17 20:59 ` [U-Boot] [PATCH 0/4] efikamx: update Efika MX support Marek Vasut
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=201208180139.05038.marex@denx.de \
--to=marex@denx.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox