From: Chin Liang See <clsee@altera.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC PATCH] arm: socfpga: Update iomux and pll for c5 socdk RevE
Date: Wed, 11 May 2016 21:35:11 +0800 [thread overview]
Message-ID: <1462973711.1933.0.camel@altera.com> (raw)
In-Reply-To: <573252D8.2090609@denx.de>
On Tue, 2016-05-10 at 23:30 +0200, Marek Vasut wrote:
> On 05/10/2016 10:13 PM, dinguyen at opensource.altera.com wrote:
> > From: Dinh Nguyen <dinguyen@kernel.org>
> >
> > Update the pinmux and pll configuration for the Cyclone5 RevE or
> > later devkit.
> >
> > Signed-off-by: Dinh Nguyen <dinguyen@opensource.altera.com>
> > ---
> > Hi Marek,
>
> Hi!
>
> > Without these pinmux and pll changes, DS-5 is unable to connect to
> > my board
> > and Linux is stuck in a loop and eventually the watchdog will
> > trigger a
> > reset.
> >
> > I tested these changes on an earlier rev board, and it seem to be
> > stable as
> > well. When you get a chance, can you try on your devkit?
>
> Tested-by: Marek Vasut <marex@denx.de>
>
> > >
Acked-by: Chin Liang See <clsee@altera.com>
Thanks
Chin Liang
prev parent reply other threads:[~2016-05-11 13:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-10 20:13 [U-Boot] [RFC PATCH] arm: socfpga: Update iomux and pll for c5 socdk RevE dinguyen at opensource.altera.com
2016-05-10 21:30 ` Marek Vasut
2016-05-11 13:35 ` Chin Liang See [this message]
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=1462973711.1933.0.camel@altera.com \
--to=clsee@altera.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox