qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>,
	"Patrick Venture" <venture@google.com>,
	lvivier@redhat.com, pbonzini@redhat.com
Cc: Hao Wu <wuhaotsh@google.com>,
	qemu-devel@nongnu.org, Corey Minyard <minyard@acm.org>,
	Doug Evans <dje@google.com>
Subject: Re: [PATCH] hw/sensor: Add SB-TSI Temperature Sensor Interface
Date: Thu, 13 Jan 2022 08:19:08 +0100	[thread overview]
Message-ID: <a1c2ebd6-1aca-f03e-e55c-f697ed244a06@redhat.com> (raw)
In-Reply-To: <eaea55f9-71f8-4810-70a7-63aadf252f20@amsat.org>

On 10/01/2022 10.35, Philippe Mathieu-Daudé wrote:
> Hi Patrick,
> 
> On 1/8/22 04:04, Patrick Venture wrote:
>> From: Hao Wu <wuhaotsh@google.com>
>>
>> SB Temperature Sensor Interface (SB-TSI) is an SMBus compatible
>> interface that reports AMD SoC's Ttcl (normalized temperature),
>> and resembles a typical 8-pin remote temperature sensor's I2C interface
>> to BMC.
>>
>> This patch implements a basic AMD SB-TSI sensor that is
>> compatible with the open-source data sheet from AMD and Linux
>> kernel driver.
>>
>> Reference:
>> Linux kernel driver:
>> https://lkml.org/lkml/2020/12/11/968
>> Register Map:
>> https://developer.amd.com/wp-content/resources/56255_3_03.PDF
>> (Chapter 6)
>>
>> Signed-off-by: Hao Wu <wuhaotsh@google.com>
>> Reviewed-by: Doug Evans <dje@google.com>
>> ---
>>   hw/sensor/Kconfig            |   4 +
>>   hw/sensor/meson.build        |   1 +
>>   hw/sensor/tmp_sbtsi.c        | 393 +++++++++++++++++++++++++++++++++++
>>   hw/sensor/trace-events       |   5 +
>>   hw/sensor/trace.h            |   1 +
>>   meson.build                  |   1 +
> 
>>   tests/qtest/meson.build      |   1 +
>>   tests/qtest/tmp_sbtsi-test.c | 180 ++++++++++++++++
> 
> Up to Thomas for qtest, but I'd rather split in 2 patches since
> different set of maintainers / reviewers.

I don't mind too much - but anyway, I'd prefer if we could stick to "-" in 
file names here - mixing underscores and "-" in file names looks somewhat 
weird (I know, there are already some files like this, but I'd prefer if 
we'd not extend that list).

  Thomas




  parent reply	other threads:[~2022-01-13  7:37 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-08  3:04 [PATCH] hw/sensor: Add SB-TSI Temperature Sensor Interface Patrick Venture
2022-01-10  2:17 ` Patrick Venture
2022-01-17 14:05   ` Corey Minyard
2022-01-18 17:10     ` Patrick Venture
2022-01-27  0:09       ` Hao Wu
2022-01-27 14:55         ` Corey Minyard
2022-01-27 18:19           ` Hao Wu
2022-01-27 23:18             ` Patrick Venture
2022-01-28  1:58               ` Corey Minyard
2022-01-10  9:35 ` Philippe Mathieu-Daudé
2022-01-10 17:14   ` Patrick Venture
2022-01-10 19:30     ` Philippe Mathieu-Daudé
2022-01-10 19:41       ` Patrick Venture
2022-01-13  7:19   ` Thomas Huth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-08-12 16:51 Hao Wu

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=a1c2ebd6-1aca-f03e-e55c-f697ed244a06@redhat.com \
    --to=thuth@redhat.com \
    --cc=dje@google.com \
    --cc=f4bug@amsat.org \
    --cc=lvivier@redhat.com \
    --cc=minyard@acm.org \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=venture@google.com \
    --cc=wuhaotsh@google.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;
as well as URLs for NNTP newsgroup(s).