All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tzung-Bi Shih <tzungbi@kernel.org>
To: Gwendal Grignou <gwendal@chromium.org>
Cc: bleung@chromium.org, chrome-platform@lists.linux.dev,
	dustin@howett.net, ben@jubnut.com
Subject: Re: [PATCH v3 0/2] Add support for IO memory mapped EC
Date: Wed, 8 Jan 2025 02:26:04 +0000	[thread overview]
Message-ID: <Z33iPIaUNFnOYQpk@google.com> (raw)
In-Reply-To: <20250107174514.2748108-1-gwendal@chromium.org>

On Tue, Jan 07, 2025 at 09:45:12AM -0800, Gwendal Grignou wrote:
> Some EC - Realtek - have their register IO mapped by the BIOS -
> coreboot. They are not using the well know io register.
> 
> The memory mapping information is retrieved through the ACPI CRS
> resource, and is used to access the registers.
> 
> To ease the support of these ECs, the global structure and accessor
> funcions are now aware of the EC device private structure.
>
> [...]

Have removed the redundant title prefix "FROMLIST" and fixed a minor typo.

Applied to

    https://git.kernel.org/pub/scm/linux/kernel/git/chrome-platform/linux.git for-next

[1/2] platform/chrome: cros_ec_lpc: Merge lpc_driver_ops into ec private structure
      commit: 58517215304b6113beaa3a319ed19cdd9f8fbcc1
[2/2] platform/chrome: cros_ec_lpc: Support direct EC register memory access
      commit: be4fccb5e1fb5c732f2868b9a278e71d9be0283c

Thanks!

      parent reply	other threads:[~2025-01-08  2:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-07 17:45 [PATCH v3 0/2] Add support for IO memory mapped EC Gwendal Grignou
2025-01-07 17:45 ` [PATCH v3 1/2] FROMLIST: platform/chrome: cros_ec_lpc: Merge lpc_driver_ops into ec private structure Gwendal Grignou
2025-01-07 17:45 ` [PATCH v3 2/2] FROMLIST: platform/chrome: cros_ec_lpc: Add Support for direct EC register memory access Gwendal Grignou
2025-01-08  2:26 ` 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=Z33iPIaUNFnOYQpk@google.com \
    --to=tzungbi@kernel.org \
    --cc=ben@jubnut.com \
    --cc=bleung@chromium.org \
    --cc=chrome-platform@lists.linux.dev \
    --cc=dustin@howett.net \
    --cc=gwendal@chromium.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.