From: Lee Jones <lee@kernel.org>
To: Jakob Hauser <jahau@rocketmail.com>
Cc: Sebastian Reichel <sre@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Beomho Seo <beomho.seo@samsung.com>,
Chanwoo Choi <cw00.choi@samsung.com>,
Stephan Gerhold <stephan@gerhold.net>,
Raymond Hackley <raymondhackley@protonmail.com>,
linux-pm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
~postmarketos/upstreaming@lists.sr.ht
Subject: Re: [PATCH 02/10] mfd: rt5033: Fix chip revision readout
Date: Sun, 5 Mar 2023 10:47:04 +0000 [thread overview]
Message-ID: <20230305104704.GG2574592@google.com> (raw)
In-Reply-To: <a667a64d0cbeef00baed2d4b117ba9f50eaf3988.1677620677.git.jahau@rocketmail.com>
On Tue, 28 Feb 2023, Jakob Hauser wrote:
> After reading the data from the DEVICE_ID register, mask 0x0f needs to be
> applied to extract the revision of the chip [1].
>
> The other part of the DEVICE_ID register, mask 0xf0, is a vendor identification
> code. That's how it is set up at similar products of Richtek, e.g. RT9455 [2]
> page 21 top.
>
> [1] https://github.com/msm8916-mainline/linux-downstream/blob/GT-I9195I/drivers/mfd/rt5033_core.c#L484
> [2] https://www.richtek.com/assets/product_file/RT9455/DS9455-00.pdf
>
> Signed-off-by: Jakob Hauser <jahau@rocketmail.com>
> ---
> drivers/mfd/rt5033.c | 8 +++++---
> include/linux/mfd/rt5033-private.h | 4 ++++
> 2 files changed, 9 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/mfd/rt5033.c b/drivers/mfd/rt5033.c
> index 8029d444b794..d32467174cb5 100644
> --- a/drivers/mfd/rt5033.c
> +++ b/drivers/mfd/rt5033.c
> @@ -55,7 +55,8 @@ static const struct regmap_config rt5033_regmap_config = {
> static int rt5033_i2c_probe(struct i2c_client *i2c)
> {
> struct rt5033_dev *rt5033;
> - unsigned int dev_id;
> + unsigned int data;
In terms of nomenclature, this is a regression.
'data' is a terrible variable name. Why not keep it as-is?
> + unsigned int chip_rev;
> int ret;
>
> rt5033 = devm_kzalloc(&i2c->dev, sizeof(*rt5033), GFP_KERNEL);
> @@ -73,12 +74,13 @@ static int rt5033_i2c_probe(struct i2c_client *i2c)
> return PTR_ERR(rt5033->regmap);
> }
>
> - ret = regmap_read(rt5033->regmap, RT5033_REG_DEVICE_ID, &dev_id);
> + ret = regmap_read(rt5033->regmap, RT5033_REG_DEVICE_ID, &data);
> if (ret) {
> dev_err(&i2c->dev, "Device not found\n");
> return -ENODEV;
> }
> - dev_info(&i2c->dev, "Device found Device ID: %04x\n", dev_id);
> + chip_rev = data & RT5033_CHIP_REV_MASK;
> + dev_info(&i2c->dev, "Device found (rev. %d)\n", chip_rev);
Why not print both?
> ret = regmap_add_irq_chip(rt5033->regmap, rt5033->irq,
> IRQF_TRIGGER_FALLING | IRQF_ONESHOT,
> diff --git a/include/linux/mfd/rt5033-private.h b/include/linux/mfd/rt5033-private.h
> index 2d1895c3efbf..d18cd4572208 100644
> --- a/include/linux/mfd/rt5033-private.h
> +++ b/include/linux/mfd/rt5033-private.h
> @@ -71,6 +71,10 @@ enum rt5033_reg {
g
> /* RT5033 CHGCTRL2 register */
> #define RT5033_CHGCTRL2_CV_MASK 0xfc
>
> +/* RT5033 DEVICE_ID register */
> +#define RT5033_VENDOR_ID_MASK 0xf0
> +#define RT5033_CHIP_REV_MASK 0x0f
> +
> /* RT5033 CHGCTRL3 register */
> #define RT5033_CHGCTRL3_CFO_EN_MASK 0x40
> #define RT5033_CHGCTRL3_TIMER_MASK 0x38
> --
> 2.39.1
>
--
Lee Jones [李琼斯]
next prev parent reply other threads:[~2023-03-05 10:47 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1677620677.git.jahau.ref@rocketmail.com>
2023-02-28 22:32 ` [PATCH 00/10] Add RT5033 charger device driver Jakob Hauser
2023-02-28 22:32 ` [PATCH 01/10] mfd: rt5033: Drop rt5033-battery sub-device Jakob Hauser
2023-02-28 22:32 ` [PATCH 02/10] mfd: rt5033: Fix chip revision readout Jakob Hauser
2023-03-05 10:47 ` Lee Jones [this message]
2023-03-05 16:10 ` Jakob Hauser
2023-03-06 9:18 ` Lee Jones
2023-03-06 22:57 ` Jakob Hauser
2023-02-28 22:32 ` [PATCH 03/10] mfd: rt5033: Fix comments and style in includes Jakob Hauser
2023-03-05 10:48 ` Lee Jones
2023-03-05 16:11 ` Jakob Hauser
2023-03-06 9:15 ` Lee Jones
2023-02-28 22:32 ` [PATCH 04/10] mfd: rt5033: Fix STAT_MASK, HZ_MASK and AICR defines Jakob Hauser
2023-03-05 10:52 ` Lee Jones
2023-02-28 22:32 ` [PATCH 05/10] mfd: rt5033: Apply preparatory changes before adding rt5033-charger driver Jakob Hauser
2023-03-05 10:55 ` Lee Jones
2023-03-05 16:14 ` Jakob Hauser
2023-04-02 10:08 ` Jakob Hauser
2023-04-05 15:09 ` Lee Jones
2023-02-28 22:32 ` [PATCH 06/10] power: supply: rt5033_charger: Add RT5033 charger device driver Jakob Hauser
2023-02-28 22:32 ` [PATCH 07/10] power: supply: rt5033_charger: Add cable detection and USB OTG supply Jakob Hauser
2023-02-28 22:32 ` [PATCH 08/10] power: supply: rt5033_charger: Make use of high impedance mode Jakob Hauser
2023-04-02 10:14 ` Jakob Hauser
2023-02-28 22:32 ` [PATCH 09/10] power: supply: rt5033_battery: Adopt status property from charger Jakob Hauser
2023-02-28 22:32 ` [PATCH 10/10] dt-bindings: Add documentation for rt5033 mfd, regulator and charger Jakob Hauser
2023-02-28 23:15 ` Rob Herring
2023-03-01 2:35 ` Rob Herring
2023-03-05 15:54 ` Jakob Hauser
2023-04-02 10:21 ` Jakob Hauser
2023-03-25 16:08 ` [PATCH 00/10] Add RT5033 charger device driver Pavel Machek
2023-03-27 20:22 ` Jakob Hauser
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=20230305104704.GG2574592@google.com \
--to=lee@kernel.org \
--cc=beomho.seo@samsung.com \
--cc=broonie@kernel.org \
--cc=cw00.choi@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=jahau@rocketmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=raymondhackley@protonmail.com \
--cc=robh+dt@kernel.org \
--cc=sre@kernel.org \
--cc=stephan@gerhold.net \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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