From: Viresh Kumar <email@example.com> To: Hsin-Yi Wang <firstname.lastname@example.org> Cc: Viresh Kumar <email@example.com>, firstname.lastname@example.org, Nishanth Menon <email@example.com>, Stephen Boyd <firstname.lastname@example.org>, "Rafael J . Wysocki" <email@example.com>, firstname.lastname@example.org, "MyungJoo Ham )" <email@example.com>, Kyungmin Park <firstname.lastname@example.org>, Chanwoo Choi <email@example.com>, Saravana Kannan <firstname.lastname@example.org> Subject: Re: [PATCH v5 0/3] Add required-opps support to devfreq passive gov Date: Thu, 4 Feb 2021 11:11:33 +0530 [thread overview] Message-ID: <20210204054133.sb6vymf56u43bpwe@vireshk-i7> (raw) In-Reply-To: <email@example.com> On 03-02-21, 17:23, Hsin-Yi Wang wrote: > The devfreq passive governor scales the frequency of a "child" device based > on the current frequency of a "parent" device (not parent/child in the > sense of device hierarchy). As of today, the passive governor requires one > of the following to work correctly: > 1. The parent and child device have the same number of frequencies > 2. The child device driver passes a mapping function to translate from > parent frequency to child frequency. > > When (1) is not true, (2) is the only option right now. But often times, > all that is required is a simple mapping from parent's frequency to child's > frequency. > > Since OPPs already support pointing to other "required-opps", add support > for using that to map from parent device frequency to child device > frequency. That way, every child device driver doesn't have to implement a > separate mapping function anytime (1) isn't true. So you guys aren't interested in dev_pm_opp_set_opp() but just the translation of the required-OPPs ? I am fine with most of the stuff and I would like to take it via OPP tree, hope that would be fine ? -- viresh
next prev parent reply other threads:[~2021-02-04 5:42 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <CGME20210203092602epcas1p1550c96a2ed1b0b6d0a0f9f750cb76e45@epcas1p1.samsung.com> 2021-02-03 9:23 ` Hsin-Yi Wang 2021-02-03 9:23 ` [PATCH v5 1/3] OPP: Add function to look up required OPP's for a given OPP Hsin-Yi Wang 2021-02-04 5:46 ` Viresh Kumar 2021-02-03 9:23 ` [PATCH v5 2/3] PM / devfreq: Cache OPP table reference in devfreq Hsin-Yi Wang 2021-02-03 9:24 ` [PATCH v5 3/3] PM / devfreq: Add required OPPs support to passive governor Hsin-Yi Wang 2021-02-04 2:49 ` Viresh Kumar 2021-02-04 7:07 ` Hsin-Yi Wang 2021-02-03 10:12 ` [PATCH v5 0/3] Add required-opps support to devfreq passive gov Chanwoo Choi 2021-02-04 5:41 ` Viresh Kumar [this message] 2021-02-04 8:12 ` Hsin-Yi Wang 2021-02-04 8:53 ` Chanwoo Choi
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=20210204054133.sb6vymf56u43bpwe@vireshk-i7 \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: [PATCH v5 0/3] Add required-opps support to devfreq passive gov' \ /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
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.