From: Ravi Kumar Bandi <ravib@amazon.com>
To: <hch@infradead.org>
Cc: <akpm@linux-foundation.org>, <bhelgaas@google.com>,
<david@kernel.org>, <djbw@kernel.org>,
<ilpo.jarvinen@linux.intel.com>, <linux-kernel@vger.kernel.org>,
<ravib@amazon.com>
Subject: Re: [PATCH] resource: export iomem_get_mapping() for loadable modules
Date: Tue, 12 May 2026 07:50:22 +0000 [thread overview]
Message-ID: <20260512075022.48671-1-ravib@amazon.com> (raw)
In-Reply-To: <agLVQPEKVLJNoU7p@infradead.org>
On 5/11/26, Bjorn Helgaas wrote:
> Which endpoint driver?
Thank you for checking.
It is Marvell PCIe driver for a device without a hot-plug pin routed
to the CPU. The link-down event is detected by the in-tree Xilinx DMA PL
PCIe controller driver (drivers/pci/controller/pcie-xilinx-dma-pl.c).
> Why would the endpoint driver map iomem to userspace?
sysfs exposed BAR resource files are mmap'd directly by a third-party
userspace driver.
> Well, we need to see the user(s) first, but once they materialize this
> begs for a higher level API. Until then it is moot anyway.
Understood. Thank you for the feedback. We will work on a higher level
API proposal and get back.
Regards,
Ravi Kumar Bandi
next prev parent reply other threads:[~2026-05-12 7:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-11 6:56 [PATCH] resource: export iomem_get_mapping() for loadable modules Ravi Kumar Bandi
2026-05-11 7:14 ` David Hildenbrand (Arm)
2026-05-11 7:17 ` Christoph Hellwig
2026-05-11 16:16 ` Ravi Kumar Bandi
2026-05-12 7:10 ` David Hildenbrand (Arm)
2026-05-12 7:31 ` Ravi Kumar Bandi
2026-05-12 7:22 ` Christoph Hellwig
2026-05-12 7:50 ` Ravi Kumar Bandi [this message]
2026-05-13 18:45 ` Dan Williams (nvidia)
2026-05-14 15:54 ` Ravi Kumar Bandi
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=20260512075022.48671-1-ravib@amazon.com \
--to=ravib@amazon.com \
--cc=akpm@linux-foundation.org \
--cc=bhelgaas@google.com \
--cc=david@kernel.org \
--cc=djbw@kernel.org \
--cc=hch@infradead.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-kernel@vger.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.