From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] arm: dra7xx: Assign omap_vcores based on board type
Date: Sun, 19 Jun 2016 10:07:56 -0400 [thread overview]
Message-ID: <20160619140756.GG4353@bill-the-cat> (raw)
In-Reply-To: <1465295725-7620-1-git-send-email-j-keerthy@ti.com>
On Tue, Jun 07, 2016 at 04:05:25PM +0530, Keerthy wrote:
> Currently omap_vcores which holds pmic data is being assigned based
> on the SoC type. PMIC is not a part of SoC. It is logical to
> to assign omap_vcores based on board type. Hence over ride the
> vcores_init function and assign omap_vcores based on the board type.
>
> Reported-by: Nishanth Menon <nm@ti.com>
> Signed-off-by: Keerthy <j-keerthy@ti.com>
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: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20160619/4dff847a/attachment.sig>
prev parent reply other threads:[~2016-06-19 14:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-07 10:35 [U-Boot] [PATCH] arm: dra7xx: Assign omap_vcores based on board type Keerthy
2016-06-13 3:54 ` Keerthy
2016-06-19 14:07 ` Tom Rini [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=20160619140756.GG4353@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