From: Georgi Djakov <georgi.djakov@linaro.org>
To: Evan Green <evgreen@chromium.org>
Cc: linux-pm@vger.kernel.org, gregkh@linuxfoundation.org,
rjw@rjwysocki.net, robh+dt@kernel.org,
Michael Turquette <mturquette@baylibre.com>,
khilman@baylibre.com,
Vincent Guittot <vincent.guittot@linaro.org>,
Saravana Kannan <skannan@codeaurora.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
amit.kucheria@linaro.org, seansw@qti.qualcomm.com,
daidavid1@codeaurora.org, mark.rutland@arm.com,
lorenzo.pieralisi@arm.com,
Alexandre Bailon <abailon@baylibre.com>,
maxime.ripard@bootlin.com, Arnd Bergmann <arnd@arndb.de>,
thierry.reding@gmail.com, ksitaraman@nvidia.com,
sanjayc@nvidia.com, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-arm-msm@vger.kernel.org, linux-tegra@vger.kernel.org
Subject: Re: [PATCH v10 3/7] interconnect: Allow endpoints translation via DT
Date: Wed, 5 Dec 2018 17:59:34 +0200 [thread overview]
Message-ID: <5590be39-de5a-f962-3d6f-835552e5956f@linaro.org> (raw)
In-Reply-To: <CAE=gft5Z7-Ri07iZesq57bqLpsStvJF3y_TSm+Cz=h-pGqJzyw@mail.gmail.com>
Hi Evan,
On 12/1/18 02:38, Evan Green wrote:
> On Tue, Nov 27, 2018 at 10:04 AM Georgi Djakov <georgi.djakov@linaro.org> wrote:
>>
>> Currently we support only platform data for specifying the interconnect
>> endpoints. As now the endpoints are hard-coded into the consumer driver
>> this may lead to complications when a single driver is used by multiple
>> SoCs, which may have different interconnect topology.
>> To avoid cluttering the consumer drivers, introduce a translation function
>> to help us get the board specific interconnect data from device-tree.
>>
>> Signed-off-by: Georgi Djakov <georgi.djakov@linaro.org>
>> ---
>> drivers/interconnect/core.c | 156 ++++++++++++++++++++++++++
>> include/linux/interconnect-provider.h | 17 +++
>> include/linux/interconnect.h | 7 ++
>> 3 files changed, 180 insertions(+)
>>
>> diff --git a/drivers/interconnect/core.c b/drivers/interconnect/core.c
>> index 3ae8e5a58969..ebc42ef9fa46 100644
>> --- a/drivers/interconnect/core.c
>> +++ b/drivers/interconnect/core.c
>> @@ -15,6 +15,7 @@
>> #include <linux/module.h>
>> #include <linux/mutex.h>
>> #include <linux/slab.h>
>> +#include <linux/of.h>
>> #include <linux/overflow.h>
>>
>> static DEFINE_IDR(icc_idr);
>> @@ -193,6 +194,159 @@ static int apply_constraints(struct icc_path *path)
>> return ret;
>> }
>>
>> +/* of_icc_xlate_onecell() - Xlate function using a single index.
>
> It would be nice if translate were spelled out instead of xlate in the
> description portion (throughout).
Ok, done.
>> + * @spec: OF phandle args to map into an interconnect node.
>> + * @data: private data (pointer to struct icc_onecell_data)
>> + *
>> + * This is a generic xlate function that can be used to model simple
>> + * interconnect providers that have one device tree node and provide
>> + * multiple interconnect nodes. A single cell is used as an index into
>> + * an array of icc nodes specified in the icc_onecell_data struct when
>> + * registering the provider.
>> + */
[..]
>> +/**
>> + * of_icc_get() - get a path handle from a DT node based on name
>> + * @dev: device pointer for the consumer device
>> + * @name: interconnect path name
>> + *
>> + * This function will search for a path two endpoints and return an
>
> path between two endpoints
>
Ok.
>> + * icc_path handle on success. Use icc_put() to release constraints when
>> + * they are not needed anymore.
>> + * If the interconnect API is disabled, NULL is returned and the consumer
>> + * drivers will still build. Drivers are free to handle this specifically,
>> + * but they don't have to. NULL is also returned when the "interconnects"
>
> I'm not sure the sentence starting with "Drivers are free" adds much.
> Also, you mention that null is returned when the interconnect API is
> disabled both above and below. We probably only need it once.
>
So it depends on the driver how to handle it. If an enabled interconnect
is a hard requirement for a driver to work, it can choose to fail. If it
is optional, the driver can succeed and continue and all bandwidth
requests will be silently ignored.
>> + * DT property is missing.
>> + *
>> + * Return: icc_path pointer on success or ERR_PTR() on error. NULL is returned
>> + * when the API is disabled or the "interconnects" DT property is missing.
>> + */
>> +struct icc_path *of_icc_get(struct device *dev, const char *name)
>> +{
>> + struct icc_path *path = ERR_PTR(-EPROBE_DEFER);
>> + struct icc_node *src_node, *dst_node;
>> + struct device_node *np = NULL;
>> + struct of_phandle_args src_args, dst_args;
>> + int idx = 0;
>> + int ret;
>> +
>> + if (!dev || !dev->of_node)
>> + return ERR_PTR(-ENODEV);
>> +
>> + np = dev->of_node;
>> +
>> + /*
>> + * When the consumer DT node do not have "interconnects" property
>> + * return a NULL path to skip setting constraints.
>> + */
>> + if (!of_find_property(np, "interconnects", NULL))
>> + return NULL;
>> +
>> + /*
>> + * We use a combination of phandle and specifier for endpoint. For now
>> + * lets support only global ids and extend this is the future if needed
>
> s/is the future/in the future/
Ok.
>> + * without breaking DT compatibility.
>> + */
>> + if (name) {
>> + idx = of_property_match_string(np, "interconnect-names", name);
>> + if (idx < 0)
>> + return ERR_PTR(idx);
>> + }
>> +
>> + ret = of_parse_phandle_with_args(np, "interconnects",
>> + "#interconnect-cells", idx * 2,
>> + &src_args);
>> + if (ret)
>> + return ERR_PTR(ret);
>> +
>> + of_node_put(src_args.np);
>> +
>> + if (!src_args.args_count || src_args.args_count > 1)
>
> This could be src_args.argc_count != 1
>
>> + return ERR_PTR(-EINVAL);
>> +
>> + ret = of_parse_phandle_with_args(np, "interconnects",
>> + "#interconnect-cells", idx * 2 + 1,
>> + &dst_args);
>> + if (ret)
>> + return ERR_PTR(ret);
>> +
>> + of_node_put(dst_args.np);
>> +
>> + if (!dst_args.args_count || dst_args.args_count > 1)
>
> Similarly, this could be dst_args.args_count != 1
Yes, and actually it might be even better if i move these checks to
of_icc_get_from_provider().
>> + return ERR_PTR(-EINVAL);
>> +
>> + src_node = of_icc_get_from_provider(&src_args);
>> +
>> + if (IS_ERR(src_node)) {
>> + if (PTR_ERR(src_node) != -EPROBE_DEFER)
>> + dev_err(dev, "error finding src node: %ld\n",
>> + PTR_ERR(src_node));
>> + return ERR_CAST(src_node);
>> + }
>> +
>> + dst_node = of_icc_get_from_provider(&dst_args);
>> +
[..]>
> With these nits fixed:
>
> Reviewed-by: Evan Green <evgreen@chromium.org>
>
Thanks,
Georgi
next prev parent reply other threads:[~2018-12-05 15:59 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-27 18:03 [PATCH v10 0/8] Introduce on-chip interconnect API Georgi Djakov
2018-11-27 18:03 ` [PATCH v10 1/7] interconnect: Add generic " Georgi Djakov
2018-11-27 18:35 ` Joe Perches
2018-11-28 18:18 ` Georgi Djakov
2018-12-01 0:38 ` Evan Green
2018-12-05 15:57 ` Georgi Djakov
2018-12-05 16:16 ` Rob Herring
2018-12-07 15:24 ` Georgi Djakov
2018-11-27 18:03 ` [PATCH v10 2/7] dt-bindings: Introduce interconnect binding Georgi Djakov
2018-12-01 0:38 ` Evan Green
2018-11-27 18:03 ` [PATCH v10 3/7] interconnect: Allow endpoints translation via DT Georgi Djakov
2018-12-01 0:38 ` Evan Green
2018-12-05 15:59 ` Georgi Djakov [this message]
2018-11-27 18:03 ` [PATCH v10 4/7] interconnect: Add debugfs support Georgi Djakov
2018-11-27 18:03 ` [PATCH v10 5/7] interconnect: qcom: Add sdm845 interconnect provider driver Georgi Djakov
2018-12-01 0:39 ` Evan Green
2018-12-05 16:00 ` Georgi Djakov
2018-12-06 21:53 ` David Dai
2018-11-27 18:03 ` [PATCH v10 6/7] arm64: dts: sdm845: Add interconnect provider DT nodes Georgi Djakov
2018-12-01 0:39 ` Evan Green
2018-12-05 16:01 ` Georgi Djakov
2018-11-27 18:03 ` [PATCH v10 7/7] MAINTAINERS: add a maintainer for the interconnect API Georgi Djakov
2018-12-05 20:41 ` [PATCH v10 0/8] Introduce on-chip " Evan Green
2018-12-06 14:55 ` Greg KH
2018-12-07 10:06 ` Georgi Djakov
2018-12-10 9:04 ` Rafael J. Wysocki
2018-12-10 10:18 ` Georgi Djakov
2018-12-10 11:00 ` Rafael J. Wysocki
2018-12-10 14:50 ` Georgi Djakov
2018-12-11 6:58 ` Greg Kroah-Hartman
2018-12-17 11:17 ` Georgi Djakov
2019-01-10 14:19 ` Georgi Djakov
2019-01-10 16:29 ` Greg Kroah-Hartman
2019-01-10 16:34 ` Georgi Djakov
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=5590be39-de5a-f962-3d6f-835552e5956f@linaro.org \
--to=georgi.djakov@linaro.org \
--cc=abailon@baylibre.com \
--cc=amit.kucheria@linaro.org \
--cc=arnd@arndb.de \
--cc=bjorn.andersson@linaro.org \
--cc=daidavid1@codeaurora.org \
--cc=devicetree@vger.kernel.org \
--cc=evgreen@chromium.org \
--cc=gregkh@linuxfoundation.org \
--cc=khilman@baylibre.com \
--cc=ksitaraman@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=mark.rutland@arm.com \
--cc=maxime.ripard@bootlin.com \
--cc=mturquette@baylibre.com \
--cc=rjw@rjwysocki.net \
--cc=robh+dt@kernel.org \
--cc=sanjayc@nvidia.com \
--cc=seansw@qti.qualcomm.com \
--cc=skannan@codeaurora.org \
--cc=thierry.reding@gmail.com \
--cc=vincent.guittot@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;
as well as URLs for NNTP newsgroup(s).