From: "Dustin L. Howett" <dustin@howett.net>
To: linux-kernel@vger.kernel.org
Cc: Benson Leung <bleung@chromium.org>,
Guenter Roeck <groeck@chromium.org>,
"Dustin L. Howett" <dustin@howett.net>
Subject: [PATCH 0/2] platform/chrome: Add support for the Framework Laptop
Date: Tue, 4 Jan 2022 21:12:40 -0600 [thread overview]
Message-ID: <20220105031242.287751-1-dustin@howett.net> (raw)
This patch series adds support for the Framework Laptop to the cros_ec
LPC driver.
The Framework Laptop is a non-Chromebook laptop that uses the ChromeOS
Embedded Controller. Since the machine was designed to present a more
normal device profile, it does not report all 512 I/O ports that are
typically used by cros_ec_lpcs. Because of this, changes to the driver's
port reservation scheme were required.
Dustin L. Howett (2):
platform/chrome: cros-ec: detect the Framework Laptop
platform/chrome: reserve only the I/O ports required for the MEC EC
drivers/platform/chrome/cros_ec_lpc.c | 47 ++++++++++-----
include/linux/platform_data/cros_ec_commands.h | 4 +
2 files changed, 38 insertions(+), 13 deletions(-)
--
2.34.1
next reply other threads:[~2022-01-05 3:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-05 3:12 Dustin L. Howett [this message]
2022-01-05 3:12 ` [PATCH 1/2] platform/chrome: cros-ec: detect the Framework Laptop Dustin L. Howett
2022-01-25 3:41 ` Tzung-Bi Shih
2022-01-25 4:16 ` Tzung-Bi Shih
2022-01-05 3:12 ` [PATCH 2/2] platform/chrome: reserve only the I/O ports required for the MEC EC Dustin L. Howett
2022-01-25 3:42 ` Tzung-Bi Shih
2022-01-25 4:17 ` Tzung-Bi Shih
2022-01-25 15:15 ` Dustin Howett
2022-01-26 6:24 ` Tzung-Bi Shih
2022-01-24 20:51 ` [PATCH 0/2] platform/chrome: Add support for the Framework Laptop Benson Leung
2022-01-25 1:12 ` Tzung-Bi Shih
2022-01-25 16:52 ` Guenter Roeck
2022-01-25 17:38 ` Benson Leung
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=20220105031242.287751-1-dustin@howett.net \
--to=dustin@howett.net \
--cc=bleung@chromium.org \
--cc=groeck@chromium.org \
--cc=linux-kernel@vger.kernel.org \
/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).