From: kernel test robot <lkp@intel.com>
To: Gerhard Engleder <eg@keba.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Lukas Wunner <lukas@wunner.de>
Subject: drivers/tty/serial/8250/8250_keba.c:250:1: warning: the frame size of 1056 bytes is larger than 1024 bytes
Date: Fri, 25 Sep 2026 19:31:43 +0200 [thread overview]
Message-ID: <202609251951.KVWH0guw-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 165768bb70265b5c38cf0b73fafd75be235f8b14
commit: ab9a30d6febf768c057fcde74a46597862db443e serial: 8250: add driver for KEBA UART
date: 10 months ago
config: sparc-allyesconfig (https://download.01.org/0day-ci/archive/20260925/202609251951.KVWH0guw-lkp@intel.com/config)
compiler: sparc64-linux-gcc (GCC) 16.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260925/202609251951.KVWH0guw-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
| Fixes: ab9a30d6febf ("serial: 8250: add driver for KEBA UART")
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202609251951.KVWH0guw-lkp@intel.com/
All warnings (new ones prefixed by >>):
drivers/tty/serial/8250/8250_keba.c: In function 'kuart_probe':
>> drivers/tty/serial/8250/8250_keba.c:250:1: warning: the frame size of 1056 bytes is larger than 1024 bytes [-Wframe-larger-than=]
250 | }
| ^
vim +250 drivers/tty/serial/8250/8250_keba.c
158
159 static int kuart_probe(struct auxiliary_device *auxdev,
160 const struct auxiliary_device_id *id)
161 {
162 struct device *dev = &auxdev->dev;
163 struct uart_8250_port uart = {};
164 struct resource res;
165 struct kuart *kuart;
166 int retval;
167
168 kuart = devm_kzalloc(dev, sizeof(*kuart), GFP_KERNEL);
169 if (!kuart)
170 return -ENOMEM;
171 kuart->auxdev = container_of(auxdev, struct keba_uart_auxdev, auxdev);
172 kuart->flags = id->driver_data;
173 auxiliary_set_drvdata(auxdev, kuart);
174
175 /*
176 * map only memory in front of UART registers, UART registers will be
177 * mapped by serial port
178 */
179 res = kuart->auxdev->io;
180 res.end = res.start + KUART_BASE - 1;
181 kuart->base = devm_ioremap_resource(dev, &res);
182 if (IS_ERR(kuart->base))
183 return PTR_ERR(kuart->base);
184
185 if (kuart->flags & KUART_USE_CAPABILITY) {
186 /*
187 * supported modes are read from capability register, at least
188 * one mode other than none must be supported
189 */
190 kuart->capability = ioread8(kuart->base + KUART_CAPABILITY) &
191 KUART_CAPABILITY_MASK;
192 if ((kuart->capability & ~KUART_CAPABILITY_NONE) == 0)
193 return -EIO;
194 }
195
196 spin_lock_init(&uart.port.lock);
197 uart.port.dev = dev;
198 uart.port.mapbase = kuart->auxdev->io.start + KUART_BASE;
199 uart.port.irq = kuart->auxdev->irq;
200 uart.port.uartclk = KUART_CLK;
201 uart.port.private_data = kuart;
202
203 /* 8 bit registers are 32 bit aligned => shift register offset */
204 uart.port.iotype = UPIO_MEM32;
205 uart.port.regshift = KUART_REGSHIFT;
206
207 /*
208 * UART mixes 16550, 16750 and 16C950 (for RS485) standard => auto
209 * configuration works best
210 */
211 uart.port.flags = UPF_SKIP_TEST | UPF_BOOT_AUTOCONF | UPF_IOREMAP;
212
213 /*
214 * UART supports RS485, RS422 and RS232 with switching of physical
215 * interface
216 */
217 uart.port.rs485_config = kuart_rs485_config;
218 if (kuart->flags & KUART_RS485) {
219 uart.port.rs485_supported.flags = SER_RS485_ENABLED |
220 SER_RS485_RTS_ON_SEND;
221 uart.port.rs485.flags = SER_RS485_ENABLED |
222 SER_RS485_RTS_ON_SEND;
223 }
224 if (kuart->flags & KUART_USE_CAPABILITY) {
225 /* default mode priority is RS485 > RS422 > RS232 */
226 if (kuart->capability & KUART_CAPABILITY_RS422) {
227 uart.port.rs485_supported.flags |= SER_RS485_ENABLED |
228 SER_RS485_RTS_ON_SEND |
229 SER_RS485_MODE_RS422;
230 uart.port.rs485.flags = SER_RS485_ENABLED |
231 SER_RS485_RTS_ON_SEND |
232 SER_RS485_MODE_RS422;
233 }
234 if (kuart->capability & KUART_CAPABILITY_RS485) {
235 uart.port.rs485_supported.flags |= SER_RS485_ENABLED |
236 SER_RS485_RTS_ON_SEND;
237 uart.port.rs485.flags = SER_RS485_ENABLED |
238 SER_RS485_RTS_ON_SEND;
239 }
240 }
241
242 retval = serial8250_register_8250_port(&uart);
243 if (retval < 0) {
244 dev_err(&auxdev->dev, "UART registration failed!\n");
245 return retval;
246 }
247 kuart->line = retval;
248
249 return 0;
> 250 }
251
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-09-25 17:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202609251951.KVWH0guw-lkp@intel.com \
--to=lkp@intel.com \
--cc=eg@keba.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=oe-kbuild-all@lists.linux.dev \
/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®