From: York Sun <yorksun@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] powerpc/t4240qds: add support of reading Core voltage
Date: Wed, 14 Oct 2015 13:29:05 -0700 [thread overview]
Message-ID: <561EBB11.20103@freescale.com> (raw)
In-Reply-To: <1440491401-1400-1-git-send-email-shh.xie@gmail.com>
On 08/25/2015 01:30 AM, shh.xie at gmail.com wrote:
> From: Shaohui Xie <Shaohui.Xie@freescale.com>
>
> A U-boot CMD vdd_read is implemented to read Core voltage.
>
> Signed-off-by: Shaohui Xie <Shaohui.Xie@freescale.com>
> ---
> board/freescale/t4qds/t4240qds.c | 30 ++++++++++++++++++++++++++++++
> 1 file changed, 30 insertions(+)
>
> diff --git a/board/freescale/t4qds/t4240qds.c b/board/freescale/t4qds/t4240qds.c
> index 4f2cccd..56273e4 100644
> --- a/board/freescale/t4qds/t4240qds.c
> +++ b/board/freescale/t4qds/t4240qds.c
> @@ -887,8 +887,38 @@ static int do_vdd_adjust(cmd_tbl_t *cmdtp,
> return 0;
> }
>
> +static int do_vdd_read(cmd_tbl_t *cmdtp,
> + int flag, int argc,
> + char * const argv[])
> +{
> + int vdd, ret;
> +
> + if (argc < 1)
> + return CMD_RET_USAGE;
> +
> + ret = select_i2c_ch_pca9547(I2C_MUX_CH_VOL_MONITOR);
> + if (ret) {
> + printf("VID: I2c failed to switch channel\n");
> + return 0;
> + }
> +
> + vdd = read_voltage();
> + if (vdd < 0)
> + printf("VID: Could not read voltage\n");
> + else
> + printf("VID: Core voltage is at %d mV\n", vdd);
> +
> + return 0;
> +}
> +
> U_BOOT_CMD(
> vdd_override, 2, 0, do_vdd_adjust,
> "Override VDD",
> "- override with the voltage specified in mV, eg. 1050"
> );
> +
> +U_BOOT_CMD(
> + vdd_read, 1, 0, do_vdd_read,
> + "read VDD",
> + " - Read the voltage specified in mV"
> +)
>
Can you explain why you need this command? You already get the voltage if you
run bdinfo. If you override vdd, you also get a print.
York
next prev parent reply other threads:[~2015-10-14 20:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-25 8:30 [U-Boot] [PATCH] powerpc/t4240qds: add support of reading Core voltage shh.xie at gmail.com
2015-10-14 20:29 ` York Sun [this message]
2015-10-15 2:20 ` Shaohui Xie
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=561EBB11.20103@freescale.com \
--to=yorksun@freescale.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