All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vijay Khemka <vijaykhemka@fb.com>
To: Ed Tanous <ed.tanous@intel.com>, Patrick Venture <venture@google.com>
Cc: "openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>
Subject: Re: pid control configuration
Date: Wed, 15 May 2019 19:21:52 +0000	[thread overview]
Message-ID: <235B9067-D22E-439F-9009-F3D6C2A70993@fb.com> (raw)
In-Reply-To: <b058940e-ae1b-d238-c9b1-885252ba2464@intel.com>



On 5/13/19, 10:32 AM, "Ed Tanous" <ed.tanous@intel.com> wrote:

    On 5/13/19 9:32 AM, Patrick Venture wrote:
    > On Fri, May 10, 2019 at 2:21 PM Vijay Khemka <vijaykhemka@fb.com> wrote:
    >>
    >>
    >>
    >> On 5/6/19, 9:20 AM, "Ed Tanous" <ed.tanous@intel.com> wrote:
    >>
    >>     On 5/2/19 4:24 PM, Vijay Khemka wrote:
    >>     >  My understanding here is pid data are only defined for temp sensors which will generate pwm values for fan.
    >>     >
    >>
    >>     The above is not how phosphor pid control operates.  The temperature
    >>     controllers "request" a given fan RPM, then the fan PID controller
    >>     (which is scanned much more quickly than the temperature controllers)
    >>     attempts to drive the fan to that speed.  This ends up being a two stage
    >>     feedback loop that can perform better than a single PID loop.
    >>
    >> Ed, we are not using cascade control here in facebook. We only use outer loop which gives data for fan to drive.
    >> Is it possible to still run Phosphor pid controller with single loop?
    > 
    > Your cascade PID could be a pass-through -- so that it receives the
    > set-point from the sensor PID and then just sets it directly within
    > that loop..  It may require a new PID controller that is just a
    > pass-through to explicitly exist -- i haven't dove into
    > phosphor-pid-control in a while, but you probably need to write a
    > basically empty PID controller object type.
    > 
    
    +1  That is an option for you.
Ed, please see if following declaration in entity manager would work as I am not defining any pid values here.
        {
            "Class": "fan",
            "Inputs": [
                "MB_FAN0_TACH"
            ],
            "Name": "MB_FAN0_TACH",
            "Outputs": [
                "Pwm 1"
            ],
            "Type": "Pid",
            "Zones": [
                "Pid 1"
            ]
        },
    
    >>
    >> Regards
    >> -Vijay
    >>
    


  reply	other threads:[~2019-05-15 19:22 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-01 22:53 pid control configuration Vijay Khemka
2019-05-01 23:05 ` Ed Tanous
2019-05-01 23:10   ` Patrick Venture
2019-05-01 23:15     ` Patrick Venture
2019-05-02 23:24   ` Vijay Khemka
2019-05-06 16:20     ` Ed Tanous
2019-05-06 18:18       ` Vijay Khemka
2019-05-06 18:54         ` Ed Tanous
2019-05-10 21:20       ` Vijay Khemka
2019-05-13 16:32         ` Patrick Venture
2019-05-13 17:32           ` Ed Tanous
2019-05-15 19:21             ` Vijay Khemka [this message]
2019-05-15 21:50               ` Ed Tanous
2019-05-16  0:07                 ` Vijay Khemka
2019-05-31 21:00                 ` Vijay Khemka
2019-06-03 17:43                   ` Ed Tanous
2019-06-03 18:18                     ` Vijay Khemka

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=235B9067-D22E-439F-9009-F3D6C2A70993@fb.com \
    --to=vijaykhemka@fb.com \
    --cc=ed.tanous@intel.com \
    --cc=openbmc@lists.ozlabs.org \
    --cc=venture@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 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.