From: Filip Jensen <dev-Felipe.Jensen@duagon.com>
To: morbidrsa@gmail.com
Cc: linux-kernel@vger.kernel.org,
Filip Jensen <dev-Felipe.Jensen@duagon.com>,
Jose Javier Rodriguez Barbarin
<dev-josejavier.rodriguez@duagon.com>
Subject: [PATCH v3 0/2] mcb: enable register PCI devices using any BAR
Date: Wed, 4 Mar 2026 14:26:48 +0100 [thread overview]
Message-ID: <20260304132650.140680-1-dev-Felipe.Jensen@duagon.com> (raw)
V2 -> V3: Thanks for second review. Fixed declaring pci_dev outside of the
only block where it is needed in patch 1/2.
V1 -> V2: Thanks to the review from Johannes Thumshirn, the patch 2/3 of
the first version has been removed and the cleaner solution from patch 3/3
is then kept.
The PCI mcb driver is currently only able to register devices that use
the first PCI BAR. That is hardcoded in mcb-parse.c in lines 156-161:
c = kzalloc_obj(struct chameleon_bar);
if (!c)
return -ENOMEM;
bar_count = 1;
c->addr = mapbase;
However, mcb devices can use other indexes of the 6 PCI BARs. This serie of
patches allows to use these devices by adding the relevant PCI BAR info to
the chameleon table. As this code must also work for lpc devices, it has
been done a refactoring in order to keep the two buses dependent operations
regarding bars (get_bar and is_io_mapped_bar) outside of the common parsing
code. These callback operations are stored in a structure and passed over
to the parser, thus rendering each module, the mcb-lpc and mcb-pci, only
with their own bus relevant logic.
This patch depends on the previously accepted patch:
Link: https://lore.kernel.org/lkml/20260217075124.10052-1-dev-Felipe.Jensen@duagon.com/
Reviewed-by: Jose Javier Rodriguez Barbarin <dev-josejavier.rodriguez@duagon.com>
Filip Jensen (2):
mcb: Use more than the first bar in pci devices
mcb: refactor bus operations out of common code
drivers/mcb/mcb-internal.h | 10 ++++-
drivers/mcb/mcb-lpc.c | 56 ++++++++++++++++++++++++++-
drivers/mcb/mcb-parse.c | 77 +++++---------------------------------
drivers/mcb/mcb-pci.c | 40 +++++++++++++++++++-
4 files changed, 111 insertions(+), 72 deletions(-)
--
2.34.1
next reply other threads:[~2026-03-04 13:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-04 13:26 Filip Jensen [this message]
2026-03-04 13:26 ` [PATCH v3 1/2] mcb: Use more than the first bar in pci devices Filip Jensen
2026-03-04 13:26 ` [PATCH v3 2/2] mcb: refactor bus operations out of common code Filip Jensen
2026-04-24 11:12 ` [PATCH v3 0/2] mcb: enable register PCI devices using any BAR Johannes Thumshirn
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=20260304132650.140680-1-dev-Felipe.Jensen@duagon.com \
--to=dev-felipe.jensen@duagon.com \
--cc=dev-josejavier.rodriguez@duagon.com \
--cc=linux-kernel@vger.kernel.org \
--cc=morbidrsa@gmail.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