From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [PATCH 2/3] ARM: imx: vining2000: Properly discern PFUZE100 and PFUZE200
Date: Wed, 15 Jan 2020 11:27:31 +0100 [thread overview]
Message-ID: <20200115102732.167211-2-marex@denx.de> (raw)
In-Reply-To: <20200115102732.167211-1-marex@denx.de>
The PFUZE100 and PFUZE200 PMICs can be discerned by bit 0 in DeviceID
register. Print the correct identification of the PMICs.
Signed-off-by: Marek Vasut <marex@denx.de>
Cc: Fabio Estevam <fabio.estevam@nxp.com>
Cc: Silvio Fricke <silvio.fricke@softing.com>
Cc: Stefano Babic <sbabic@denx.de>
---
board/softing/vining_2000/vining_2000.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/board/softing/vining_2000/vining_2000.c b/board/softing/vining_2000/vining_2000.c
index 6dc3fc8b50..c74c06eaee 100644
--- a/board/softing/vining_2000/vining_2000.c
+++ b/board/softing/vining_2000/vining_2000.c
@@ -146,7 +146,7 @@ static struct pmic *pfuze_init(unsigned char i2cbus)
return NULL;
pmic_reg_read(p, PFUZE100_DEVICEID, ®);
- printf("PMIC: PFUZE100 ID=0x%02x\n", reg);
+ printf("PMIC: PFUZE%i00 ID=0x%02x\n", (reg & 1) ? 2 : 1, reg);
/* Set SW1AB stanby volage to 0.975V */
pmic_reg_read(p, PFUZE100_SW1ABSTBY, ®);
--
2.24.1
next prev parent reply other threads:[~2020-01-15 10:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-15 10:27 [PATCH 1/3] ARM: imx: vining2000: Clean up uSDHC4 setup Marek Vasut
2020-01-15 10:27 ` Marek Vasut [this message]
2020-01-20 20:18 ` [PATCH 2/3] ARM: imx: vining2000: Properly discern PFUZE100 and PFUZE200 sbabic at denx.de
2020-01-15 10:27 ` [PATCH 3/3] ARM: imx: vining2000: Enable SPL SDP by default Marek Vasut
2020-01-20 20:18 ` sbabic at denx.de
2020-01-15 12:40 ` [PATCH 1/3] ARM: imx: vining2000: Clean up uSDHC4 setup Stefano Babic
2020-01-20 20:17 ` sbabic at denx.de
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=20200115102732.167211-2-marex@denx.de \
--to=marex@denx.de \
--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