From: Tom Li <biergaizi2009@gmail.com>
To: Lee Jones <lee.jones@linaro.org>
Cc: linux-mips@vger.kernel.org, Paul Burton <paul.burton@mips.com>,
linux-kernel@vger.kernel.org, Tom Li <biergaizi2009@gmail.com>
Subject: [PATCH 0/1] KB3310B MFD Driver for Lemote Yeeloong laptops.
Date: Sat, 30 Mar 2019 16:18:35 +0800 [thread overview]
Message-ID: <20190330081836.26942-1-biergaizi2009@gmail.com> (raw)
This is a resend of the first patch ("[PATCH v3 1/7]") in the patchset
"[PATCH v3 0/7] Preliminary Platform Driver Support for Lemote Yeeloong
Laptops" [0], which introduced a new MFD driver.
The original patchset never arrived to Lee's inbox. so I resend the
patch to facilitate review.
It features the following...
* Create a MFD driver for KB3310B controller, and move the original
KB3310B controller code from mips/loongson64 to our new MFD driver.
This needs to be reviewed by the MFD subsystem maintainer before the
following can proceed.
* Subdrivers - hwmon, battery, backlight, lcd and hotkey are registered
as MFD cells in the MFD driver. It means onlf the MFD driver is resposible
to register the upcoming subdrivers, the core board files mips/loongson64/
will not contain unrelated code.
[0] https://lore.kernel.org/linux-mips/20190306120113.648-1-tomli@tomli.me/T/#m2a6e18afbb62ceb535a859181d8485916b30a63f
Thanks,
Yifeng Li (1):
mfd: yeeloong_kb3310b: support KB3310B EC for Lemote Yeeloong laptops.
MAINTAINERS | 7 +
drivers/mfd/Kconfig | 10 ++
drivers/mfd/Makefile | 1 +
drivers/mfd/yeeloong_kb3310b.c | 200 +++++++++++++++++++++++++
include/linux/mfd/yeeloong_kb3310b.h | 211 +++++++++++++++++++++++++++
5 files changed, 429 insertions(+)
create mode 100644 drivers/mfd/yeeloong_kb3310b.c
create mode 100644 include/linux/mfd/yeeloong_kb3310b.h
--
2.20.1
next reply other threads:[~2019-03-30 8:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-30 8:18 Tom Li [this message]
2019-03-30 8:18 ` [PATCH 1/1] mfd: yeeloong_kb3310b: support KB3310B EC for Lemote Yeeloong laptops Tom Li
2019-04-03 8:36 ` Lee Jones
2020-01-23 0:22 ` Matt Turner
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=20190330081836.26942-1-biergaizi2009@gmail.com \
--to=biergaizi2009@gmail.com \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=paul.burton@mips.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;
as well as URLs for NNTP newsgroup(s).