From: b.zolnierkie@samsung.com (Bartlomiej Zolnierkiewicz)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2 08/11] opp: Add OPP sharing information to OPP library
Date: Mon, 27 Jul 2015 16:48:59 +0200 [thread overview]
Message-ID: <1564699.gQjhqzf5VE@amdc1976> (raw)
In-Reply-To: <f92bd33dcaa2094dfc99aa9656487c6f08f160fe.1437972635.git.viresh.kumar@linaro.org>
Hi,
Two very minor nits:
On Monday, July 27, 2015 10:32:38 AM Viresh Kumar wrote:
> An opp can be shared by multiple devices, for example its very common
> for CPUs to share the OPPs, i.e. when they share clock/voltage rails.
>
> This patch adds support of shared OPPs to the OPP library.
>
> Instead of a single device, dev_opp will not contain a list of devices
s/will not/will now/ ?
> that use it. It also senses if the device (we are trying to initialize
> OPPs for) shares OPPs with a device added earlier and in that case we
> update the list of devices managed by OPPs instead of duplicating OPPs
> again.
>
> The same infrastructure will be used for the old OPP bindings, with
> later patches.
>
> Reviewed-by: Stephen Boyd <sboyd@codeaurora.org>
> Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
[...]
> +static struct device_list_opp *_add_list_dev(const struct device *dev,
> + struct device_opp *dev_opp)
> +{
> + struct device_list_opp *list_dev;
> +
> + list_dev = kzalloc(sizeof(*list_dev), GFP_KERNEL);
> + if (!list_dev)
> + return NULL;
> +
> + /* Initialize list-dev */
> + list_add_rcu(&list_dev->node, &dev_opp->dev_list);
> + list_dev->dev = dev;
Probably doesn't matter currently but how's about:
list_dev->dev = dev;
list_add_rcu(&list_dev->node, &dev_opp->dev_list);
?
> +
> + return list_dev;
> +}
Otherwise:
Reviewed-by: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
Best regards,
--
Bartlomiej Zolnierkiewicz
Samsung R&D Institute Poland
Samsung Electronics
next prev parent reply other threads:[~2015-07-27 14:48 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-27 5:02 [PATCH V2 00/11] OPP: Add code to support operating-points-v2 bindings Viresh Kumar
2015-07-27 5:02 ` [PATCH V2 01/11] opp: Create a directory for opp bindings Viresh Kumar
2015-07-27 5:02 ` [PATCH V2 02/11] opp: Relocate few routines Viresh Kumar
2015-07-27 5:02 ` [PATCH V2 03/11] OPP: Create _remove_device_opp() for freeing dev_opp Viresh Kumar
2015-07-27 5:02 ` [PATCH V2 04/11] OPP: Allocate dev_opp from _add_device_opp() Viresh Kumar
2015-07-27 5:02 ` [PATCH V2 05/11] OPP: Break _opp_add_dynamic() into smaller functions Viresh Kumar
2015-07-27 5:02 ` [PATCH V2 06/11] opp: Add support to parse "operating-points-v2" bindings Viresh Kumar
2015-07-27 14:23 ` Bartlomiej Zolnierkiewicz
2015-07-27 5:02 ` [PATCH V2 07/11] OPP: Add clock-latency-ns support Viresh Kumar
2015-07-27 14:27 ` Bartlomiej Zolnierkiewicz
2015-07-27 5:02 ` [PATCH V2 08/11] opp: Add OPP sharing information to OPP library Viresh Kumar
2015-07-27 14:48 ` Bartlomiej Zolnierkiewicz [this message]
2015-07-28 2:11 ` Viresh Kumar
2015-07-27 5:02 ` [PATCH V2 09/11] OPP: Add support for opp-suspend Viresh Kumar
2015-07-27 14:50 ` Bartlomiej Zolnierkiewicz
2015-07-27 5:02 ` [PATCH V2 10/11] opp: Add helpers for initializing CPU OPPs Viresh Kumar
2015-07-27 16:37 ` Bartlomiej Zolnierkiewicz
2015-07-27 5:02 ` [PATCH V2 11/11] cpufreq-dt: Add support for operating-points-v2 bindings Viresh Kumar
2015-07-27 16:50 ` Bartlomiej Zolnierkiewicz
2015-07-27 13:39 ` [PATCH V2 00/11] OPP: Add code to support " Rafael J. Wysocki
2015-07-27 14:34 ` Viresh Kumar
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=1564699.gQjhqzf5VE@amdc1976 \
--to=b.zolnierkie@samsung.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).