From: Lee Jones <lee@kernel.org>
To: "Eric Gonçalves" <ghatto404@gmail.com>
Cc: Krzysztof Kozlowski <krzk@kernel.org>,
Chanwoo Choi <cw00.choi@samsung.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] mfd: max77705: support revision 0x2
Date: Thu, 23 Oct 2025 14:17:32 +0100 [thread overview]
Message-ID: <20251023131732.GN475031@google.com> (raw)
In-Reply-To: <20251014043255.176499-1-ghatto404@gmail.com>
On Tue, 14 Oct 2025, Eric Gonçalves wrote:
> Revision 0x2 has been tested on the r0q (Galaxy S22) board.
>
> Signed-off-by: Eric Gonçalves <ghatto404@gmail.com>
> ---
> drivers/mfd/max77705.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/mfd/max77705.c b/drivers/mfd/max77705.c
> index e1a9bfd65856..5201a4c9c3f5 100644
> --- a/drivers/mfd/max77705.c
> +++ b/drivers/mfd/max77705.c
> @@ -105,8 +105,8 @@ static int max77705_i2c_probe(struct i2c_client *i2c)
> return -ENODEV;
>
> pmic_rev = pmic_rev_value & MAX77705_REVISION_MASK;
> - if (pmic_rev != MAX77705_PASS3)
> - return dev_err_probe(dev, -ENODEV, "Rev.0x%x is not tested\n", pmic_rev);
> + if (pmic_rev == MAX77705_PASS1)
> + return dev_err_probe(dev, -ENODEV, "Rev.0x1 is not tested\n");
What happens when PASS4 is released but not tested?
What about changing only the first line to:
if (pmic_rev < MAX77705_PASS2 || pmic_rev > MAX77705_PASS3)
> /* Active Discharge Enable */
> regmap_update_bits(max77705->regmap, MAX77705_PMIC_REG_MAINCTRL1, 1, 1);
> --
> 2.51.0
>
--
Lee Jones [李琼斯]
next prev parent reply other threads:[~2025-10-23 13:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-14 4:32 [PATCH v1] mfd: max77705: support revision 0x2 Eric Gonçalves
2025-10-23 13:17 ` Lee Jones [this message]
2025-10-23 13:46 ` Ghatto
2025-10-23 14:21 ` Lee Jones
2025-10-23 15:02 ` Eric Gonçalves
2025-11-06 13:41 ` Lee Jones
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=20251023131732.GN475031@google.com \
--to=lee@kernel.org \
--cc=cw00.choi@samsung.com \
--cc=ghatto404@gmail.com \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.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