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 0/3] Add support for Congatec CGEB BIOS interface
Date: Wed, 17 Jul 2024 21:15:01 -0400 [thread overview]
Message-ID: <20240718011504.4106163-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.
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):
mm: vmalloc: export __vmalloc_node_range
Sascha Hauer (2):
x86: Add basic support for the Congatec CGEB BIOS interface
i2c: Add Congatec CGEB I2C driver
drivers/i2c/busses/Kconfig | 7 +
drivers/i2c/busses/Makefile | 1 +
drivers/i2c/busses/i2c-congatec-cgeb.c | 187 ++++++++
drivers/mfd/Kconfig | 10 +
drivers/mfd/Makefile | 1 +
drivers/mfd/congatec-cgeb.c | 620 +++++++++++++++++++++++++
include/linux/mfd/congatec-cgeb.h | 105 +++++
mm/vmalloc.c | 1 +
8 files changed, 932 insertions(+)
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-07-18 1:16 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-18 1:15 Mary Strodl [this message]
2024-07-18 1:15 ` [PATCH 1/3] mm: vmalloc: export __vmalloc_node_range Mary Strodl
2024-07-18 2:53 ` Andrew Morton
2024-07-18 12:29 ` Mary Strodl
2024-07-18 3:04 ` Christoph Hellwig
2024-07-18 12:40 ` Mary Strodl
2024-07-18 12:45 ` Matthew Wilcox
2024-07-18 12:49 ` Christoph Hellwig
2024-07-18 12:53 ` Matthew Wilcox
2024-07-18 13:20 ` Mary Strodl
2024-07-18 21:31 ` Andrew Morton
2024-07-18 21:35 ` Matthew Wilcox
2024-07-18 21:39 ` Andrew Morton
2024-07-19 6:41 ` Christian Gmeiner
2024-07-19 11:58 ` Mary Strodl
2024-07-19 12:42 ` Matthew Wilcox
2024-07-24 0:00 ` Andrew Morton
2024-07-24 0:16 ` Matthew Wilcox
2024-07-24 1:36 ` Christoph Hellwig
2024-07-19 19:59 ` Rudolf Marek
2024-07-22 14:54 ` Mary Strodl
2024-07-18 1:15 ` [PATCH 2/3] x86: Add basic support for the Congatec CGEB BIOS interface Mary Strodl
2024-07-18 3:56 ` kernel test robot
2024-07-18 14:01 ` kernel test robot
2024-07-18 1:15 ` [PATCH 3/3] i2c: Add Congatec CGEB I2C driver Mary Strodl
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=20240718011504.4106163-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