All of lore.kernel.org
 help / color / mirror / Atom feed
* [PATCH v7 0/9] Add support MT6316/6363/MT6373 PMICs regulators and MFD
@ 2025-10-02  9:00 AngeloGioacchino Del Regno
  2025-10-02  9:00 ` [PATCH v7 1/9] dt-bindings: regulator: Document MediaTek MT6316 PMIC Regulators AngeloGioacchino Del Regno
                   ` (8 more replies)
  0 siblings, 9 replies; 13+ messages in thread
From: AngeloGioacchino Del Regno @ 2025-10-02  9:00 UTC (permalink / raw)
  To: linux-mediatek
  Cc: lee, robh, krzk+dt, conor+dt, matthias.bgg,
	angelogioacchino.delregno, lgirdwood, broonie, devicetree,
	linux-kernel, linux-arm-kernel, kernel, wenst, igor.belwon

Changes in v7:
 - Removed unintentionally added, useless Link tags from all patches
 - #size-cells is now required in mfd mt6363 binding
 - Further fixes in mt6363/73 regulator bindings
 - Mentioned weird 9-bits BE format and usage of undocumented set/clr
   registers in commit description for the MT6316 regulator driver
 - Refactored bindings for MT6316 PMIC (regulators):
   - Added reg, #address-cells as required properties
   - Added regulator-allowed-modes and its description
   - Changed mt6316b/mt6316c to use patternProperties instead, as it
     now makes sense to avoid duplication while keeping documentation
     for the regulator-allowed-modes property in all vbuck entries
   - Added decent examples that correctly describes the MT6316 PMICs

Changes in v6:
 - Added missing bitfield.h header inclusion in mt6363-regulator.c
 - Added commit "dt-bindings: iio: adc: mt6359: Allow reg for SPMI PMICs AuxADC"
   to fix warnings on specifying reg property in adc node
 - Added $ref in mt6363/73 regulator bindings to reduce duplication on LDOs
 - Moved MT6363 regulators example to MFD binding
 - Rebased on next-20250929

Changes in v5:
 - This time the dt-bindings commits are the right ones... sorry again :-)
 - Removed accidentally added Link: tags in all patches.

Changes in v4:
 - Rewritten all register definitions for both MT6363 and MT6373
   regulators to be register offsets instead
 - Added the appropriate supply_name to all vregs in 6363 and 6373
 - Simplified the macro parameters for all vregs in 6363 and 6373
   - Added common definitions pattern in macros to avoid plain writing
     register definitions in every macro call
 - Added registration of SPMI sub-device in MT6363/73 and setup of
   regmap reg_base based on `reg` parsed from devicetree
 - Removed interrupts parsing from devicetree
   - Moved (pmic-internal) IRQs to macros
 - mtk-spmi-pmic: Added parsing if irqspec with param_count=2 for
   easier irqs registration from regulator drivers

Changes in v3:
 - Added buck and ldo supplies to mt6363 and mt6373 drivers and bindings;
 - Removed interrupts from mt6363 and mt6373 bindings;
 - Added registering interrupts in mt6363/73 drivers instead:
   this avoids big arrays in the mfd driver, which will grow
   uncontrollably (as it already happened in multiple MediaTek
   drivers) and with each new(future) supported PMIC;
 - Removed "ldo-" and "buck-" prefixes from mt6363 regulators
   - Renamed "vbX" to "vbuckX", reflecting datasheet name
 - Changed all LDOs in MT6363 and MT6373 to add VOCAL usage, both
   increasing the number of voltage steps (2.5 or 10mV increments
   depending on the LDO) and the accuracy of the reported voltages
 - Tested again on MT8196 board

Changes in v2:
 - Merged MFD and regulator in one series
 - Split mediatek,mt6316-regulator.yaml in three files as
   suggested by krzk
 - Added interrupt-names list in MT6363/MT6373 bindings as
   suggested by krzk
 - Documented regulator modes in MT6363/73 as suggested by krzk
 - Fixed interrupt and interrupt-names maxItems in both 6363/73
   because, well... I miscounted them in v1 :-)
 - Removed keys from mt6363 binding: the compatible was not yet
   added to the keys binding and doing that will take quite a
   while, as I have to find a way to test the code before that
   as unfortunately my HW does not provide any way to test the
   PMIC keys (thought it did, but then turns out it doesn't...)
 - Completed the mt6363 MFD example with ADC as suggested by Rob
 - Avoided applying regulator schemas multiple times as pointed
   out by Rob (in mfd binding)
 - Fixed MT6363/73 issues pointed out by lkp (eh, sorry, that
   happened during a last minute cleanup... ugh!).
 - Brewed some more coffee :-)


This series adds support for three new MediaTek PMICs: MT6316, MT6363
and MT6373 and their variants - used in board designs featuring the
MediaTek MT8196 Chromebook SoC, or the MT6991 Dimensity 9400 Smartphone
SoC.

In particular, MT6316 is a regulator, but the MT6363 and MT6373 PMICs
are multi-function devices, as they have and expose multiple sub-devices;
moreover, some of those also contain an interrupt controller, managing
internal IPs interrupts: for those, a chained interrupt handler is
registered, which parent is the SPMI controller itself.

This series adds support for all of the MT6316 regulator variants and
for MT6363, MT6373 SPMI PMICs and their interrupt controller.


AngeloGioacchino Del Regno (9):
  dt-bindings: regulator: Document MediaTek MT6316 PMIC Regulators
  regulator: Add support for MediaTek MT6316 SPMI PMIC Regulators
  dt-bindings: regulator: Document MediaTek MT6363 PMIC Regulators
  regulator: Add support for MediaTek MT6363 SPMI PMIC Regulators
  dt-bindings: regulator: Document MediaTek MT6373 PMIC Regulators
  regulator: Add support for MediaTek MT6373 SPMI PMIC Regulators
  dt-bindings: iio: adc: mt6359: Allow reg for SPMI PMICs AuxADC
  dt-bindings: mfd: Add binding for MediaTek MT6363 series SPMI PMIC
  drivers: mfd: Add support for MediaTek SPMI PMICs and MT6363/73

 .../iio/adc/mediatek,mt6359-auxadc.yaml       |  17 +
 .../bindings/mfd/mediatek,mt6363.yaml         | 116 +++
 .../regulator/mediatek,mt6316b-regulator.yaml |  80 ++
 .../regulator/mediatek,mt6316c-regulator.yaml |  80 ++
 .../regulator/mediatek,mt6316d-regulator.yaml |  79 ++
 .../regulator/mediatek,mt6363-regulator.yaml  | 146 +++
 .../regulator/mediatek,mt6373-regulator.yaml  | 137 +++
 drivers/mfd/Kconfig                           |  17 +
 drivers/mfd/Makefile                          |   1 +
 drivers/mfd/mtk-spmi-pmic.c                   | 410 ++++++++
 drivers/regulator/Kconfig                     |  27 +
 drivers/regulator/Makefile                    |   3 +
 drivers/regulator/mt6316-regulator.c          | 345 +++++++
 drivers/regulator/mt6363-regulator.c          | 935 ++++++++++++++++++
 drivers/regulator/mt6373-regulator.c          | 762 ++++++++++++++
 include/linux/mfd/mt6363.h                    |  26 +
 include/linux/mfd/mt6373.h                    |  21 +
 include/linux/regulator/mt6363-regulator.h    | 331 +++++++
 include/linux/regulator/mt6373-regulator.h    | 162 +++
 19 files changed, 3695 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/mfd/mediatek,mt6363.yaml
 create mode 100644 Documentation/devicetree/bindings/regulator/mediatek,mt6316b-regulator.yaml
 create mode 100644 Documentation/devicetree/bindings/regulator/mediatek,mt6316c-regulator.yaml
 create mode 100644 Documentation/devicetree/bindings/regulator/mediatek,mt6316d-regulator.yaml
 create mode 100644 Documentation/devicetree/bindings/regulator/mediatek,mt6363-regulator.yaml
 create mode 100644 Documentation/devicetree/bindings/regulator/mediatek,mt6373-regulator.yaml
 create mode 100644 drivers/mfd/mtk-spmi-pmic.c
 create mode 100644 drivers/regulator/mt6316-regulator.c
 create mode 100644 drivers/regulator/mt6363-regulator.c
 create mode 100644 drivers/regulator/mt6373-regulator.c
 create mode 100644 include/linux/mfd/mt6363.h
 create mode 100644 include/linux/mfd/mt6373.h
 create mode 100644 include/linux/regulator/mt6363-regulator.h
 create mode 100644 include/linux/regulator/mt6373-regulator.h

-- 
2.51.0



^ permalink raw reply	[flat|nested] 13+ messages in thread
* Re: [PATCH v7 6/9] regulator: Add support for MediaTek MT6373 SPMI PMIC Regulators
  2025-10-02  9:00 ` [PATCH v7 6/9] regulator: Add support for MediaTek MT6373 SPMI " AngeloGioacchino Del Regno
@ 2025-10-03  8:36 ` Dan Carpenter
  -1 siblings, 0 replies; 13+ messages in thread
From: kernel test robot @ 2025-10-03  2:12 UTC (permalink / raw)
  To: oe-kbuild; +Cc: lkp, Dan Carpenter

BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
In-Reply-To: <20251002090028.1796462-7-angelogioacchino.delregno@collabora.com>
References: <20251002090028.1796462-7-angelogioacchino.delregno@collabora.com>
TO: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
TO: linux-mediatek@lists.infradead.org
CC: lee@kernel.org
CC: robh@kernel.org
CC: krzk+dt@kernel.org
CC: conor+dt@kernel.org
CC: matthias.bgg@gmail.com
CC: angelogioacchino.delregno@collabora.com
CC: lgirdwood@gmail.com
CC: broonie@kernel.org
CC: devicetree@vger.kernel.org
CC: linux-kernel@vger.kernel.org
CC: linux-arm-kernel@lists.infradead.org
CC: kernel@collabora.com
CC: wenst@chromium.org
CC: igor.belwon@mentallysanemainliners.org

Hi AngeloGioacchino,

kernel test robot noticed the following build warnings:

[auto build test WARNING on broonie-regulator/for-next]
[also build test WARNING on lee-mfd/for-mfd-next jic23-iio/togreg lee-leds/for-leds-next lee-mfd/for-mfd-fixes linus/master v6.17 next-20251002]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]

url:    https://github.com/intel-lab-lkp/linux/commits/AngeloGioacchino-Del-Regno/dt-bindings-regulator-Document-MediaTek-MT6316-PMIC-Regulators/20251002-170532
base:   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next
patch link:    https://lore.kernel.org/r/20251002090028.1796462-7-angelogioacchino.delregno%40collabora.com
patch subject: [PATCH v7 6/9] regulator: Add support for MediaTek MT6373 SPMI PMIC Regulators
:::::: branch date: 17 hours ago
:::::: commit date: 17 hours ago
config: arm-randconfig-r071-20251003 (https://download.01.org/0day-ci/archive/20251003/202510030902.aQS5rL8n-lkp@intel.com/config)
compiler: arm-linux-gnueabi-gcc (GCC) 8.5.0

If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Reported-by: Dan Carpenter <error27@gmail.com>
| Closes: https://lore.kernel.org/r/202510030902.aQS5rL8n-lkp@intel.com/

smatch warnings:
drivers/regulator/mt6373-regulator.c:664 mt6373_regulator_probe() warn: passing zero to 'PTR_ERR'

vim +/PTR_ERR +664 drivers/regulator/mt6373-regulator.c

910ce1c7c9122a AngeloGioacchino Del Regno 2025-10-02  644  
910ce1c7c9122a AngeloGioacchino Del Regno 2025-10-02  645  static int mt6373_regulator_probe(struct platform_device *pdev)
910ce1c7c9122a AngeloGioacchino Del Regno 2025-10-02  646  {
910ce1c7c9122a AngeloGioacchino Del Regno 2025-10-02  647  	struct irq_fwspec fwspec = {
910ce1c7c9122a AngeloGioacchino Del Regno 2025-10-02  648  		.param_count = 2,
910ce1c7c9122a AngeloGioacchino Del Regno 2025-10-02  649  		.param = { 0, IRQ_TYPE_LEVEL_HIGH },
910ce1c7c9122a AngeloGioacchino Del Regno 2025-10-02  650  	};
910ce1c7c9122a AngeloGioacchino Del Regno 2025-10-02  651  	struct device_node *interrupt_parent;
910ce1c7c9122a AngeloGioacchino Del Regno 2025-10-02  652  	struct regulator_config config = {};
910ce1c7c9122a AngeloGioacchino Del Regno 2025-10-02  653  	struct mt6373_regulator_info *info;
910ce1c7c9122a AngeloGioacchino Del Regno 2025-10-02  654  	struct device *dev = &pdev->dev;
910ce1c7c9122a AngeloGioacchino Del Regno 2025-10-02  655  	struct regulator_dev *rdev;
910ce1c7c9122a AngeloGioacchino Del Regno 2025-10-02  656  	struct irq_domain *domain;
910ce1c7c9122a AngeloGioacchino Del Regno 2025-10-02  657  	bool is_vbuck4_hw_ctrl;
910ce1c7c9122a AngeloGioacchino Del Regno 2025-10-02  658  	bool is_cw_variant;
910ce1c7c9122a AngeloGioacchino Del Regno 2025-10-02  659  	int i, ret;
910ce1c7c9122a AngeloGioacchino Del Regno 2025-10-02  660  	u32 val;
910ce1c7c9122a AngeloGioacchino Del Regno 2025-10-02  661  
910ce1c7c9122a AngeloGioacchino Del Regno 2025-10-02  662  	config.regmap = mt6373_spmi_register_regmap(dev);
910ce1c7c9122a AngeloGioacchino Del Regno 2025-10-02  663  	if (!config.regmap)
910ce1c7c9122a AngeloGioacchino Del Regno 2025-10-02 @664  		return dev_err_probe(dev, PTR_ERR(config.regmap),
910ce1c7c9122a AngeloGioacchino Del Regno 2025-10-02  665  				     "Cannot get regmap\n");
910ce1c7c9122a AngeloGioacchino Del Regno 2025-10-02  666  	config.dev = dev;
910ce1c7c9122a AngeloGioacchino Del Regno 2025-10-02  667  
910ce1c7c9122a AngeloGioacchino Del Regno 2025-10-02  668  	interrupt_parent = of_irq_find_parent(dev->of_node);
910ce1c7c9122a AngeloGioacchino Del Regno 2025-10-02  669  	if (!interrupt_parent)
910ce1c7c9122a AngeloGioacchino Del Regno 2025-10-02  670  		return -EINVAL;
910ce1c7c9122a AngeloGioacchino Del Regno 2025-10-02  671  
910ce1c7c9122a AngeloGioacchino Del Regno 2025-10-02  672  	domain = irq_find_host(interrupt_parent);
910ce1c7c9122a AngeloGioacchino Del Regno 2025-10-02  673  	of_node_put(interrupt_parent);
910ce1c7c9122a AngeloGioacchino Del Regno 2025-10-02  674  	fwspec.fwnode = domain->fwnode;
910ce1c7c9122a AngeloGioacchino Del Regno 2025-10-02  675  
910ce1c7c9122a AngeloGioacchino Del Regno 2025-10-02  676  	/* Read PMIC variant information */
910ce1c7c9122a AngeloGioacchino Del Regno 2025-10-02  677  	ret = regmap_read(config.regmap, MT6373_PLG_CFG_ELR1, &val);
910ce1c7c9122a AngeloGioacchino Del Regno 2025-10-02  678  	if (ret)
910ce1c7c9122a AngeloGioacchino Del Regno 2025-10-02  679  		return dev_err_probe(dev, ret, "Cannot read ID register\n");
910ce1c7c9122a AngeloGioacchino Del Regno 2025-10-02  680  
910ce1c7c9122a AngeloGioacchino Del Regno 2025-10-02  681  	val = FIELD_GET(MT6373_ELR_VARIANT_MASK, val);
910ce1c7c9122a AngeloGioacchino Del Regno 2025-10-02  682  	is_cw_variant = (val == MT6373_ELR_VARIANT_MT6373CW);
910ce1c7c9122a AngeloGioacchino Del Regno 2025-10-02  683  
910ce1c7c9122a AngeloGioacchino Del Regno 2025-10-02  684  	/* Read Reserved-SW information */
910ce1c7c9122a AngeloGioacchino Del Regno 2025-10-02  685  	ret = regmap_read(config.regmap, MT6373_RG_RSV_SWREG_H, &val);
910ce1c7c9122a AngeloGioacchino Del Regno 2025-10-02  686  	if (ret)
910ce1c7c9122a AngeloGioacchino Del Regno 2025-10-02  687  		return dev_err_probe(dev, ret, "Cannot read RSV_SW register\n");
910ce1c7c9122a AngeloGioacchino Del Regno 2025-10-02  688  
910ce1c7c9122a AngeloGioacchino Del Regno 2025-10-02  689  	is_vbuck4_hw_ctrl = val & MT6373_RG_RSV_SWREG_VBUCK4_HW_CTRL;
910ce1c7c9122a AngeloGioacchino Del Regno 2025-10-02  690  
910ce1c7c9122a AngeloGioacchino Del Regno 2025-10-02  691  	for (i = 0; i < ARRAY_SIZE(mt6373_regulators); i++) {
910ce1c7c9122a AngeloGioacchino Del Regno 2025-10-02  692  		info = &mt6373_regulators[i];
910ce1c7c9122a AngeloGioacchino Del Regno 2025-10-02  693  
910ce1c7c9122a AngeloGioacchino Del Regno 2025-10-02  694  		/* MT6373CW VBUCK4 constraints are different */
910ce1c7c9122a AngeloGioacchino Del Regno 2025-10-02  695  		if (info->desc.id == MT6373_ID_VBUCK4) {
910ce1c7c9122a AngeloGioacchino Del Regno 2025-10-02  696  			unsigned int vbuck4_max_uV;
910ce1c7c9122a AngeloGioacchino Del Regno 2025-10-02  697  
910ce1c7c9122a AngeloGioacchino Del Regno 2025-10-02  698  			/* VBUCK4 vreg software control not allowed in hw_ctrl mode */
910ce1c7c9122a AngeloGioacchino Del Regno 2025-10-02  699  			if (is_vbuck4_hw_ctrl)
910ce1c7c9122a AngeloGioacchino Del Regno 2025-10-02  700  				continue;
910ce1c7c9122a AngeloGioacchino Del Regno 2025-10-02  701  
910ce1c7c9122a AngeloGioacchino Del Regno 2025-10-02  702  			if (is_cw_variant) {
910ce1c7c9122a AngeloGioacchino Del Regno 2025-10-02  703  				info->desc.uV_step = 6250;
910ce1c7c9122a AngeloGioacchino Del Regno 2025-10-02  704  				vbuck4_max_uV = 1193750;
910ce1c7c9122a AngeloGioacchino Del Regno 2025-10-02  705  			} else {
910ce1c7c9122a AngeloGioacchino Del Regno 2025-10-02  706  				info->desc.uV_step = 13875;
910ce1c7c9122a AngeloGioacchino Del Regno 2025-10-02  707  				vbuck4_max_uV = 2650125;
910ce1c7c9122a AngeloGioacchino Del Regno 2025-10-02  708  			}
910ce1c7c9122a AngeloGioacchino Del Regno 2025-10-02  709  			info->desc.n_voltages = vbuck4_max_uV / info->desc.uV_step + 1;
910ce1c7c9122a AngeloGioacchino Del Regno 2025-10-02  710  		}
910ce1c7c9122a AngeloGioacchino Del Regno 2025-10-02  711  
910ce1c7c9122a AngeloGioacchino Del Regno 2025-10-02  712  		fwspec.param[0] = info->hwirq;
910ce1c7c9122a AngeloGioacchino Del Regno 2025-10-02  713  		info->virq = irq_create_fwspec_mapping(&fwspec);
910ce1c7c9122a AngeloGioacchino Del Regno 2025-10-02  714  		if (!info->virq)
910ce1c7c9122a AngeloGioacchino Del Regno 2025-10-02  715  			return dev_err_probe(dev, -EINVAL,
910ce1c7c9122a AngeloGioacchino Del Regno 2025-10-02  716  					     "Failed to map IRQ%d\n", info->hwirq);
910ce1c7c9122a AngeloGioacchino Del Regno 2025-10-02  717  
910ce1c7c9122a AngeloGioacchino Del Regno 2025-10-02  718  		ret = devm_add_action_or_reset(dev, mt6373_irq_remove, &info->virq);
910ce1c7c9122a AngeloGioacchino Del Regno 2025-10-02  719  		if (ret) {
910ce1c7c9122a AngeloGioacchino Del Regno 2025-10-02  720  			irq_dispose_mapping(info->virq);
910ce1c7c9122a AngeloGioacchino Del Regno 2025-10-02  721  			return ret;
910ce1c7c9122a AngeloGioacchino Del Regno 2025-10-02  722  		}
910ce1c7c9122a AngeloGioacchino Del Regno 2025-10-02  723  
910ce1c7c9122a AngeloGioacchino Del Regno 2025-10-02  724  		config.driver_data = info;
910ce1c7c9122a AngeloGioacchino Del Regno 2025-10-02  725  		INIT_DELAYED_WORK(&info->oc_work, mt6373_oc_irq_enable_work);
910ce1c7c9122a AngeloGioacchino Del Regno 2025-10-02  726  
910ce1c7c9122a AngeloGioacchino Del Regno 2025-10-02  727  		rdev = devm_regulator_register(dev, &info->desc, &config);
910ce1c7c9122a AngeloGioacchino Del Regno 2025-10-02  728  		if (IS_ERR(rdev))
910ce1c7c9122a AngeloGioacchino Del Regno 2025-10-02  729  			return dev_err_probe(dev, PTR_ERR(rdev),
910ce1c7c9122a AngeloGioacchino Del Regno 2025-10-02  730  					     "failed to register %s\n", info->desc.name);
910ce1c7c9122a AngeloGioacchino Del Regno 2025-10-02  731  	}
910ce1c7c9122a AngeloGioacchino Del Regno 2025-10-02  732  	dev_set_drvdata(dev, config.regmap);
910ce1c7c9122a AngeloGioacchino Del Regno 2025-10-02  733  
910ce1c7c9122a AngeloGioacchino Del Regno 2025-10-02  734  	return 0;
910ce1c7c9122a AngeloGioacchino Del Regno 2025-10-02  735  }
910ce1c7c9122a AngeloGioacchino Del Regno 2025-10-02  736  

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

^ permalink raw reply	[flat|nested] 13+ messages in thread

end of thread, other threads:[~2025-10-03  8:36 UTC | newest]

Thread overview: 13+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2025-10-02  9:00 [PATCH v7 0/9] Add support MT6316/6363/MT6373 PMICs regulators and MFD AngeloGioacchino Del Regno
2025-10-02  9:00 ` [PATCH v7 1/9] dt-bindings: regulator: Document MediaTek MT6316 PMIC Regulators AngeloGioacchino Del Regno
2025-10-02  9:00 ` [PATCH v7 2/9] regulator: Add support for MediaTek MT6316 SPMI " AngeloGioacchino Del Regno
2025-10-02  9:00 ` [PATCH v7 3/9] dt-bindings: regulator: Document MediaTek MT6363 " AngeloGioacchino Del Regno
2025-10-02  9:00 ` [PATCH v7 4/9] regulator: Add support for MediaTek MT6363 SPMI " AngeloGioacchino Del Regno
2025-10-03  6:38   ` kernel test robot
2025-10-02  9:00 ` [PATCH v7 5/9] dt-bindings: regulator: Document MediaTek MT6373 " AngeloGioacchino Del Regno
2025-10-02  9:00 ` [PATCH v7 6/9] regulator: Add support for MediaTek MT6373 SPMI " AngeloGioacchino Del Regno
2025-10-02  9:00 ` [PATCH v7 7/9] dt-bindings: iio: adc: mt6359: Allow reg for SPMI PMICs AuxADC AngeloGioacchino Del Regno
2025-10-02  9:00 ` [PATCH v7 8/9] dt-bindings: mfd: Add binding for MediaTek MT6363 series SPMI PMIC AngeloGioacchino Del Regno
2025-10-02  9:00 ` [PATCH v7 9/9] drivers: mfd: Add support for MediaTek SPMI PMICs and MT6363/73 AngeloGioacchino Del Regno
  -- strict thread matches above, loose matches on Subject: below --
2025-10-03  2:12 [PATCH v7 6/9] regulator: Add support for MediaTek MT6373 SPMI PMIC Regulators kernel test robot
2025-10-03  8:36 ` Dan Carpenter

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.