From: chengwei <foxfly.lai.tw@gmail.com>
To: pavel@ucw.cz, lee@kernel.org
Cc: linux-kernel@vger.kernel.org, linux-leds@vger.kernel.org,
GaryWang@aaeon.com.tw, musa.lin@yunjingtech.com,
jack.chang@yunjingtech.com, chengwei <larry.lai@yunjingtech.com>
Subject: [PATCH v2 0/2] Add support control UP board CPLD onboard LEDS
Date: Fri, 7 Oct 2022 13:25:28 +0800 [thread overview]
Message-ID: <20221007052530.31621-1-larry.lai@yunjingtech.com> (raw)
The UP board <http://www.upboard.com> is the computer board for
Professional Makers and Industrial Applications. We want to upstream
the UP board 40-pin GP-bus Kernel driver for giving the users better
experience on the software release. (not just download from UP board
github)
These patches are generated from the Linux kernel mainline tag v6.0.
chengwei (2):
mfd: Add support for UP board CPLD/FPGA
leds: Add support for UP board CPLD onboard LEDS
drivers/leds/Kconfig | 10 +
drivers/leds/Makefile | 1 +
drivers/leds/leds-upboard.c | 78 +++++
drivers/mfd/Kconfig | 11 +
drivers/mfd/Makefile | 1 +
drivers/mfd/upboard-fpga.c | 482 +++++++++++++++++++++++++++++++
include/linux/mfd/upboard-fpga.h | 49 ++++
7 files changed, 632 insertions(+)
create mode 100644 drivers/leds/leds-upboard.c
create mode 100644 drivers/mfd/upboard-fpga.c
create mode 100644 include/linux/mfd/upboard-fpga.h
base-commit: 4fe89d07dcc2804c8b562f6c7896a45643d34b2f
--
2.17.1
next reply other threads:[~2022-10-07 5:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-07 5:25 chengwei [this message]
2022-10-07 5:25 ` [PATCH v2 1/2] mfd: Add support for UP board CPLD/FPGA chengwei
2022-10-07 17:23 ` kernel test robot
2022-10-08 2:51 ` kernel test robot
2022-10-07 5:25 ` [PATCH v2 2/2] leds: Add support for UP board CPLD onboard LEDS chengwei
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=20221007052530.31621-1-larry.lai@yunjingtech.com \
--to=foxfly.lai.tw@gmail.com \
--cc=GaryWang@aaeon.com.tw \
--cc=jack.chang@yunjingtech.com \
--cc=larry.lai@yunjingtech.com \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=musa.lin@yunjingtech.com \
--cc=pavel@ucw.cz \
/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
all inboxes | Powered by JetHome®