From: Mary Strodl <mstrodl@csh.rit.edu>
To: linux-kernel@vger.kernel.org
Cc: akpm@linux-foundation.org, urezki@gmail.com, hch@infradead.org,
linux-mm@kvack.org, lee@kernel.org, andi.shyti@kernel.org,
linux-i2c@vger.kernel.org, s.hauer@pengutronix.de,
christian.gmeiner@gmail.com, Mary Strodl <mstrodl@csh.rit.edu>
Subject: [PATCH v4 0/2] Add support for Congatec CGEB BIOS interface
Date: Wed, 14 Aug 2024 14:47:29 -0400 [thread overview]
Message-ID: <20240814184731.1310988-1-mstrodl@csh.rit.edu> (raw)
The following series adds support for the Congatec CGEB interface
found on some Congatec x86 boards. The CGEB interface is a BIOS
interface which provides access to onboard peripherals like I2C
busses and watchdogs. It works by mapping BIOS code and searching
for magic values which specify the entry points to the CGEB call.
The CGEB call is an API provided by the BIOS which provides access
to the functions in an ioctl like fashion.
At the request of some folks the first time I sent this series out,
CGEB has a userspace component which runs the x86 blob (rather than
running it directly in the kernel), which sends requests back and
forth using the cn_netlink API.
You can find a reference implementation of the userspace helper here:
https://github.com/Mstrodl/cgeb-helper
I didn't get an answer when I asked where the userspace component
should live, so I didn't put a ton of work into getting the helper
up to snuff since similar userspace helpers (like v86d) are not
in-tree. If folks would like the helper in-tree, that's fine too.
Changelog:
v2:
* Moved CGEB code snippet execution into userspace
v3:
* `checkpatch` pass
* Should I add the driver files to MAINTAINERS? I'm not sure what
the norm is there...
* `sparse` pass
* I'm not sure there's a good way to keep the __iomem marker
around while not making the struct fields really inconvenient
to access, so I just cast them away which causes a sparse
warning. I figure it's probably okay since this driver
is x86-specific anyways? Let me know if this is an issue and
what the preferred approach is.
v4:
* Sort includes
* Remove GPL blurb from top of file
* Use memremap instead of ioremap_cache, avoids sparse warning
* Minor styling stuff
* Relocated some static declarations into function bodies
This series is based on the excellent work of Sascha Hauer and
Christian Gmeiner. You can find their original work here:
http://patchwork.ozlabs.org/patch/219756/
http://patchwork.ozlabs.org/patch/219755/
http://patchwork.ozlabs.org/patch/219757/
http://patchwork.ozlabs.org/patch/483262/
http://patchwork.ozlabs.org/patch/483264/
http://patchwork.ozlabs.org/patch/483261/
http://patchwork.ozlabs.org/patch/483263/
Mary Strodl (1):
x86: Add basic support for the Congatec CGEB BIOS interface
Sascha Hauer (1):
i2c: Add Congatec CGEB I2C driver
drivers/i2c/busses/Kconfig | 10 +
drivers/i2c/busses/Makefile | 1 +
drivers/i2c/busses/i2c-congatec-cgeb.c | 190 ++++
drivers/mfd/Kconfig | 10 +
drivers/mfd/Makefile | 1 +
drivers/mfd/congatec-cgeb.c | 1125 ++++++++++++++++++++++++
include/linux/mfd/congatec-cgeb.h | 112 +++
include/uapi/linux/connector.h | 4 +-
8 files changed, 1452 insertions(+), 1 deletion(-)
create mode 100644 drivers/i2c/busses/i2c-congatec-cgeb.c
create mode 100644 drivers/mfd/congatec-cgeb.c
create mode 100644 include/linux/mfd/congatec-cgeb.h
--
2.45.2
next reply other threads:[~2024-08-14 18:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-14 18:47 Mary Strodl [this message]
2024-08-14 18:47 ` [PATCH v4 1/2] x86: Add basic support for the " Mary Strodl
2024-08-15 4:59 ` Christoph Hellwig
2024-08-15 12:17 ` Thomas Gleixner
2024-08-15 12:39 ` Mary Strodl
2024-08-15 13:23 ` Thomas Gleixner
2024-08-14 18:47 ` [PATCH v4 2/2] i2c: Add Congatec CGEB I2C driver Mary Strodl
2024-08-20 8:39 ` [PATCH v4 0/2] Add support for Congatec CGEB BIOS interface Thomas Richard
2024-08-20 8:48 ` Christian Gmeiner
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=20240814184731.1310988-1-mstrodl@csh.rit.edu \
--to=mstrodl@csh.rit.edu \
--cc=akpm@linux-foundation.org \
--cc=andi.shyti@kernel.org \
--cc=christian.gmeiner@gmail.com \
--cc=hch@infradead.org \
--cc=lee@kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=s.hauer@pengutronix.de \
--cc=urezki@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