From: Florian Eckert <fe@dev.tdt.de>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: gregkh@linuxfoundation.org, jirislaby@kernel.org,
kumaravel.thiagarajan@microchip.com, pnewman@connecttech.com,
angelogioacchino.delregno@collabora.com, peterz@infradead.org,
yujiaoliang@vivo.com, arnd@kernel.org, cang1@live.co.uk,
macro@orcam.me.uk, schnelle@linux.ibm.com,
Eckert.Florian@googlemail.com, linux-kernel@vger.kernel.org,
linux-serial@vger.kernel.org
Subject: Re: [PATCH v2] serial: 8250_pcilib: Replace deprecated PCI functions
Date: Mon, 20 Oct 2025 08:47:16 +0200 [thread overview]
Message-ID: <84ad1b3070a8374ec20f06588fab9f86@dev.tdt.de> (raw)
In-Reply-To: <aPPreT00iiTDzJwG@ashevche-desk.local>
On 2025-10-18 21:33, Andy Shevchenko wrote:
> On Tue, Sep 30, 2025 at 09:27:43AM +0200, Florian Eckert wrote:
>> When the '8250_exar' module is loaded into the kernel, a kernel trace
>> with 'WARN_ON(legacy_iomap_table[bar])' is dumped to the console,
>> because the old pci table mapping is still used in '8250_pcilib'.
>>
>> The old function have been deprecated in commit e354bb84a4c1 ("PCI:
>> Deprecate pcim_iomap_table(), pcim_iomap_regions_request_all()").
>>
>> The remapping already takes or must take place in the driver that
>> calls
>> the function 'serial8250_pci_setup_port()'. The remapping should only
>> be
>> called once via 'pcim_iomap()'. Therefore the remapping moved to the
>> caller of 'serial8250_pci_setup_port()'.
>>
>> To replace the outdated/legacy iomap_table processing in '8250_pcilib'
>> the
>> function signature of 'serial8250_pci_setup_port()' has been extended
>> with
>> an already iomapped address value. So this can be used directly
>> without
>> io mapping again.
>
> ...
>
>> + if (pci_resource_flags(priv->dev, bar) & IORESOURCE_MEM) {
>
> Dunno if this is included already in Linux Next, but here is room for
> improvement.
>
I followed the code in the 'serial8250_pci_setup_port()' [1] function.
The same pattern is used there [2].
>
> The problem with the above code is it (wrongly?) checks for bit and not
> for the resource type. OTOH I don't remember if 64-bit version requires
> the IORESOURCE_MEM to be set along with that.
>
Do you mean the function 'platform_get_resource()' [3]? This is a
platform
device function?
[1]
https://elixir.bootlin.com/linux/v6.18-rc1/source/drivers/tty/serial/8250/8250_pcilib.c#L24
[2]
https://elixir.bootlin.com/linux/v6.18-rc1/source/drivers/tty/serial/8250/8250_pcilib.c#L30
[3]
https://elixir.bootlin.com/linux/v6.17.3/source/drivers/base/platform.c#L55
---
Florian
next prev parent reply other threads:[~2025-10-20 7:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-18 19:33 [PATCH v2] serial: 8250_pcilib: Replace deprecated PCI functions Andy Shevchenko
2025-10-20 6:47 ` Florian Eckert [this message]
2025-10-20 8:42 ` Andy Shevchenko
2025-10-20 16:18 ` Florian Eckert
2025-10-20 17:32 ` Andy Shevchenko
-- strict thread matches above, loose matches on Subject: below --
2025-09-30 7:27 Florian Eckert
2025-09-30 7:34 ` Jiri Slaby
2025-10-01 14:45 ` Florian Eckert
2025-10-02 5:25 ` Greg KH
2025-10-07 14:31 ` Florian Eckert
2025-10-13 20:35 ` Andy Shevchenko
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=84ad1b3070a8374ec20f06588fab9f86@dev.tdt.de \
--to=fe@dev.tdt.de \
--cc=Eckert.Florian@googlemail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=arnd@kernel.org \
--cc=cang1@live.co.uk \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=kumaravel.thiagarajan@microchip.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=macro@orcam.me.uk \
--cc=peterz@infradead.org \
--cc=pnewman@connecttech.com \
--cc=schnelle@linux.ibm.com \
--cc=yujiaoliang@vivo.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 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.