From: kernel test robot <lkp@intel.com>
To: "Kate Hsuan" <hpa@redhat.com>, "Pavel Machek" <pavel@ucw.cz>,
"Lee Jones" <lee@kernel.org>,
linux-leds@vger.kernel.org, platform-driver-x86@vger.kernel.org,
"Hans de Goede" <hdegoede@redhat.com>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"André Apitzsch" <git@apitzsch.eu>,
linux-kernel@vger.kernel.org,
"Andy Shevchenko" <andy.shevchenko@gmail.com>,
"Sebastian Reichel" <sre@kernel.org>,
linux-pm@vger.kernel.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Kate Hsuan <hpa@redhat.com>
Subject: Re: [PATCH v6 4/5] power: supply: power-supply-leds: Add charging_orange_full_green trigger for RGB LED
Date: Wed, 17 Apr 2024 07:27:50 +0800 [thread overview]
Message-ID: <202404170705.Or8MFKNi-lkp@intel.com> (raw)
In-Reply-To: <20240416053909.256319-5-hpa@redhat.com>
Hi Kate,
kernel test robot noticed the following build errors:
[auto build test ERROR on sre-power-supply/for-next]
[also build test ERROR on lee-leds/for-leds-next linus/master v6.9-rc4]
[cannot apply to next-20240416]
[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/Kate-Hsuan/platform-x86-android-tablets-other-Add-swnode-for-Xiaomi-pad2-indicator-LED/20240416-134240
base: https://git.kernel.org/pub/scm/linux/kernel/git/sre/linux-power-supply.git for-next
patch link: https://lore.kernel.org/r/20240416053909.256319-5-hpa%40redhat.com
patch subject: [PATCH v6 4/5] power: supply: power-supply-leds: Add charging_orange_full_green trigger for RGB LED
config: arm-defconfig (https://download.01.org/0day-ci/archive/20240417/202404170705.Or8MFKNi-lkp@intel.com/config)
compiler: clang version 14.0.6 (https://github.com/llvm/llvm-project.git f28c006a5895fc0e329fe15fead81e37457cb1d1)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240417/202404170705.Or8MFKNi-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/202404170705.Or8MFKNi-lkp@intel.com/
All errors (new ones prefixed by >>):
>> drivers/power/supply/power_supply_leds.c:42:3: error: implicit declaration of function 'led_mc_trigger_event' is invalid in C99 [-Werror,-Wimplicit-function-declaration]
led_mc_trigger_event(psy->charging_orange_full_green_trig,
^
drivers/power/supply/power_supply_leds.c:42:3: note: did you mean 'led_trigger_event'?
include/linux/leds.h:489:6: note: 'led_trigger_event' declared here
void led_trigger_event(struct led_trigger *trigger, enum led_brightness event);
^
1 error generated.
vim +/led_mc_trigger_event +42 drivers/power/supply/power_supply_leds.c
21
22 static void power_supply_update_bat_leds(struct power_supply *psy)
23 {
24 union power_supply_propval status;
25 unsigned int intensity_green[3] = {255, 0, 0};
26 unsigned int intensity_orange[3] = {128, 0, 255};
27 unsigned int intensity_red[3] = {0, 0, 255};
28
29 if (power_supply_get_property(psy, POWER_SUPPLY_PROP_STATUS, &status))
30 return;
31
32 dev_dbg(&psy->dev, "%s %d\n", __func__, status.intval);
33
34 switch (status.intval) {
35 case POWER_SUPPLY_STATUS_FULL:
36 led_trigger_event(psy->charging_full_trig, LED_FULL);
37 led_trigger_event(psy->charging_trig, LED_OFF);
38 led_trigger_event(psy->full_trig, LED_FULL);
39 /* Going from blink to LED on requires a LED_OFF event to stop blink */
40 led_trigger_event(psy->charging_blink_full_solid_trig, LED_OFF);
41 led_trigger_event(psy->charging_blink_full_solid_trig, LED_FULL);
> 42 led_mc_trigger_event(psy->charging_orange_full_green_trig,
43 intensity_green,
44 ARRAY_SIZE(intensity_green),
45 LED_FULL);
46 break;
47 case POWER_SUPPLY_STATUS_CHARGING:
48 led_trigger_event(psy->charging_full_trig, LED_FULL);
49 led_trigger_event(psy->charging_trig, LED_FULL);
50 led_trigger_event(psy->full_trig, LED_OFF);
51 led_trigger_blink(psy->charging_blink_full_solid_trig, 0, 0);
52 led_mc_trigger_event(psy->charging_orange_full_green_trig,
53 intensity_orange,
54 ARRAY_SIZE(intensity_orange),
55 LED_FULL);
56 break;
57 default:
58 led_trigger_event(psy->charging_full_trig, LED_OFF);
59 led_trigger_event(psy->charging_trig, LED_OFF);
60 led_trigger_event(psy->full_trig, LED_OFF);
61 led_trigger_event(psy->charging_blink_full_solid_trig,
62 LED_OFF);
63 led_mc_trigger_event(psy->charging_orange_full_green_trig,
64 intensity_red,
65 ARRAY_SIZE(intensity_red),
66 LED_OFF);
67 break;
68 }
69 }
70
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
parent reply other threads:[~2024-04-16 23:28 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20240416053909.256319-5-hpa@redhat.com>]
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=202404170705.Or8MFKNi-lkp@intel.com \
--to=lkp@intel.com \
--cc=andy.shevchenko@gmail.com \
--cc=git@apitzsch.eu \
--cc=hdegoede@redhat.com \
--cc=hpa@redhat.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pavel@ucw.cz \
--cc=platform-driver-x86@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox