mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: hdegoede@redhat.com, linus.walleij@linaro.org, brgl@bgdev.pl,
	 wim@linux-watchdog.org, linux@roeck-us.net,
	 Yen-Chi Huang <jesse.huang@portwell.com.tw>
Cc: linux-kernel@vger.kernel.org,
	platform-driver-x86@vger.kernel.org,  linux-gpio@vger.kernel.org,
	linux-watchdog@vger.kernel.org,  jay.chen@canonical.com
Subject: Re: [PATCH v6] platform/x86: portwell-ec: Add GPIO and WDT driver for Portwell EC
Date: Thu, 08 May 2025 17:50:34 +0300	[thread overview]
Message-ID: <174671583458.18151.3490608010947983443.b4-ty@linux.intel.com> (raw)
In-Reply-To: <a04be962-b207-4085-af5b-523f59bffcbc@portwell.com.tw>

On Tue, 06 May 2025 18:23:14 +0800, Yen-Chi Huang wrote:

> Adds a driver for the ITE Embedded Controller (EC) on Portwell boards.
> It integrates with the Linux GPIO and watchdog subsystems to provide:
> 
> - Control/monitoring of up to 8 EC GPIO pins.
> - Hardware watchdog timer with 1-255 second timeouts.
> 
> The driver communicates with the EC via I/O port 0xe300 and identifies
> the hardware by the "PWG" firmware signature. This enables enhanced
> system management for Portwell embedded/industrial platforms.
> 
> [...]


Thank you for your contribution, it has been applied to my local
review-ilpo-next branch. Note it will show up in the public
platform-drivers-x86/review-ilpo-next branch only once I've pushed my
local branch there, which might take a while.

The list of commits applied:
[1/1] platform/x86: portwell-ec: Add GPIO and WDT driver for Portwell EC
      commit: 83579675331059689e2869bf752ca9e17fadbd82

--
 i.


      reply	other threads:[~2025-05-08 14:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-06 10:23 Yen-Chi Huang
2025-05-08 14:50 ` Ilpo Järvinen [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=174671583458.18151.3490608010947983443.b4-ty@linux.intel.com \
    --to=ilpo.jarvinen@linux.intel.com \
    --cc=brgl@bgdev.pl \
    --cc=hdegoede@redhat.com \
    --cc=jay.chen@canonical.com \
    --cc=jesse.huang@portwell.com.tw \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=wim@linux-watchdog.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

all inboxes | Powered by JetHome®