public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: "Zhang, Rui" <rui.zhang@intel.com>
To: "rafael@kernel.org" <rafael@kernel.org>,
	"W_Armin@gmx.de" <W_Armin@gmx.de>
Cc: "linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>
Subject: Re: ACPI INT340E PTID device
Date: Mon, 15 Jan 2024 14:13:12 +0000	[thread overview]
Message-ID: <fec103c301df89c630d894d7c1f6db6f7ccea540.camel@intel.com> (raw)
In-Reply-To: <14c6f480-66f4-4683-92d6-55a58eb98585@gmx.de>

Hi,

On Sun, 2024-01-14 at 13:42 +0100, Armin Wolf wrote:
> Hello,
> 
> a user has asked if the ACPI INT340E device could be supported.

What does this device bring to the user?

>  Its seems that this device exposes
> thermal and power sensors to the operating system, plus some general
> purpose "OSD" sensors.

Hmm, I don't know what this device really means. At least it is not
related with the other INT340X devices.

> 
> The device is already supported by the Hackintosh community, see
> here:
> https://github.com/RehabMan/OS-X-FakeSMC-kozlek/blob/master/ACPISensors/PTIDSensors.cpp
> 
> Back in 2014, the INT340E device was mentioned in message
> "1408622934.3315.8.camel@rzhang1-toshiba" as:
> 
>         The PTID device has _CID PNP0C02, but it is also represents
> an
>         INT340E device, there is a platform bus driver for this
> device
>         which will be introduced by myself soon.

Interesting, I cannot recall what happened, maybe that device ID is
deprecated later.

CC srinivas, and we will make clear what it does before doing anything.

thanks,
rui

  reply	other threads:[~2024-01-15 14:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-14 12:42 ACPI INT340E PTID device Armin Wolf
2024-01-15 14:13 ` Zhang, Rui [this message]
2024-01-15 17:00   ` Armin Wolf
2024-01-18 16:51     ` Zhang, Rui

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=fec103c301df89c630d894d7c1f6db6f7ccea540.camel@intel.com \
    --to=rui.zhang@intel.com \
    --cc=W_Armin@gmx.de \
    --cc=linux-acpi@vger.kernel.org \
    --cc=rafael@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