From: Ionela Voinescu <ionela.voinescu@arm.com>
To: Lukasz Luba <lukasz.luba@arm.com>
Cc: linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
dri-devel@lists.freedesktop.org, amit.kucheria@verdurent.com,
airlied@linux.ie, daniel.lezcano@linaro.org,
steven.price@arm.com, alyssa.rosenzweig@collabora.com,
rui.zhang@intel.com, orjan.eide@arm.com
Subject: Re: [PATCH 3/5] thermal: devfreq_cooling: add new registration functions with Energy Model
Date: Tue, 1 Dec 2020 15:02:27 +0000 [thread overview]
Message-ID: <20201201150227.GA29042@arm.com> (raw)
In-Reply-To: <a0b70daf-fbd8-928e-36d0-d44d5fd68ca6@arm.com>
On Tuesday 01 Dec 2020 at 14:37:58 (+0000), Lukasz Luba wrote:
>
>
> On 12/1/20 2:05 PM, Ionela Voinescu wrote:
> > Hi,
> >
> > On Thursday 22 Oct 2020 at 12:17:31 (+0100), Lukasz Luba wrote:
> > [..]
> >
> > > > > +/**
> > > > > + * devfreq_cooling_em_register_power() - Register devfreq cooling device with
> > > > > + * power information and attempt to register Energy Model (EM)
> > > >
> > > > It took me a while to understand the differences between devfreq
> > > > register functions and it left me with a nagging feeling that we don't
> > > > need all of them. Also, looking over the cpufreq cooling devices, they
> > > > keep their registering interfaces quite simple.
> > >
> > > This was discussed in previous series, related to EM core changes.
> > > It was requested to have a helper registration function which would
> > > create EM automatically.
> > >
> > > >
> > > > With the functions added by this patch, the devfreq cooling devices will have:
> > > > - old:
> > > > of_devfreq_cooling_register_power
> > > > of_devfreq_cooling_register
> > > > devfreq_cooling_register
> > > > devfreq_cooling_unregister
> > > > - new:
> > > > devfreq_cooling_em_register_power
> > > > devfreq_cooling_em_register
> > > >
> > > > My question is whether we actually need the two new
> > > > devfreq_cooling_em_register_power() and devfreq_cooling_em_register()?
> > >
> > > It is just for consistency, with older scheme. It is only a wrapper, one
> > > line, with default NULL. This scheme is common in thermal and some other
> > > frameworks.
> > >
> > > >
> > > > The power_ops and the em are dependent on one another, so could we
> > > > extend the of_devfreq_cooling_register_power() to do the additional em
> > > > registration. We only need a way to pass the em_cb and I think that
> > > > could fit nicely in devfreq_cooling_power.
> > >
> > > No, they aren't 'dependent on one another'. The EM usage doesn't depend
> > > on presence of power_ops. Drivers might not support power_ops, but want
> > > the framework still use EM and do power estimation.
> > >
> >
> > Okay, wrong choice of words. There's only a one way dependency: you can't
> > use power_ops without an em, according to
> > of_devfreq_cooling_register_power().
> >
> > Correct me if I'm wrong, but I see this as being okay as you still need
> > an em to give you the maximum power of a device in a certain state.
> >
> > With this in mind, and taking in detail the possible calls of the
> > devfreq cooling register functions:
> >
> > 1. Register devfreq cooling device with energy model.
> > (used in patch 5/5)
> >
> > -> devfreq_cooling_em_register()
> > -> devfreq_cooling_em_register_power(dfc_power = NULL, em obtained
> > through various methods)
> > -> of_devfreq_cooling_register_power(same as above)
> >
> > 2. Register devfreq cooling device with power_ops and em:
> > (not used)
> >
> > -> devfreq_cooling_em_register_power(dfc_power != NULL, em obtained
> > through various methods)
> > -> of_devfreq_cooling_register_power(same as above)
> >
> > 3. Register a devfreq cooling devices with power_ops but no em
> > (not used)
> >
> > -> of_devfreq_cooling_register_power(dfc_power != NULL)
> >
> >
> > 4. Register a devfreq cooling devices without any kind of power
> > information (em or dfc_power/power_ops)
> >
> > -> devfreq_cooling_register() or of_devfreq_cooling_register()
> > -> of_devfreq_cooling_register_power(dfc_power = NULL)
> >
> >
> > Given this, aren't we ending up with some possible calls to these
> > registration functions that don't make sense? That is case 3, as
> > of_devfreq_cooling_register_power() could not assign and later use
> > power_ops without an em. For this usecase, 2 should be used instead.
>
> In use case 3. you missed that the driver could registered EM by itself.
> Maybe wanted to manage the EM internally, for various reasons. Then this
> registration use case 3. makes sense.
>
Yes, the code allows it but it would be unlikely.
> >
> > Therefore, can't the same be achieved by collapsing
> > devfreq_cooling_em_register_power() into
> > of_devfreq_cooling_register_power()? (with the user having the
> > possibility to provide the em callback similarly to how get_real_power()
> > is provided - in devfreq_cooling_power).
> >
> > IMO is cleaner to unify the functionality (registration and callbacks)
> > of cooling devices with power capabilities (based on em alone or together
> > with power_ops). Otherwise we just create confusion for users registering
> > cooling devices not knowing which function to call.
>
> I don't want to add the code from devfreq_cooling_em_register_power()
> into the of_devfreq_cooling_register_power(), these are pretty dense
> functions with complicated error handling paths.
> In this shape and a few wrappers, which help users to register according
> to their needs, it looks OK.
>
> There will be always a review of the coming drivers which would like to
> register.
>
Okay, no other arguments from my part.
I'll now take a look over v2. I just wanted to get some of these design
choices out of the way first.
Thanks,
Ionela.
> >
> > If this has been discussed previously and I'm missing some details,
> > please provide some links to the discussions.
> >
> > Thank you for the patience :).
> >
> > Ionela.
> >
next prev parent reply other threads:[~2020-12-01 15:03 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-21 12:20 [PATCH 0/5] Thermal devfreq cooling improvements with Energy Model Lukasz Luba
2020-09-21 12:20 ` [PATCH 1/5] thermal: devfreq_cooling: change tracing function and arguments Lukasz Luba
2020-09-21 12:20 ` [PATCH 2/5] thermal: devfreq_cooling: get a copy of device status Lukasz Luba
2020-10-07 16:11 ` Ionela Voinescu
2020-10-22 10:55 ` Lukasz Luba
2020-12-01 10:36 ` Ionela Voinescu
2020-12-01 12:19 ` Lukasz Luba
2020-12-01 14:55 ` Ionela Voinescu
2020-10-14 14:34 ` Daniel Lezcano
2020-10-22 11:45 ` Lukasz Luba
2020-09-21 12:20 ` [PATCH 3/5] thermal: devfreq_cooling: add new registration functions with Energy Model Lukasz Luba
2020-10-07 12:07 ` Ionela Voinescu
2020-10-22 11:17 ` Lukasz Luba
2020-12-01 14:05 ` Ionela Voinescu
2020-12-01 14:37 ` Lukasz Luba
2020-12-01 15:02 ` Ionela Voinescu [this message]
2020-09-21 12:20 ` [PATCH 4/5] thermal: devfreq_cooling: remove old power model and use EM Lukasz Luba
2020-10-07 15:12 ` Ionela Voinescu
2020-10-22 11:26 ` Lukasz Luba
2020-09-21 12:20 ` [PATCH 5/5] drm/panfrost: Register devfreq cooling and attempt to add Energy Model Lukasz Luba
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=20201201150227.GA29042@arm.com \
--to=ionela.voinescu@arm.com \
--cc=airlied@linux.ie \
--cc=alyssa.rosenzweig@collabora.com \
--cc=amit.kucheria@verdurent.com \
--cc=daniel.lezcano@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lukasz.luba@arm.com \
--cc=orjan.eide@arm.com \
--cc=rui.zhang@intel.com \
--cc=steven.price@arm.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).