From: Frank Li <Frank.li@nxp.com>
To: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
imx@lists.linux.dev, Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Joy Zou <joy.zou@nxp.com>
Subject: Re: [PATCH v3 2/2] regulator: pf9453: add PMIC PF9453 support
Date: Mon, 16 Dec 2024 11:27:02 -0500 [thread overview]
Message-ID: <Z2BU1itPMjVQRMkW@lizhi-Precision-Tower-5810> (raw)
In-Reply-To: <689b1095-0dfe-4204-843d-5a7c23213aad@wanadoo.fr>
On Sat, Dec 14, 2024 at 11:57:59AM +0100, Christophe JAILLET wrote:
> Le 13/12/2024 à 21:46, Frank Li a écrit :
> > From: Joy Zou <joy.zou-3arQi8VN3Tc@public.gmane.org>
> >
> > Support new PMIC PF9453, which is totally difference with PCA9450. So
> > create new file for it.
> >
> > The PF9453 is a single chip Power Management IC (PMIC) specifically
> > designed for i.MX 91 processor. It provides power supply solutions for IoT
> > (Internet of Things), smart appliance, and portable applications where size
> > and efficiency are critical. The device provides four high efficiency
> > step-down regulators, three LDOs, one 400 mA load switch and 32.768 kHz
> > crystal oscillator driver.
>
> ...
>
> > +/* PF9453_REG_BUCK2_CTRL bits */
> > +#define BUCK2_RAMP_MASK GENMASK(7, 4)
>
> This was 0xC0 in previous patch, so GENMASK(7, 6) if I'm correct.
> Which one is the good one?
>
> (the datasheet I've found does not give any details, so I can't check)
Good capture! It should be GENMASK(7, 6)
Frank
>
> > +#define BUCK2_RAMP_25MV 0x0
> > +#define BUCK2_RAMP_12P5MV 0x1
> > +#define BUCK2_RAMP_6P25MV 0x2
> > +#define BUCK2_RAMP_3P125MV 0x3
>
> ...
>
> > +/* PF9453_REG_LDO2_VOLT bits */
> > +#define LDO2_EN_MASK GENMASK(1, 0)
> > +#define LDO2OUT_MASK GENMASK(6, 0)
> > +
> > +/* PF9453_REG_LDOSNVS_VOLT bits */
> > +#define LDOSNVS_EN_MASK 0x1
>
> GENMASK(0, 0) to be consistent?
>
> > +#define LDOSNVSCFG1_MASK GENMASK(6, 0)
> > +
> > +/* PF9453_REG_IRQ bits */
> > +#define IRQ_RSVD 0x80
> > +#define IRQ_RSTB 0x40
> > +#define IRQ_ONKEY 0x20
> > +#define IRQ_RESETKEY 0x10
> > +#define IRQ_VR_FLT1 0x08
> > +#define IRQ_LOWVSYS 0x04
> > +#define IRQ_THERM_100 0x02
> > +#define IRQ_THERM_80 0x01
> > +
> > +/* PF9453_REG_RESET_CTRL bits */
> > +#define WDOG_B_CFG_MASK GENMASK(7, 4)
>
> This was 0xC0 in previous patch, so GENMASK(7, 6) if I'm correct.
> Which one is the good one?
>
> > +#define WDOG_B_CFG_NONE 0x00
> > +#define WDOG_B_CFG_WARM 0x40
> > +#define WDOG_B_CFG_COLD 0x80
>
> ...
>
> CJ
prev parent reply other threads:[~2024-12-16 16:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-13 20:46 [PATCH v3 0/2] regulator: add new PMIC PF9453 support Frank Li
2024-12-13 20:46 ` [PATCH v3 1/2] regulator: dt-bindings: pca9450: Add nxp,pf9453 compatible string Frank Li
2024-12-16 9:25 ` Krzysztof Kozlowski
2024-12-13 20:46 ` [PATCH v3 2/2] regulator: pf9453: add PMIC PF9453 support Frank Li
2024-12-14 10:57 ` Christophe JAILLET
2024-12-16 16:27 ` Frank Li [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=Z2BU1itPMjVQRMkW@lizhi-Precision-Tower-5810 \
--to=frank.li@nxp.com \
--cc=broonie@kernel.org \
--cc=christophe.jaillet@wanadoo.fr \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=imx@lists.linux.dev \
--cc=joy.zou@nxp.com \
--cc=krzk+dt@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
/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