From: kernel test robot <lkp@intel.com>
To: Andrea Tomassetti <andrea.tomassetti@sipearl.com>,
sudeep.holla@arm.com, jassisinghbrar@gmail.com,
rafael@kernel.org
Cc: oe-kbuild-all@lists.linux.dev,
Andrea Tomassetti <andrea.tomassetti@sipearl.com>,
lenb@kernel.org, linux-acpi@vger.kernel.org,
linux-kernel@vger.kernel.org, olivierdautricourt@gmail.com,
Thibault Cantori <thibault.cantori@sipearl.com>,
Olivier Dautricourt <olivier.dautricourt@sipearl.com>
Subject: Re: [PATCH] mailbox: pcc: support polling mode when there is no platform IRQ
Date: Wed, 12 Nov 2025 08:07:20 +0800 [thread overview]
Message-ID: <202511120729.R3XQNSnx-lkp@intel.com> (raw)
In-Reply-To: <20251110150825.3548819-1-andrea.tomassetti@sipearl.com>
Hi Andrea,
kernel test robot noticed the following build errors:
[auto build test ERROR on rafael-pm/linux-next]
[also build test ERROR on rafael-pm/bleeding-edge jassibrar-mailbox/for-next linus/master v6.18-rc5 next-20251111]
[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/Andrea-Tomassetti/mailbox-pcc-support-polling-mode-when-there-is-no-platform-IRQ/20251110-232950
base: https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git linux-next
patch link: https://lore.kernel.org/r/20251110150825.3548819-1-andrea.tomassetti%40sipearl.com
patch subject: [PATCH] mailbox: pcc: support polling mode when there is no platform IRQ
config: i386-buildonly-randconfig-002-20251112 (https://download.01.org/0day-ci/archive/20251112/202511120729.R3XQNSnx-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251112/202511120729.R3XQNSnx-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/202511120729.R3XQNSnx-lkp@intel.com/
All errors (new ones prefixed by >>):
ld: drivers/acpi/acpi_pcc.o: in function `acpi_pcc_address_space_handler':
>> drivers/acpi/acpi_pcc.c:148:(.text+0x7e): undefined reference to `__udivdi3'
Kconfig warnings: (for reference only)
WARNING: unmet direct dependencies detected for OF_GPIO
Depends on [n]: GPIOLIB [=y] && OF [=n] && HAS_IOMEM [=y]
Selected by [y]:
- GPIO_TB10X [=y] && GPIOLIB [=y] && HAS_IOMEM [=y] && (ARC_PLAT_TB10X || COMPILE_TEST [=y])
WARNING: unmet direct dependencies detected for GPIO_SYSCON
Depends on [n]: GPIOLIB [=y] && HAS_IOMEM [=y] && MFD_SYSCON [=y] && OF [=n]
Selected by [m]:
- GPIO_SAMA5D2_PIOBU [=m] && GPIOLIB [=y] && HAS_IOMEM [=y] && MFD_SYSCON [=y] && OF_GPIO [=y] && (ARCH_AT91 || COMPILE_TEST [=y])
WARNING: unmet direct dependencies detected for I2C_K1
Depends on [n]: I2C [=y] && HAS_IOMEM [=y] && (ARCH_SPACEMIT || COMPILE_TEST [=y]) && OF [=n]
Selected by [m]:
- MFD_SPACEMIT_P1 [=m] && HAS_IOMEM [=y] && (ARCH_SPACEMIT || COMPILE_TEST [=y]) && I2C [=y]
vim +148 drivers/acpi/acpi_pcc.c
124
125 static acpi_status
126 acpi_pcc_address_space_handler(u32 function, acpi_physical_address addr,
127 u32 bits, acpi_integer *value,
128 void *handler_context, void *region_context)
129 {
130 acpi_status ret;
131 struct pcc_data *data = region_context;
132 u64 usecs_lat;
133 bool use_polling = data->pcc_chan->mchan->mbox->txdone_poll;
134
135 reinit_completion(&data->done);
136
137 /* Write to Shared Memory */
138 memcpy_toio(data->pcc_chan->shmem, (void *)value, data->ctx.length);
139
140 /*
141 * pcc_chan->latency is just a Nominal value. In reality the remote
142 * processor could be much slower to reply. So add an arbitrary
143 * amount of wait on top of Nominal.
144 */
145 usecs_lat = PCC_CMD_WAIT_RETRIES_NUM * data->pcc_chan->latency;
146
147 data->cl.tx_block = use_polling;
> 148 data->cl.tx_tout = usecs_lat / USEC_PER_MSEC;
149
150 if (use_polling)
151 ret = acpi_pcc_send_msg_polling(data);
152 else
153 ret = acpi_pcc_send_msg_irq(data);
154
155 memcpy_fromio(value, data->pcc_chan->shmem, data->ctx.length);
156
157 return ret;
158 }
159
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-11-12 0:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-10 15:08 [PATCH] mailbox: pcc: support polling mode when there is no platform IRQ Andrea Tomassetti
2025-11-11 18:29 ` kernel test robot
2025-11-11 21:47 ` kernel test robot
2025-11-12 0:07 ` kernel test robot [this message]
2025-11-19 9:01 ` [PATCH v2] " Andrea Tomassetti
2025-11-27 14:51 ` Sudeep Holla
2025-12-02 10:12 ` [PATCH v3 1/2] " Andrea Tomassetti
2025-12-03 10:28 ` Sudeep Holla
2025-12-04 12:59 ` Andrea Tomassetti
2025-12-04 13:14 ` Sudeep Holla
2025-12-09 10:39 ` Andrea Tomassetti
2025-12-09 11:11 ` Sudeep Holla
2025-12-02 10:12 ` [PATCH v3 2/2] mailbox: pcc: add peek_data handler Andrea Tomassetti
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=202511120729.R3XQNSnx-lkp@intel.com \
--to=lkp@intel.com \
--cc=andrea.tomassetti@sipearl.com \
--cc=jassisinghbrar@gmail.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=olivier.dautricourt@sipearl.com \
--cc=olivierdautricourt@gmail.com \
--cc=rafael@kernel.org \
--cc=sudeep.holla@arm.com \
--cc=thibault.cantori@sipearl.com \
/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