From: Tony Nguyen <anthony.l.nguyen@intel.com>
To: Konrad Knitter <konrad.knitter@intel.com>,
<intel-wired-lan@lists.osuosl.org>
Cc: Eric Joyner <eric.joyner@intel.com>,
netdev@vger.kernel.org,
Marcin Szycik <marcin.szycik@linux.intel.com>,
Przemek Kitszel <przemyslaw.kitszel@intel.com>,
Marcin Domagala <marcinx.domagala@intel.com>
Subject: Re: [Intel-wired-lan] [PATCH iwl-next v1] ice: read internal temperature sensor
Date: Thu, 28 Sep 2023 14:39:42 -0700 [thread overview]
Message-ID: <e34287a6-6ecf-55af-b2df-b14ec7801a16@intel.com> (raw)
In-Reply-To: <20230927133857.559432-1-konrad.knitter@intel.com>
On 9/27/2023 6:38 AM, Konrad Knitter wrote:
> Since 4.30 firmware exposes internal thermal sensor reading via admin
> queue commands. Expose those readouts via hwmon API when supported.
>
> Driver provides current reading from HW as well as device specific
> thresholds for thermal alarm (Warning, Critical, Fatal) events.
>
> $ sensors
>
> Output
> =========================================================
> ice-pci-b100
> Adapter: PCI adapter
> temp1: +62.0°C (high = +95.0°C, crit = +105.0°C)
> (emerg = +115.0°C)
checkpatch reports issues; please resolve applicable issues.
> Co-developed-by: Marcin Domagala <marcinx.domagala@intel.com>
> Signed-off-by: Marcin Domagala <marcinx.domagala@intel.com>
> Co-developed-by: Eric Joyner <eric.joyner@intel.com>
> Signed-off-by: Eric Joyner <eric.joyner@intel.com>
> Reviewed-by: Marcin Szycik <marcin.szycik@linux.intel.com>
> Reviewed-by: Przemek Kitszel <przemyslaw.kitszel@intel.com>
> Signed-off-by: Konrad Knitter <konrad.knitter@intel.com>
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
prev parent reply other threads:[~2023-09-28 21:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-27 13:38 [Intel-wired-lan] [PATCH iwl-next v1] ice: read internal temperature sensor Konrad Knitter
2023-09-27 13:48 ` Andrew Lunn
2023-09-28 21:39 ` Tony Nguyen [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=e34287a6-6ecf-55af-b2df-b14ec7801a16@intel.com \
--to=anthony.l.nguyen@intel.com \
--cc=eric.joyner@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=konrad.knitter@intel.com \
--cc=marcin.szycik@linux.intel.com \
--cc=marcinx.domagala@intel.com \
--cc=netdev@vger.kernel.org \
--cc=przemyslaw.kitszel@intel.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