All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jae Hyun Yoo" <jae.hyun.yoo@linux.intel.com>
To: <openbmc@lists.ozlabs.org>
Cc: <james.feist@linux.intel.com>, <ed.tanous@linux.intel.com>
Subject: Re: PECI API?
Date: Mon, 23 Oct 2017 10:03:51 -0700	[thread overview]
Message-ID: <001801d34c20$e670c150$b35243f0$@linux.intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 586 bytes --]

Hi Dave,

 

I'm currently working on PECI kernel driver and hwmon driver implementation.
The kernel driver would provide these PECI commands as ioctls:

 

- low-level PECI xfer command

- Ping()

- GetDIB()

- GetTemp()

- RdPkgConfig()

- WrPkgConfig()

- RdIAMSR()

- RdPCIConfigLocal()

- WrPCIConfigLocal()

- RdPCIConfig()

 

Also, through the hwmon driver, these temperature monitoring features would
be provided:

 

- Core temperature

- DTS thermal margin (hysteresis)

- DDR DIMM temperature

- etc.

 

Patches will come in to upstream when it is ready.

 

Cheers,

Jae


[-- Attachment #2: Type: text/html, Size: 9621 bytes --]

             reply	other threads:[~2017-10-23 17:04 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-23 17:03 Jae Hyun Yoo [this message]
2017-10-30 17:45 ` PECI API? Patrick Venture
2017-10-30 19:21 ` Brad Bishop
2017-10-31 16:26   ` Jae Hyun Yoo
2017-10-31 18:29     ` Rick Altherr
2017-10-31 21:50       ` Jae Hyun Yoo
2017-10-31 22:07         ` Rick Altherr
2017-11-01 16:45           ` Jae Hyun Yoo
2017-11-01 17:27             ` Rick Altherr
  -- strict thread matches above, loose matches on Subject: below --
2017-10-21  8:57 David Müller (ELSOFT AG)
2017-10-23 16:44 ` Tanous, Ed
2017-10-23 19:02   ` Rick Altherr
2017-10-23 19:39     ` Tanous, Ed
2017-10-23 19:47       ` Rick Altherr
2017-10-23 20:24         ` Tanous, Ed
2017-10-23 20:40           ` Rick Altherr
2017-10-24 11:12   ` David Müller (ELSOFT AG)
2017-10-25 20:11     ` Rick Altherr
2017-10-23 19:17 ` Brad Bishop

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='001801d34c20$e670c150$b35243f0$@linux.intel.com' \
    --to=jae.hyun.yoo@linux.intel.com \
    --cc=ed.tanous@linux.intel.com \
    --cc=james.feist@linux.intel.com \
    --cc=openbmc@lists.ozlabs.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.