From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] keystone2: use correct EFUSE_BOOTROM fileds to configure speed
Date: Mon, 15 Jun 2015 10:31:13 -0400 [thread overview]
Message-ID: <20150615143113.GQ1728@bill-the-cat> (raw)
In-Reply-To: <1434372855-1422-1-git-send-email-vitalya@ti.com>
On Mon, Jun 15, 2015 at 08:54:15AM -0400, Vitaly Andrianov wrote:
> The get_max_arm_speed() and get_max_dev_speed() used wrong register
> fields to get the maximum speeds. This commit fixes the bug.
>
> Signed-off-by: Vitaly Andrianov <vitalya@ti.com>
Reviewed-by: Tom Rini <trini@konsulko.com>
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20150615/6c51964b/attachment.sig>
next prev parent reply other threads:[~2015-06-15 14:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-15 12:54 [U-Boot] [PATCH] keystone2: use correct EFUSE_BOOTROM fileds to configure speed Vitaly Andrianov
2015-06-15 14:31 ` Tom Rini [this message]
2015-06-19 20:24 ` [U-Boot] " Tom Rini
2015-06-23 11:33 ` Vitaly Andrianov
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=20150615143113.GQ1728@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox