From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
Cc: Barebox List <barebox@lists.infradead.org>
Subject: Re: [PATCH 2/3] scripts/kwbimage: Make BINARY files relative to config file
Date: Thu, 15 Oct 2015 11:44:52 +0200 [thread overview]
Message-ID: <20151015114452.33d8e46f@free-electrons.com> (raw)
In-Reply-To: <561F7212.1010205@gmail.com>
Hello,
On Thu, 15 Oct 2015 11:29:54 +0200, Sebastian Hesselbarth wrote:
> > - http://git.denx.de/?p=u-boot.git;a=tree;f=arch/arm/mach-mvebu/serdes
> > for the SERDES lane initialization
>
> ... I don't see why SERDES init is important that early (for production
> use). I think SERDES init should be/stay part of the PHY init code we
> already have.
Agreed. It's done this way in U-Boot because it was done this way in
the vendor U-Boot. But it is obviously not the best/proper way of doing
things.
Note I'm also working on making the kernel SERDES/PHY aware, so that
we can turn on/off the unused SERDES lanes (and save power).
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2015-10-15 9:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-15 8:18 Sascha Hauer
2015-10-15 8:18 ` [PATCH 1/3] scripts/kwbimage: Move configfile opening to the function that reads it Sascha Hauer
2015-10-15 8:18 ` [PATCH 2/3] scripts/kwbimage: Make BINARY files relative to config file Sascha Hauer
2015-10-15 9:00 ` Thomas Petazzoni
2015-10-15 9:29 ` Sebastian Hesselbarth
2015-10-15 9:44 ` Thomas Petazzoni [this message]
2015-10-19 6:40 ` Sascha Hauer
2015-10-15 10:44 ` Sascha Hauer
2015-10-15 8:18 ` [PATCH 3/3] ARM: mvebu: Lenovo IX4 300D: Fix pblb generation 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=20151015114452.33d8e46f@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=barebox@lists.infradead.org \
--cc=sebastian.hesselbarth@gmail.com \
/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