From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Jishnu Prakash <jishnu.prakash@oss.qualcomm.com>,
Lee Jones <lee@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Guru Das Srinagesh <linux@gurudas.dev>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, mfd@lists.linux.dev,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Dhruvin Rajpura <drajpura@qti.qualcomm.com>,
Nihal Kumar Gupta <nihal.gupta@oss.qualcomm.com>,
Kamal Wadhwa <kamal.wadhwa@oss.qualcomm.com>,
Oleg Keri <okerixx@gmail.com>
Subject: Re: [PATCH v2 5/7] mfd: qcom-pm8008: Add PM8010 support
Date: Thu, 15 Oct 2026 14:04:40 +0200 [thread overview]
Message-ID: <a940a7e4-95c1-4207-91d0-6aa5e715c2c7@oss.qualcomm.com> (raw)
In-Reply-To: <20261014-pm8010_i2c_support-v2-5-b395d2b3f668@oss.qualcomm.com>
On 10/14/26 12:32 PM, Jishnu Prakash wrote:
> From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
>
> PM8010 is effectively the next generation of PM8008. The device is
> generally designed to serve the exact same function - power camera
> sensors and the associated supporting hardware.
[...]
> + pmic_type = (unsigned long)of_device_get_match_data(dev);
I don't understand why you changed my match_data_struct approach
here just to reconstruct the same data
Konrad
> +
> + switch (pmic_type) {
> + case TYPE_PM8008:
> + irq_chip_desc = &pm8008_irq_chip;
> + mfd_cells = pm8008_cells;
> + num_mfd_cells = ARRAY_SIZE(pm8008_cells);
> + break;
> + case TYPE_PM8010:
> + irq_chip_desc = &pm8010_irq_chip;
> + mfd_cells = pm8010_cells;
> + num_mfd_cells = ARRAY_SIZE(pm8010_cells);
> + break;
> + default:
> + dev_err(dev, "Unknown device type: %lu\n", pmic_type);
> + return -EINVAL;
> + }
> +
> dummy = devm_i2c_new_dummy_device(dev, client->adapter, client->addr + 1);
> if (IS_ERR(dummy)) {
> ret = PTR_ERR(dummy);
> @@ -233,19 +293,20 @@ static int pm8008_probe(struct i2c_client *client)
> return ret;
>
> ret = devm_regmap_add_irq_chip_fwnode(dev, fwnode, regmap, client->irq,
> - IRQF_SHARED, 0, &pm8008_irq_chip, &irq_data);
> + IRQF_SHARED, 0, irq_chip_desc, &irq_data);
> if (ret) {
> dev_err(dev, "failed to add IRQ chip: %d\n", ret);
> return ret;
> }
>
> - return devm_mfd_add_devices(dev, PLATFORM_DEVID_AUTO, pm8008_cells,
> - ARRAY_SIZE(pm8008_cells), NULL, 0,
> + return devm_mfd_add_devices(dev, PLATFORM_DEVID_AUTO, mfd_cells,
> + num_mfd_cells, NULL, 0,
> regmap_irq_get_domain(irq_data));
> }
>
> static const struct of_device_id pm8008_match[] = {
> - { .compatible = "qcom,pm8008", },
> + { .compatible = "qcom,pm8008", .data = (void *)TYPE_PM8008, },
> + { .compatible = "qcom,pm8010-i2c", .data = (void *)TYPE_PM8010, },
> { },
> };
> MODULE_DEVICE_TABLE(of, pm8008_match);
>
next prev parent reply other threads:[~2026-10-15 12:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-14 10:31 [PATCH v2 0/7] mfd: qcom-pm8008: Add support for PM8010 over I2C Jishnu Prakash
2026-10-14 10:31 ` [PATCH v2 1/7] dt-bindings: mfd: pm8008: Add qcom,pm8010-i2c compatible Jishnu Prakash
2026-10-14 10:31 ` [PATCH v2 2/7] regulator: pm8008: Add PM8010 support Jishnu Prakash
2026-10-14 10:32 ` [PATCH v2 3/7] regulator: qcom-pm8008: Add PM8010 mode support Jishnu Prakash
2026-10-14 10:32 ` [PATCH v2 4/7] mfd: qcom-pm8008: Drop GPIO support Jishnu Prakash
2026-10-15 12:01 ` Konrad Dybcio
2026-10-14 10:32 ` [PATCH v2 5/7] mfd: qcom-pm8008: Add PM8010 support Jishnu Prakash
2026-10-15 12:04 ` Konrad Dybcio [this message]
2026-10-14 10:32 ` [PATCH v2 6/7] dt-bindings: mfd: pm8008: Make interrupts optional Jishnu Prakash
2026-10-14 10:32 ` [PATCH v2 7/7] mfd: qcom-pm8008: Tolerate missing interrupt Jishnu Prakash
2026-10-15 11:00 ` Nihal Kumar Gupta
2026-10-15 12:05 ` Konrad Dybcio
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=a940a7e4-95c1-4207-91d0-6aa5e715c2c7@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=drajpura@qti.qualcomm.com \
--cc=jishnu.prakash@oss.qualcomm.com \
--cc=kamal.wadhwa@oss.qualcomm.com \
--cc=krzk+dt@kernel.org \
--cc=lee@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@gurudas.dev \
--cc=mfd@lists.linux.dev \
--cc=nihal.gupta@oss.qualcomm.com \
--cc=okerixx@gmail.com \
--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
all inboxes | Powered by JetHome®