From: Dietmar Eggemann <dietmar.eggemann@arm.com>
To: Lukasz Luba <lukasz.luba@arm.com>,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
rafael@kernel.org
Cc: linux-arm-kernel@lists.infradead.org, sboyd@kernel.org,
nm@ti.com, linux-samsung-soc@vger.kernel.org,
daniel.lezcano@linaro.org, viresh.kumar@linaro.org,
krzysztof.kozlowski@linaro.org, alim.akhtar@samsung.com,
m.szyprowski@samsung.com, mhiramat@kernel.org
Subject: Re: [PATCH v4 1/4] OPP: OF: Export dev_opp_pm_calc_power() for usage from EM
Date: Wed, 3 Apr 2024 14:07:49 +0200 [thread overview]
Message-ID: <03834bb6-c5dc-4be6-8244-fafb4080d5ac@arm.com> (raw)
In-Reply-To: <20240402155822.505491-2-lukasz.luba@arm.com>
On 02/04/2024 17:58, Lukasz Luba wrote:
[...]
> @@ -539,6 +541,12 @@ static inline void dev_pm_opp_of_unregister_em(struct device *dev)
> {
> }
>
> +static inline int dev_pm_opp_calc_power(struct device *dev, unsigned long *uW,
> + unsigned long *kHz)
This looks like a weird alignment comparing to the adjacent functions.
[...]
next prev parent reply other threads:[~2024-04-03 12:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-02 15:58 [PATCH v4 0/4] Update Energy Model after chip binning adjusted voltages Lukasz Luba
2024-04-02 15:58 ` [PATCH v4 1/4] OPP: OF: Export dev_opp_pm_calc_power() for usage from EM Lukasz Luba
2024-04-03 12:07 ` Dietmar Eggemann [this message]
2024-04-02 15:58 ` [PATCH v4 2/4] PM: EM: Refactor em_adjust_new_capacity() Lukasz Luba
2024-04-02 15:58 ` [PATCH v4 3/4] PM: EM: Add em_dev_update_chip_binning() Lukasz Luba
2024-04-02 15:58 ` [PATCH v4 4/4] soc: samsung: exynos-asv: Update Energy Model after adjusting voltage Lukasz Luba
2024-04-03 12:07 ` Dietmar Eggemann
2024-04-03 12:07 ` [PATCH v4 0/4] Update Energy Model after chip binning adjusted voltages Dietmar Eggemann
2024-04-03 12:36 ` 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=03834bb6-c5dc-4be6-8244-fafb4080d5ac@arm.com \
--to=dietmar.eggemann@arm.com \
--cc=alim.akhtar@samsung.com \
--cc=daniel.lezcano@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=lukasz.luba@arm.com \
--cc=m.szyprowski@samsung.com \
--cc=mhiramat@kernel.org \
--cc=nm@ti.com \
--cc=rafael@kernel.org \
--cc=sboyd@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox