From: Lukasz Luba <lukasz.luba@arm.com>
To: Luis Gerhorst <linux-kernel@luisgerhorst.de>
Cc: linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
dri-devel@lists.freedesktop.org, linux-omap@vger.kernel.org,
linux-mediatek@lists.infradead.org,
linux-arm-msm@vger.kernel.org, linux-imx@nxp.com,
Dietmar.Eggemann@arm.com, cw00.choi@samsung.com,
b.zolnierkie@samsung.com, rjw@rjwysocki.net,
sudeep.holla@arm.com, viresh.kumar@linaro.org, nm@ti.com,
sboyd@kernel.org, rui.zhang@intel.com,
amit.kucheria@verdurent.com, daniel.lezcano@linaro.org,
mingo@redhat.com, peterz@infradead.org, juri.lelli@redhat.com,
vincent.guittot@linaro.org, rostedt@goodmis.org,
qperret@google.com, bsegall@google.com, mgorman@suse.de,
shawnguo@kernel.org, s.hauer@pengutronix.de, festevam@gmail.com,
kernel@pengutronix.de, khilman@kernel.org, agross@kernel.org,
bjorn.andersson@linaro.org, robh@kernel.org,
matthias.bgg@gmail.com, steven.price@arm.com,
tomeu.vizoso@collabora.com, alyssa.rosenzweig@collabora.com,
airlied@linux.ie, daniel@ffwll.ch, liviu.dudau@arm.com,
lorenzo.pieralisi@arm.com, patrick.bellasi@matbug.net,
orjan.eide@arm.com, rdunlap@infradead.org, mka@chromium.org
Subject: Re: [PATCH v6 04/10] PM / EM: add support for other devices than CPUs in Energy Model
Date: Fri, 10 Apr 2020 12:34:56 +0100 [thread overview]
Message-ID: <56053904-0314-340e-fdaa-4a8f649d7b6f@arm.com> (raw)
In-Reply-To: <87ftdboaqr.fsf@luis-debian.luis-debian-domain>
On 4/10/20 12:12 PM, Luis Gerhorst wrote:
>
> Lukasz Luba writes:
>
>> +/**
>> + * em_dev_unregister_perf_domain() - Unregister Energy Model (EM) for
>> a device
>> + * @dev : Device for which the EM is registered
>> + *
>> + * Try to unregister the EM for the specified device (it checks current
>> + * reference counter). The EM for CPUs will not be freed.
>> + */
>> +void em_dev_unregister_perf_domain(struct device *dev)
>> +{
>> + struct em_device *em_dev, *tmp;
>> +
>> + if (IS_ERR_OR_NULL(dev))
>> + return;
>> +
>> + /* We don't support freeing CPU structures in hotplug */
>> + if (_is_cpu_device(dev)) {
>> + dev_dbg_once(dev, "EM: the structures are not going to be
>> removed\n");
>> + return;
>> + }
>> +
>> + mutex_lock(&em_pd_mutex);
>> +
>> + if (list_empty(&em_pd_dev_list)) {
>> + mutex_unlock(&em_pd_mutex);
>> + return;
>> + }
>> +
>> + list_for_each_entry_safe(em_dev, tmp, &em_pd_dev_list,
>> em_dev_list) {
>> + if (em_dev->dev == dev) {
>> + kref_put(&em_dev->kref, _em_release);
>> + break;
>> + }
>> + }
>> +
>> + mutex_unlock(&em_pd_mutex);
>> +}
>> +EXPORT_SYMBOL_GPL(em_dev_unregister_perf_domain);
>
> Ok, so em_dev_unregister_perf_domain() does not support the CPU device
> and a subsequent em_register_perf_domain() will fail with EEXIST.
Correct. At the current mainline Energy Model we don't even have
em_unregister_perf_domain function. I had to introduce it in order
to support other devices which might have drivers loaded/unloaded
as modules.
>
> Is there a way to unregister/change the CPU's energy model during
> runtime without restarting the whole system?
Not for the CPU for now.
It is possible for other devices. When you have i.e. a module driver for
a device and in your code there is a (*active_power)(), then it is
possible to change EM by unloading/loading the module.
For the CPU we don't have this requirement for production code. I will
add you to CC list when something like this would pop-up for a
prototyping/experimentation code. We have been analyzing some options.
Regards,
Lukasz
WARNING: multiple messages have this Message-ID (diff)
From: Lukasz Luba <lukasz.luba@arm.com>
To: Luis Gerhorst <linux-kernel@luisgerhorst.de>
Cc: nm@ti.com, juri.lelli@redhat.com, peterz@infradead.org,
viresh.kumar@linaro.org, liviu.dudau@arm.com,
dri-devel@lists.freedesktop.org, bjorn.andersson@linaro.org,
bsegall@google.com, alyssa.rosenzweig@collabora.com,
festevam@gmail.com, mka@chromium.org, robh@kernel.org,
amit.kucheria@verdurent.com, lorenzo.pieralisi@arm.com,
vincent.guittot@linaro.org, khilman@kernel.org,
agross@kernel.org, daniel.lezcano@linaro.org,
steven.price@arm.com, cw00.choi@samsung.com, mingo@redhat.com,
linux-imx@nxp.com, rui.zhang@intel.com, mgorman@suse.de,
orjan.eide@arm.com, daniel@ffwll.ch, linux-pm@vger.kernel.org,
linux-arm-msm@vger.kernel.org, s.hauer@pengutronix.de,
rostedt@goodmis.org, linux-mediatek@lists.infradead.org,
matthias.bgg@gmail.com, linux-omap@vger.kernel.org,
Dietmar.Eggemann@arm.com, linux-arm-kernel@lists.infradead.org,
airlied@linux.ie, tomeu.vizoso@collabora.com, qperret@google.com,
sboyd@kernel.org, rdunlap@infradead.org, rjw@rjwysocki.net,
linux-kernel@vger.kernel.org, b.zolnierkie@samsung.com,
kernel@pengutronix.de, sudeep.holla@arm.com,
patrick.bellasi@matbug.net, shawnguo@kernel.org
Subject: Re: [PATCH v6 04/10] PM / EM: add support for other devices than CPUs in Energy Model
Date: Fri, 10 Apr 2020 12:34:56 +0100 [thread overview]
Message-ID: <56053904-0314-340e-fdaa-4a8f649d7b6f@arm.com> (raw)
In-Reply-To: <87ftdboaqr.fsf@luis-debian.luis-debian-domain>
On 4/10/20 12:12 PM, Luis Gerhorst wrote:
>
> Lukasz Luba writes:
>
>> +/**
>> + * em_dev_unregister_perf_domain() - Unregister Energy Model (EM) for
>> a device
>> + * @dev : Device for which the EM is registered
>> + *
>> + * Try to unregister the EM for the specified device (it checks current
>> + * reference counter). The EM for CPUs will not be freed.
>> + */
>> +void em_dev_unregister_perf_domain(struct device *dev)
>> +{
>> + struct em_device *em_dev, *tmp;
>> +
>> + if (IS_ERR_OR_NULL(dev))
>> + return;
>> +
>> + /* We don't support freeing CPU structures in hotplug */
>> + if (_is_cpu_device(dev)) {
>> + dev_dbg_once(dev, "EM: the structures are not going to be
>> removed\n");
>> + return;
>> + }
>> +
>> + mutex_lock(&em_pd_mutex);
>> +
>> + if (list_empty(&em_pd_dev_list)) {
>> + mutex_unlock(&em_pd_mutex);
>> + return;
>> + }
>> +
>> + list_for_each_entry_safe(em_dev, tmp, &em_pd_dev_list,
>> em_dev_list) {
>> + if (em_dev->dev == dev) {
>> + kref_put(&em_dev->kref, _em_release);
>> + break;
>> + }
>> + }
>> +
>> + mutex_unlock(&em_pd_mutex);
>> +}
>> +EXPORT_SYMBOL_GPL(em_dev_unregister_perf_domain);
>
> Ok, so em_dev_unregister_perf_domain() does not support the CPU device
> and a subsequent em_register_perf_domain() will fail with EEXIST.
Correct. At the current mainline Energy Model we don't even have
em_unregister_perf_domain function. I had to introduce it in order
to support other devices which might have drivers loaded/unloaded
as modules.
>
> Is there a way to unregister/change the CPU's energy model during
> runtime without restarting the whole system?
Not for the CPU for now.
It is possible for other devices. When you have i.e. a module driver for
a device and in your code there is a (*active_power)(), then it is
possible to change EM by unloading/loading the module.
For the CPU we don't have this requirement for production code. I will
add you to CC list when something like this would pop-up for a
prototyping/experimentation code. We have been analyzing some options.
Regards,
Lukasz
_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek
WARNING: multiple messages have this Message-ID (diff)
From: Lukasz Luba <lukasz.luba@arm.com>
To: Luis Gerhorst <linux-kernel@luisgerhorst.de>
Cc: nm@ti.com, juri.lelli@redhat.com, peterz@infradead.org,
viresh.kumar@linaro.org, liviu.dudau@arm.com,
dri-devel@lists.freedesktop.org, bjorn.andersson@linaro.org,
bsegall@google.com, alyssa.rosenzweig@collabora.com,
festevam@gmail.com, mka@chromium.org, robh@kernel.org,
amit.kucheria@verdurent.com, lorenzo.pieralisi@arm.com,
khilman@kernel.org, agross@kernel.org, daniel.lezcano@linaro.org,
steven.price@arm.com, cw00.choi@samsung.com, mingo@redhat.com,
linux-imx@nxp.com, rui.zhang@intel.com, mgorman@suse.de,
orjan.eide@arm.com, daniel@ffwll.ch, linux-pm@vger.kernel.org,
linux-arm-msm@vger.kernel.org, s.hauer@pengutronix.de,
rostedt@goodmis.org, linux-mediatek@lists.infradead.org,
matthias.bgg@gmail.com, linux-omap@vger.kernel.org,
Dietmar.Eggemann@arm.com, linux-arm-kernel@lists.infradead.org,
airlied@linux.ie, tomeu.vizoso@collabora.com, qperret@google.com,
sboyd@kernel.org, rdunlap@infradead.org, rjw@rjwysocki.net,
linux-kernel@vger.kernel.org, b.zolnierkie@samsung.com,
kernel@pengutronix.de, sudeep.holla@arm.com,
patrick.bellasi@matbug.net, shawnguo@kernel.org
Subject: Re: [PATCH v6 04/10] PM / EM: add support for other devices than CPUs in Energy Model
Date: Fri, 10 Apr 2020 12:34:56 +0100 [thread overview]
Message-ID: <56053904-0314-340e-fdaa-4a8f649d7b6f@arm.com> (raw)
In-Reply-To: <87ftdboaqr.fsf@luis-debian.luis-debian-domain>
On 4/10/20 12:12 PM, Luis Gerhorst wrote:
>
> Lukasz Luba writes:
>
>> +/**
>> + * em_dev_unregister_perf_domain() - Unregister Energy Model (EM) for
>> a device
>> + * @dev : Device for which the EM is registered
>> + *
>> + * Try to unregister the EM for the specified device (it checks current
>> + * reference counter). The EM for CPUs will not be freed.
>> + */
>> +void em_dev_unregister_perf_domain(struct device *dev)
>> +{
>> + struct em_device *em_dev, *tmp;
>> +
>> + if (IS_ERR_OR_NULL(dev))
>> + return;
>> +
>> + /* We don't support freeing CPU structures in hotplug */
>> + if (_is_cpu_device(dev)) {
>> + dev_dbg_once(dev, "EM: the structures are not going to be
>> removed\n");
>> + return;
>> + }
>> +
>> + mutex_lock(&em_pd_mutex);
>> +
>> + if (list_empty(&em_pd_dev_list)) {
>> + mutex_unlock(&em_pd_mutex);
>> + return;
>> + }
>> +
>> + list_for_each_entry_safe(em_dev, tmp, &em_pd_dev_list,
>> em_dev_list) {
>> + if (em_dev->dev == dev) {
>> + kref_put(&em_dev->kref, _em_release);
>> + break;
>> + }
>> + }
>> +
>> + mutex_unlock(&em_pd_mutex);
>> +}
>> +EXPORT_SYMBOL_GPL(em_dev_unregister_perf_domain);
>
> Ok, so em_dev_unregister_perf_domain() does not support the CPU device
> and a subsequent em_register_perf_domain() will fail with EEXIST.
Correct. At the current mainline Energy Model we don't even have
em_unregister_perf_domain function. I had to introduce it in order
to support other devices which might have drivers loaded/unloaded
as modules.
>
> Is there a way to unregister/change the CPU's energy model during
> runtime without restarting the whole system?
Not for the CPU for now.
It is possible for other devices. When you have i.e. a module driver for
a device and in your code there is a (*active_power)(), then it is
possible to change EM by unloading/loading the module.
For the CPU we don't have this requirement for production code. I will
add you to CC list when something like this would pop-up for a
prototyping/experimentation code. We have been analyzing some options.
Regards,
Lukasz
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Lukasz Luba <lukasz.luba@arm.com>
To: Luis Gerhorst <linux-kernel@luisgerhorst.de>
Cc: nm@ti.com, juri.lelli@redhat.com, peterz@infradead.org,
viresh.kumar@linaro.org, liviu.dudau@arm.com,
dri-devel@lists.freedesktop.org, bjorn.andersson@linaro.org,
bsegall@google.com, alyssa.rosenzweig@collabora.com,
mka@chromium.org, amit.kucheria@verdurent.com,
lorenzo.pieralisi@arm.com, vincent.guittot@linaro.org,
khilman@kernel.org, agross@kernel.org, daniel.lezcano@linaro.org,
steven.price@arm.com, cw00.choi@samsung.com, mingo@redhat.com,
linux-imx@nxp.com, rui.zhang@intel.com, mgorman@suse.de,
orjan.eide@arm.com, linux-pm@vger.kernel.org,
linux-arm-msm@vger.kernel.org, s.hauer@pengutronix.de,
rostedt@goodmis.org, linux-mediatek@lists.infradead.org,
matthias.bgg@gmail.com, linux-omap@vger.kernel.org,
Dietmar.Eggemann@arm.com, linux-arm-kernel@lists.infradead.org,
airlied@linux.ie, tomeu.vizoso@collabora.com, qperret@google.com,
sboyd@kernel.org, rdunlap@infradead.org, rjw@rjwysocki.net,
linux-kernel@vger.kernel.org, b.zolnierkie@samsung.com,
kernel@pengutronix.de, sudeep.holla@arm.com,
patrick.bellasi@matbug.net, shawnguo@kernel.org
Subject: Re: [PATCH v6 04/10] PM / EM: add support for other devices than CPUs in Energy Model
Date: Fri, 10 Apr 2020 12:34:56 +0100 [thread overview]
Message-ID: <56053904-0314-340e-fdaa-4a8f649d7b6f@arm.com> (raw)
In-Reply-To: <87ftdboaqr.fsf@luis-debian.luis-debian-domain>
On 4/10/20 12:12 PM, Luis Gerhorst wrote:
>
> Lukasz Luba writes:
>
>> +/**
>> + * em_dev_unregister_perf_domain() - Unregister Energy Model (EM) for
>> a device
>> + * @dev : Device for which the EM is registered
>> + *
>> + * Try to unregister the EM for the specified device (it checks current
>> + * reference counter). The EM for CPUs will not be freed.
>> + */
>> +void em_dev_unregister_perf_domain(struct device *dev)
>> +{
>> + struct em_device *em_dev, *tmp;
>> +
>> + if (IS_ERR_OR_NULL(dev))
>> + return;
>> +
>> + /* We don't support freeing CPU structures in hotplug */
>> + if (_is_cpu_device(dev)) {
>> + dev_dbg_once(dev, "EM: the structures are not going to be
>> removed\n");
>> + return;
>> + }
>> +
>> + mutex_lock(&em_pd_mutex);
>> +
>> + if (list_empty(&em_pd_dev_list)) {
>> + mutex_unlock(&em_pd_mutex);
>> + return;
>> + }
>> +
>> + list_for_each_entry_safe(em_dev, tmp, &em_pd_dev_list,
>> em_dev_list) {
>> + if (em_dev->dev == dev) {
>> + kref_put(&em_dev->kref, _em_release);
>> + break;
>> + }
>> + }
>> +
>> + mutex_unlock(&em_pd_mutex);
>> +}
>> +EXPORT_SYMBOL_GPL(em_dev_unregister_perf_domain);
>
> Ok, so em_dev_unregister_perf_domain() does not support the CPU device
> and a subsequent em_register_perf_domain() will fail with EEXIST.
Correct. At the current mainline Energy Model we don't even have
em_unregister_perf_domain function. I had to introduce it in order
to support other devices which might have drivers loaded/unloaded
as modules.
>
> Is there a way to unregister/change the CPU's energy model during
> runtime without restarting the whole system?
Not for the CPU for now.
It is possible for other devices. When you have i.e. a module driver for
a device and in your code there is a (*active_power)(), then it is
possible to change EM by unloading/loading the module.
For the CPU we don't have this requirement for production code. I will
add you to CC list when something like this would pop-up for a
prototyping/experimentation code. We have been analyzing some options.
Regards,
Lukasz
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2020-04-10 11:35 UTC|newest]
Thread overview: 116+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-10 8:42 [PATCH v6 00/10] Add support for devices in the Energy Model Lukasz Luba
2020-04-10 8:42 ` Lukasz Luba
2020-04-10 8:42 ` Lukasz Luba
2020-04-10 8:42 ` Lukasz Luba
2020-04-10 8:42 ` [PATCH v6 01/10] PM / EM: change naming convention from 'capacity' to 'performance' Lukasz Luba
2020-04-10 8:42 ` Lukasz Luba
2020-04-10 8:42 ` Lukasz Luba
2020-04-10 8:42 ` Lukasz Luba
2020-04-23 9:55 ` Daniel Lezcano
2020-04-23 9:55 ` Daniel Lezcano
2020-04-23 9:55 ` Daniel Lezcano
2020-04-23 9:55 ` Daniel Lezcano
2020-04-10 8:42 ` [PATCH v6 02/10] PM / EM: introduce em_dev_register_perf_domain function Lukasz Luba
2020-04-10 8:42 ` Lukasz Luba
2020-04-10 8:42 ` Lukasz Luba
2020-04-10 8:42 ` Lukasz Luba
2020-04-23 10:46 ` Daniel Lezcano
2020-04-23 10:46 ` Daniel Lezcano
2020-04-23 10:46 ` Daniel Lezcano
2020-04-23 10:46 ` Daniel Lezcano
2020-04-10 8:42 ` [PATCH v6 03/10] PM / EM: update callback structure and add device pointer Lukasz Luba
2020-04-10 8:42 ` Lukasz Luba
2020-04-10 8:42 ` Lukasz Luba
2020-04-10 8:42 ` Lukasz Luba
2020-04-23 13:22 ` Daniel Lezcano
2020-04-23 13:22 ` Daniel Lezcano
2020-04-23 13:22 ` Daniel Lezcano
2020-04-23 13:22 ` Daniel Lezcano
2020-04-23 15:28 ` Lukasz Luba
2020-04-23 15:28 ` Lukasz Luba
2020-04-23 15:28 ` Lukasz Luba
2020-04-23 15:28 ` Lukasz Luba
2020-04-10 8:42 ` [PATCH v6 04/10] PM / EM: add support for other devices than CPUs in Energy Model Lukasz Luba
2020-04-10 8:42 ` Lukasz Luba
2020-04-10 8:42 ` Lukasz Luba
2020-04-10 8:42 ` Lukasz Luba
2020-04-10 11:12 ` Luis Gerhorst
2020-04-10 11:12 ` Luis Gerhorst
2020-04-10 11:12 ` Luis Gerhorst
2020-04-10 11:12 ` Luis Gerhorst
2020-04-10 11:34 ` Lukasz Luba [this message]
2020-04-10 11:34 ` Lukasz Luba
2020-04-10 11:34 ` Lukasz Luba
2020-04-10 11:34 ` Lukasz Luba
2020-04-10 14:35 ` kbuild test robot
2020-04-10 14:35 ` kbuild test robot
2020-04-10 14:35 ` kbuild test robot
2020-04-10 14:35 ` kbuild test robot
2020-04-23 15:12 ` Daniel Lezcano
2020-04-23 15:12 ` Daniel Lezcano
2020-04-23 15:12 ` Daniel Lezcano
2020-04-23 15:12 ` Daniel Lezcano
2020-04-23 16:57 ` Lukasz Luba
2020-04-23 16:57 ` Lukasz Luba
2020-04-23 16:57 ` Lukasz Luba
2020-04-23 16:57 ` Lukasz Luba
2020-04-23 17:15 ` Daniel Lezcano
2020-04-23 17:15 ` Daniel Lezcano
2020-04-23 17:15 ` Daniel Lezcano
2020-04-23 17:15 ` Daniel Lezcano
2020-04-23 17:19 ` Lukasz Luba
2020-04-23 17:19 ` Lukasz Luba
2020-04-23 17:19 ` Lukasz Luba
2020-04-23 17:19 ` Lukasz Luba
2020-04-10 8:42 ` [PATCH v6 05/10] PM / EM: remove em_register_perf_domain Lukasz Luba
2020-04-10 8:42 ` Lukasz Luba
2020-04-10 8:42 ` Lukasz Luba
2020-04-10 8:42 ` Lukasz Luba
2020-04-23 15:14 ` Daniel Lezcano
2020-04-23 15:14 ` Daniel Lezcano
2020-04-23 15:14 ` Daniel Lezcano
2020-04-23 15:14 ` Daniel Lezcano
2020-04-10 8:42 ` [PATCH v6 06/10] PM / EM: change name of em_pd_energy to em_cpu_energy Lukasz Luba
2020-04-10 8:42 ` Lukasz Luba
2020-04-10 8:42 ` Lukasz Luba
2020-04-10 8:42 ` Lukasz Luba
2020-04-23 15:28 ` Daniel Lezcano
2020-04-23 15:28 ` Daniel Lezcano
2020-04-23 15:28 ` Daniel Lezcano
2020-04-23 15:28 ` Daniel Lezcano
2020-04-10 8:42 ` [PATCH v6 07/10] Documentation: power: update Energy Model description Lukasz Luba
2020-04-10 8:42 ` Lukasz Luba
2020-04-10 8:42 ` Lukasz Luba
2020-04-10 8:42 ` Lukasz Luba
2020-04-23 16:07 ` Daniel Lezcano
2020-04-23 16:07 ` Daniel Lezcano
2020-04-23 16:07 ` Daniel Lezcano
2020-04-23 16:07 ` Daniel Lezcano
2020-04-10 8:42 ` [PATCH v6 08/10] OPP: refactor dev_pm_opp_of_register_em() and update related drivers Lukasz Luba
2020-04-10 8:42 ` Lukasz Luba
2020-04-10 8:42 ` Lukasz Luba
2020-04-10 8:42 ` Lukasz Luba
2020-04-23 16:47 ` Daniel Lezcano
2020-04-23 16:47 ` Daniel Lezcano
2020-04-23 16:47 ` Daniel Lezcano
2020-04-23 16:47 ` Daniel Lezcano
2020-04-10 8:42 ` [PATCH v6 09/10] thermal: devfreq_cooling: Refactor code and switch to use Energy Model Lukasz Luba
2020-04-10 8:42 ` Lukasz Luba
2020-04-10 8:42 ` Lukasz Luba
2020-04-10 8:42 ` Lukasz Luba
2020-04-23 17:57 ` Daniel Lezcano
2020-04-23 17:57 ` Daniel Lezcano
2020-04-23 17:57 ` Daniel Lezcano
2020-04-23 17:57 ` Daniel Lezcano
2020-04-24 10:02 ` Lukasz Luba
2020-04-24 10:02 ` Lukasz Luba
2020-04-24 10:02 ` Lukasz Luba
2020-04-24 10:02 ` Lukasz Luba
2020-04-24 10:43 ` Daniel Lezcano
2020-04-24 10:43 ` Daniel Lezcano
2020-04-24 10:43 ` Daniel Lezcano
2020-04-24 10:43 ` Daniel Lezcano
2020-04-10 8:42 ` [PATCH v6 10/10] drm/panfrost: Register devfreq cooling and attempt to add " Lukasz Luba
2020-04-10 8:42 ` Lukasz Luba
2020-04-10 8:42 ` Lukasz Luba
2020-04-10 8:42 ` 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=56053904-0314-340e-fdaa-4a8f649d7b6f@arm.com \
--to=lukasz.luba@arm.com \
--cc=Dietmar.Eggemann@arm.com \
--cc=agross@kernel.org \
--cc=airlied@linux.ie \
--cc=alyssa.rosenzweig@collabora.com \
--cc=amit.kucheria@verdurent.com \
--cc=b.zolnierkie@samsung.com \
--cc=bjorn.andersson@linaro.org \
--cc=bsegall@google.com \
--cc=cw00.choi@samsung.com \
--cc=daniel.lezcano@linaro.org \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=festevam@gmail.com \
--cc=juri.lelli@redhat.com \
--cc=kernel@pengutronix.de \
--cc=khilman@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@luisgerhorst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=liviu.dudau@arm.com \
--cc=lorenzo.pieralisi@arm.com \
--cc=matthias.bgg@gmail.com \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=mka@chromium.org \
--cc=nm@ti.com \
--cc=orjan.eide@arm.com \
--cc=patrick.bellasi@matbug.net \
--cc=peterz@infradead.org \
--cc=qperret@google.com \
--cc=rdunlap@infradead.org \
--cc=rjw@rjwysocki.net \
--cc=robh@kernel.org \
--cc=rostedt@goodmis.org \
--cc=rui.zhang@intel.com \
--cc=s.hauer@pengutronix.de \
--cc=sboyd@kernel.org \
--cc=shawnguo@kernel.org \
--cc=steven.price@arm.com \
--cc=sudeep.holla@arm.com \
--cc=tomeu.vizoso@collabora.com \
--cc=vincent.guittot@linaro.org \
--cc=viresh.kumar@linaro.org \
/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.