All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Feist <james.feist@linux.intel.com>
To: rgrs <rgrs@protonmail.com>
Cc: "openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>,
	Alexander Amelkin <a.amelkin@yadro.com>,
	"Thomaiyar,
	Richard Marian" <richard.marian.thomaiyar@linux.intel.com>
Subject: Re: Faking Sensor Readings
Date: Mon, 9 Dec 2019 10:28:50 -0800	[thread overview]
Message-ID: <e59e36d1-74fc-5f44-a472-26fdfb127af2@linux.intel.com> (raw)
In-Reply-To: <JIIzLFDdd2_yAem6ToyksGqeJ7ulaTOylaocMLH19rYqyv3fSzcEL2H9VDJW66iYQY8L8FwjgpZqPFj8rRD0JP52xsAHQ6kD4_ygDAjj0LE=@protonmail.com>

On 12/6/19 3:32 AM, rgrs wrote:
> Hi,
> 
> I dont see any new service even after adding dbus-sensors.
> Please can you point to any platform in upstream that I can refer to?

https://github.com/openbmc/meta-intel/blob/daa333d956ad9391abcbb85468d9bc9f26ee1190/meta-common/recipes-intel/packagegroups/packagegroup-intel-apps.bb#L43

https://github.com/openbmc/meta-facebook/blob/master/meta-tiogapass/recipes-fbtp/packagegroups/packagegroup-fb-apps.bb

If you do a ps do you see any of the sensor daemons running?

root@intel-obmc:~# ps | grep -i sensor
   332 root      6008 S    /usr/bin/adcsensor
   333 root      6356 S    /usr/bin/cpusensor
   334 root      5784 S    /usr/bin/exitairtempsensor
   335 root      5696 S    /usr/bin/fansensor
   336 root      5608 S    /usr/bin/hwmontempsensor
   337 root      5660 S    intrusionsensor
   339 root      5716 S    /usr/bin/ipmbsensor
   340 root      5512 S    /usr/bin/mcutempsensor
   341 root      5868 S    /usr/bin/psusensor
   588 root      2776 S    grep -i sensor
root@intel-obmc:~#


If so then you'll need to add entity-manager configurations like these:

https://github.com/openbmc/entity-manager/blob/7d807754cc9153b04b599804464edd9654d7a81e/configurations/WFT%20Baseboard.json#L2023

Thanks

James




> 
> Thanks,
> Raj
> 
> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> On Wednesday, December 4, 2019 10:40 PM, James Feist <james.feist@linux.intel.com> wrote:
> 
>> On 12/4/19 1:39 AM, rgrs wrote:
>>
>>> Hi James,
>>> I tried busctl set-property, but the values didn't change.
>>> Are the steps below correct?
>>> (test with both 'field mode' enabled and disabled)
>>> root@obmc:~# busctl introspect xyz.openbmc_project.Hwmon-2439434288.Hwmon1 /xyz/openbmc_project/sensors/temperature/INLET_TEMP xyz.openbmc_project.Sensor.Value --no-pager
>>> NAME TYPE SIGNATURE RESULT/VALUE FLAGS
>>> .MaxValue property x 0 emits-change writable
>>> .MinValue property x 0 emits-change writable
>>> .Scale property x -3 emits-change writable
>>> .Unit property s "xyz.openbmc_project.Sensor.Value.Unit.… emits-change writable
>>
>> This looks like phosphor-hwmon, not dbus-sensors
>> https://github.com/openbmc/dbus-sensors.
>>
>>> .Value property x 18500 emits-change writable
>>> root@obmc:~# busctl --no-pager set-property xyz.openbmc_project.Hwmon-2439434288.Hwmon1 /xyz/openbmc_project/sensors/temperature/INLET_TEMP xyz.openbmc_project.Sensor.Value Value x 50000
>>> root@saber:~# busctl --no-pager get-property xyz.openbmc_project.Hwmon-2439434288.Hwmon1 /xyz/openbmc_project/sensors/temperature/INLET_TEMP xyz.openbmc_project.Sensor.Value Value
>>> x 18500
>>> root@obmc:~#
>>> Thanks,
>>> Raj
>>> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
>>> On Wednesday, December 4, 2019 1:34 AM, James Feist james.feist@linux.intel.com wrote:
>>>> On 12/3/19 5:49 AM, Alexander Amelkin wrote:
>>>>
>>>>> 03.12.2019 15:06, rgrs wrote:
>>>>>
>>>>>> Hi,
>>>>>> How do I fake sensor readings in OpenBMC?
>>>>>> We're trying to fake temperature sensors and make sure fans ramp up/down
>>>>>> accordingly.
>>>>>
>>>>> We ended up patching the kernel driver to fake the readings by request.
>>>>> I'm not aware of any ready interface in OpenBMC for that.
>>>>
>>>> If you're using d-bus sensors, the sensor property is writable. It is
>>>> also supported by patching the sensor value in redfish.
>>>>
>>>>> With best regards,
>>>>> Alexander Amelkin
>>> /james.feist@linux.intel.com
> 
> 

  reply	other threads:[~2019-12-09 18:28 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-03 12:06 Faking Sensor Readings rgrs
2019-12-03 13:49 ` Alexander Amelkin
2019-12-03 20:04   ` James Feist
2019-12-04  9:39     ` rgrs
2019-12-04 17:10       ` James Feist
2019-12-06 11:32         ` rgrs
2019-12-09 18:28           ` James Feist [this message]
2019-12-11  9:14             ` rgrs
2019-12-11 17:29               ` James Feist
2019-12-12  5:28                 ` rgrs
2019-12-12 15:57                   ` James Feist
2019-12-13  6:06                     ` rgrs

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=e59e36d1-74fc-5f44-a472-26fdfb127af2@linux.intel.com \
    --to=james.feist@linux.intel.com \
    --cc=a.amelkin@yadro.com \
    --cc=openbmc@lists.ozlabs.org \
    --cc=rgrs@protonmail.com \
    --cc=richard.marian.thomaiyar@linux.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 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.