From: kernel test robot <lkp@intel.com>
To: cy_huang@richtek.com, Sebastian Reichel <sre@kernel.org>,
Krzysztof Kozlowski <krzk@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev, Rob Herring <robh@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
ChiYuan Huang <cy_huang@richtek.com>,
devicetree@vger.kernel.org, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 2/3] power: supply: rt9756: Add Richtek RT9756 smart cap divider charger
Date: Fri, 31 Oct 2025 05:17:28 +0800 [thread overview]
Message-ID: <202510310457.iAWJdDLC-lkp@intel.com> (raw)
In-Reply-To: <5eab51e111b092329519dd2c200858a522780626.1761699952.git.cy_huang@richtek.com>
Hi,
kernel test robot noticed the following build warnings:
[auto build test WARNING on sre-power-supply/for-next]
[also build test WARNING on krzk-dt/for-next robh/for-next linus/master v6.18-rc3 next-20251030]
[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/cy_huang-richtek-com/dt-bindings-power-supply-Add-Richtek-RT9756-smart-cap-divider-charger/20251029-091554
base: https://git.kernel.org/pub/scm/linux/kernel/git/sre/linux-power-supply.git for-next
patch link: https://lore.kernel.org/r/5eab51e111b092329519dd2c200858a522780626.1761699952.git.cy_huang%40richtek.com
patch subject: [PATCH v3 2/3] power: supply: rt9756: Add Richtek RT9756 smart cap divider charger
config: nios2-randconfig-r112-20251031 (https://download.01.org/0day-ci/archive/20251031/202510310457.iAWJdDLC-lkp@intel.com/config)
compiler: nios2-linux-gcc (GCC) 9.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251031/202510310457.iAWJdDLC-lkp@intel.com/reproduce)
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>
| Closes: https://lore.kernel.org/oe-kbuild-all/202510310457.iAWJdDLC-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/power/supply/rt9756.c:645:41: sparse: sparse: incorrect type in argument 2 (different base types) @@ expected unsigned int [usertype] size @@ got restricted gfp_t @@
drivers/power/supply/rt9756.c:645:41: sparse: expected unsigned int [usertype] size
drivers/power/supply/rt9756.c:645:41: sparse: got restricted gfp_t
>> drivers/power/supply/rt9756.c:645:53: sparse: sparse: incorrect type in argument 3 (different base types) @@ expected restricted gfp_t [usertype] gfp @@ got unsigned int @@
drivers/power/supply/rt9756.c:645:53: sparse: expected restricted gfp_t [usertype] gfp
drivers/power/supply/rt9756.c:645:53: sparse: got unsigned int
drivers/power/supply/rt9756.c: note: in included file (through include/uapi/linux/swab.h, include/linux/swab.h, include/uapi/linux/byteorder/little_endian.h, ...):
arch/nios2/include/uapi/asm/swab.h:25:24: sparse: sparse: too many arguments for function __builtin_custom_ini
vim +645 drivers/power/supply/rt9756.c
619
620 static int rt9756_register_psy(struct rt9756_data *data)
621 {
622 struct power_supply_desc *desc = &data->psy_desc;
623 struct power_supply_desc *bat_desc = &data->bat_psy_desc;
624 struct power_supply_config cfg = {}, bat_cfg = {};
625 struct device *dev = data->dev;
626 char *psy_name, *bat_psy_name, **supplied_to;
627
628 bat_cfg.drv_data = data;
629 bat_cfg.fwnode = dev_fwnode(dev);
630
631 bat_psy_name = devm_kasprintf(dev, GFP_KERNEL, "rt9756-%s-battery", dev_name(dev));
632 if (!bat_psy_name)
633 return -ENOMEM;
634
635 bat_desc->name = bat_psy_name;
636 bat_desc->type = POWER_SUPPLY_TYPE_BATTERY;
637 bat_desc->properties = rt9756_bat_psy_properties;
638 bat_desc->num_properties = ARRAY_SIZE(rt9756_bat_psy_properties);
639 bat_desc->get_property = rt9756_bat_psy_get_property;
640
641 data->bat_psy = devm_power_supply_register(dev, bat_desc, &bat_cfg);
642 if (IS_ERR(data->bat_psy))
643 return dev_err_probe(dev, PTR_ERR(data->bat_psy), "Failed to register battery\n");
644
> 645 supplied_to = devm_kzalloc(dev, GFP_KERNEL, sizeof(*supplied_to));
646 if (!supplied_to)
647 return -ENOMEM;
648
649 /* Link charger psy to battery psy */
650 supplied_to[0] = bat_psy_name;
651
652 cfg.drv_data = data;
653 cfg.fwnode = dev_fwnode(dev);
654 cfg.attr_grp = rt9756_sysfs_groups;
655 cfg.supplied_to = supplied_to;
656 cfg.num_supplicants = 1;
657
658 psy_name = devm_kasprintf(dev, GFP_KERNEL, "rt9756-%s", dev_name(dev));
659 if (!psy_name)
660 return -ENOMEM;
661
662 desc->name = psy_name;
663 desc->type = POWER_SUPPLY_TYPE_USB;
664 desc->usb_types = BIT(POWER_SUPPLY_USB_TYPE_UNKNOWN) | BIT(POWER_SUPPLY_USB_TYPE_SDP) |
665 BIT(POWER_SUPPLY_USB_TYPE_DCP) | BIT(POWER_SUPPLY_USB_TYPE_CDP);
666 desc->properties = rt9756_psy_properties;
667 desc->num_properties = ARRAY_SIZE(rt9756_psy_properties);
668 desc->property_is_writeable = rt9756_psy_property_is_writeable;
669 desc->get_property = rt9756_psy_get_property;
670 desc->set_property = rt9756_psy_set_property;
671
672 data->psy = devm_power_supply_register(dev, desc, &cfg);
673
674 return PTR_ERR_OR_ZERO(data->psy);
675 }
676
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-10-30 21:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-29 1:14 [PATCH v3 0/3] Add Richtek RT9756 Smart-Cap divider charger cy_huang
2025-10-29 1:14 ` [PATCH v3 1/3] dt-bindings: power: supply: Add Richtek RT9756 smart cap " cy_huang
2025-10-29 1:14 ` [PATCH v3 2/3] power: supply: rt9756: " cy_huang
2025-10-30 21:17 ` kernel test robot [this message]
2025-10-30 23:11 ` kernel test robot
2025-10-29 1:14 ` [PATCH v3 3/3] Documentation: power: rt9756: Document exported sysfs entries cy_huang
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=202510310457.iAWJdDLC-lkp@intel.com \
--to=lkp@intel.com \
--cc=conor+dt@kernel.org \
--cc=cy_huang@richtek.com \
--cc=devicetree@vger.kernel.org \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=robh@kernel.org \
--cc=sre@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 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.