From: Georgi Djakov <georgi.djakov@linaro.org>
To: Sean Paul <sean@poorly.run>, Rob Clark <robdclark@gmail.com>
Cc: dri-devel@lists.freedesktop.org,
Jayant Shekhar <jshekhar@codeaurora.org>,
Sravanthi Kollukuduru <skolluku@codeaurora.org>,
Rob Clark <robdclark@chromium.org>,
David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
Jordan Crouse <jcrouse@codeaurora.org>,
Abhinav Kumar <abhinavk@codeaurora.org>,
Stephen Boyd <swboyd@chromium.org>,
Jeykumar Sankaran <jsanka@codeaurora.org>,
linux-arm-msm@vger.kernel.org, freedreno@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/5] drm/msm/dpu: Integrate interconnect API in MDSS
Date: Wed, 29 May 2019 16:05:05 +0300 [thread overview]
Message-ID: <2ac15174-09f5-7c7f-8ca8-226f8238a115@linaro.org> (raw)
In-Reply-To: <20190513144722.GO17077@art_vandelay>
On 5/13/19 17:47, Sean Paul wrote:
> On Wed, May 08, 2019 at 01:42:12PM -0700, Rob Clark wrote:
>> From: Jayant Shekhar <jshekhar@codeaurora.org>
>>
>> The interconnect framework is designed to provide a
>> standard kernel interface to control the settings of
>> the interconnects on a SoC.
>>
>> The interconnect API uses a consumer/provider-based model,
>> where the providers are the interconnect buses and the
>> consumers could be various drivers.
>>
>> MDSS is one of the interconnect consumers which uses the
>> interconnect APIs to get the path between endpoints and
>> set its bandwidth requirement for the given interconnected
>> path.
>>
>> Changes in v2:
>> - Remove error log and unnecessary check (Jordan Crouse)
>>
>> Changes in v3:
>> - Code clean involving variable name change, removal
>> of extra paranthesis and variables (Matthias Kaehlcke)
>>
>> Changes in v4:
>> - Add comments, spacings, tabs, proper port name
>> and icc macro (Georgi Djakov)
>>
>> Changes in v5:
>> - Commit text and parenthesis alignment (Georgi Djakov)
>>
>> Changes in v6:
>> - Change to new icc_set API's (Doug Anderson)
>>
>> Changes in v7:
>> - Fixed a typo
>>
>> Signed-off-by: Sravanthi Kollukuduru <skolluku@codeaurora.org>
>> Signed-off-by: Jayant Shekhar <jshekhar@codeaurora.org>
>> Signed-off-by: Rob Clark <robdclark@chromium.org>
>> ---
>> drivers/gpu/drm/msm/disp/dpu1/dpu_mdss.c | 49 ++++++++++++++++++++++--
>> 1 file changed, 45 insertions(+), 4 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/msm/disp/dpu1/dpu_mdss.c b/drivers/gpu/drm/msm/disp/dpu1/dpu_mdss.c
>> index 7316b4ab1b85..e3c56ccd7357 100644
>> --- a/drivers/gpu/drm/msm/disp/dpu1/dpu_mdss.c
>> +++ b/drivers/gpu/drm/msm/disp/dpu1/dpu_mdss.c
>> @@ -4,11 +4,15 @@
>> */
>>
>> #include "dpu_kms.h"
>> +#include <linux/interconnect.h>
>>
>> #define to_dpu_mdss(x) container_of(x, struct dpu_mdss, base)
>>
>> #define HW_INTR_STATUS 0x0010
>>
>> +/* Max BW defined in KBps */
>> +#define MAX_BW 6800000
>> +
>> struct dpu_irq_controller {
>> unsigned long enabled_mask;
>> struct irq_domain *domain;
>> @@ -21,8 +25,30 @@ struct dpu_mdss {
>> u32 hwversion;
>> struct dss_module_power mp;
>> struct dpu_irq_controller irq_controller;
>> + struct icc_path *path[2];
>> + u32 num_paths;
>> };
>>
>> +static int dpu_mdss_parse_data_bus_icc_path(struct drm_device *dev,
>> + struct dpu_mdss *dpu_mdss)
>> +{
>> + struct icc_path *path0 = of_icc_get(dev->dev, "mdp0-mem");
>> + struct icc_path *path1 = of_icc_get(dev->dev, "mdp1-mem");
>> +
>> + if (IS_ERR(path0))
>
> of_icc_get can also return NULL, it looks like we also want to guard against
> this case and keep num_paths == 0.
of_icc_get() returns NULL when the interconnect API is not enabled or the DT
properties are not present. In this case, passing a NULL path to the icc
functions is just a nop. So it should be fine either way.
Acked-by: Georgi Djakov <georgi.djakov@linaro.org>
Thanks,
Georgi
next prev parent reply other threads:[~2019-05-29 13:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190508204219.31687-1-robdclark@gmail.com>
2019-05-08 20:42 ` [PATCH 1/5] drm/msm/dpu: clean up references of DPU custom bus scaling Rob Clark
2019-05-13 14:42 ` Sean Paul
2019-05-08 20:42 ` [PATCH 2/5] drm/msm/dpu: Integrate interconnect API in MDSS Rob Clark
2019-05-13 14:47 ` Sean Paul
2019-05-29 13:05 ` Georgi Djakov [this message]
2019-05-08 20:42 ` [PATCH 3/5] dt-bindings: msm/disp: Introduce interconnect bindings for MDSS on SDM845 Rob Clark
2019-05-13 14:48 ` Sean Paul
2019-05-08 20:42 ` [PATCH 4/5] drm/msm/dpu: add icc voting in dpu_mdss_init Rob Clark
2019-05-08 20:42 ` [PATCH 5/5] drm/msm/mdp5: Use the interconnect API Rob Clark
2019-05-13 14:49 ` Sean Paul
2019-05-29 13:08 ` Georgi Djakov
2019-06-18 20:24 [PATCH 0/5] drm/msm: mdp5+dpu interconnect support Rob Clark
2019-06-18 20:24 ` [PATCH 2/5] drm/msm/dpu: Integrate interconnect API in MDSS Rob Clark
2019-06-18 20:42 ` Sean Paul
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=2ac15174-09f5-7c7f-8ca8-226f8238a115@linaro.org \
--to=georgi.djakov@linaro.org \
--cc=abhinavk@codeaurora.org \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=jcrouse@codeaurora.org \
--cc=jsanka@codeaurora.org \
--cc=jshekhar@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robdclark@chromium.org \
--cc=robdclark@gmail.com \
--cc=sean@poorly.run \
--cc=skolluku@codeaurora.org \
--cc=swboyd@chromium.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).