[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH 2/3] hw/sensor: max31785 : add fan status, tach target, and t
From: |
Peter Maydell |
Subject: |
Re: [PATCH 2/3] hw/sensor: max31785 : add fan status, tach target, and tach input object properties |
Date: |
Thu, 14 Jul 2022 14:10:35 +0100 |
On Thu, 14 Jul 2022 at 14:04, Maheswara Kurapati
<quic_mkurapat@quicinc.com> wrote:
>
> This fix adds object properties for the FAN_COMMAND_1 (3Bh), STATUS_FANS_1_2
> (81h),
> READ_FAN_SPEED_1 (90h) registers for the MAX31785 instrumentation. An
> additional
> property tach_margin_percent updates the tachs for a configured percent of
> FAN_COMMAND_1 value.
>
> Register property
> --------------------------------------
> FAN_COMMAND_1 (3Bh) fan_target
> STATUS_FANS_1_2 (81h) status_fans_1_2
> READ_FAN_SPEED_1 (90h) fan_input
This commit message is missing the rationale -- why do we need this?
I am also not sure that we should be defining properties that are
just straight 1:1 with the device registers. Compare the way we
handle temperature-sensor values, where the property values are
defined in a generic manner (same units representation) regardless
of the underlying device and the device's property-set-get implementation
then handles converting that to and from whatever internal implementation
representation the device happens to use.
thanks
-- PMM
- [PATCH 0/3] Object properties for MAX31785 status, target, and input., Maheswara Kurapati, 2022/07/14
- [PATCH 1/3] qom/object : add object_property_add_int8_ptr() property for 8 bit signed integers., Maheswara Kurapati, 2022/07/14
- [PATCH 3/3] hw/sensor: max31785 : update the tach input based on the tach margin percentage, Maheswara Kurapati, 2022/07/14
- [PATCH 2/3] hw/sensor: max31785 : add fan status, tach target, and tach input object properties, Maheswara Kurapati, 2022/07/14
- Re: [PATCH 2/3] hw/sensor: max31785 : add fan status, tach target, and tach input object properties,
Peter Maydell <=