From: Tzung-Bi Shih <tzungbi@google.com>
To: "Dustin L. Howett" <dustin@howett.net>
Cc: linux-kernel@vger.kernel.org, Benson Leung <bleung@chromium.org>,
Guenter Roeck <groeck@chromium.org>,
Michael Niksa <michael.niksa@live.com>
Subject: Re: [PATCH v2 0/2] platform/chrome: add support for the Framework Laptop
Date: Thu, 27 Jan 2022 10:31:16 +0800 [thread overview]
Message-ID: <YfID9LgDOW0GkJ26@google.com> (raw)
In-Reply-To: <20220126180020.15873-1-dustin@howett.net>
On Wed, Jan 26, 2022 at 12:00:18PM -0600, Dustin L. Howett wrote:
> 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.
>
> Since this EC driver probes the MEC range first, and uses only the MEC
> range if that probe succeeds[^1], we can get by without requesting the
> entire port range required by non-MEC embedded controllers until
> absolutely necessary.
>
> [^1]: this includes "memory mapped" read - where the traditional LPC EC
> requires I/O ports 0x900-0x9FF, the MEC EC multiplexes reads/writes
> over the same eight ports, 0x800-0x807.
>
> Changelog in v2:
> Cleaned up the commit subjects per request.
>
> Dustin L. Howett (2):
> platform/chrome: cros_ec_lpcs: detect the Framework Laptop
> platform/chrome: cros_ec_lpcs: reserve the MEC LPC I/O ports first
For the series,
Reviewed-by: Tzung-Bi Shih <tzungbi@google.com>
prev parent reply other threads:[~2022-01-27 2:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-26 18:00 Dustin L. Howett
2022-01-26 18:00 ` [PATCH v2 1/2] platform/chrome: cros_ec_lpcs: detect " Dustin L. Howett
2022-01-26 18:00 ` [PATCH v2 2/2] platform/chrome: cros_ec_lpcs: reserve the MEC LPC I/O ports first Dustin L. Howett
2022-01-27 18:55 ` Prashant Malani
2022-01-27 19:18 ` Dustin Howett
2022-01-27 19:25 ` Prashant Malani
2022-01-28 3:15 ` Dustin Howett
[not found] ` <CAJnPg5+bU68s2hq75aewap2gyW3YB+gpamKmuB-VfcpGf5krwA@mail.gmail.com>
2022-02-02 19:47 ` Prashant Malani
2022-01-27 19:30 ` Prashant Malani
2022-01-27 2:31 ` Tzung-Bi Shih [this message]
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=YfID9LgDOW0GkJ26@google.com \
--to=tzungbi@google.com \
--cc=bleung@chromium.org \
--cc=dustin@howett.net \
--cc=groeck@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.niksa@live.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
Powered by JetHome