regulator: mt6358: Fail probe on unknown chip ID
authorChen-Yu Tsai <wenst@chromium.org>
Wed, 13 Sep 2023 08:29:16 +0000 (16:29 +0800)
committerMark Brown <broonie@kernel.org>
Mon, 25 Sep 2023 12:19:48 +0000 (14:19 +0200)
The MT6358 and MT6366 PMICs, and likely many others from MediaTek, have
a chip ID register, making the chip semi-discoverable.

The driver currently supports two PMICs and expects to be probed on one
or the other. It does not account for incorrect mfd driver entries or
device trees. While these should not happen, if they do, it could be
catastrophic for the device. The driver should be sure the hardware is
what it expects.

Make the driver fail to probe if the chip ID presented is not a known
one.

Suggested-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
Fixes: f0e3c6261af1 ("regulator: mt6366: Add support for MT6366 regulator")
Signed-off-by: Chen-Yu Tsai <wenst@chromium.org>
Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
Link: https://lore.kernel.org/r/20230913082919.1631287-2-wenst@chromium.org
Signed-off-by: Mark Brown <broonie@kernel.org>
drivers/regulator/mt6358-regulator.c

index b9cda2210c3308655a27914429c7ff52965cb03a..a1eae45f5fee5eaa983caf9bdc967a3ec9698050 100644 (file)
@@ -676,12 +676,18 @@ static int mt6358_regulator_probe(struct platform_device *pdev)
        const struct mt6358_regulator_info *mt6358_info;
        int i, max_regulator, ret;
 
-       if (mt6397->chip_id == MT6366_CHIP_ID) {
-               max_regulator = MT6366_MAX_REGULATOR;
-               mt6358_info = mt6366_regulators;
-       } else {
+       switch (mt6397->chip_id) {
+       case MT6358_CHIP_ID:
                max_regulator = MT6358_MAX_REGULATOR;
                mt6358_info = mt6358_regulators;
+               break;
+       case MT6366_CHIP_ID:
+               max_regulator = MT6366_MAX_REGULATOR;
+               mt6358_info = mt6366_regulators;
+               break;
+       default:
+               dev_err(&pdev->dev, "unsupported chip ID: %d\n", mt6397->chip_id);
+               return -EINVAL;
        }
 
        ret = mt6358_sync_vcn33_setting(&pdev->dev);