All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rajendra Nayak <rnayak@codeaurora.org>
To: Stanimir Varbanov <svarbanov@mm-sol.com>
Cc: sboyd@codeaurora.org, mturquette@linaro.org,
	linux-arm-msm@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, linux-pm@vger.kernel.org,
	georgi.djakov@linaro.org, srinivas.kandagatla@linaro.org,
	sviau@codeaurora.org
Subject: Re: [PATCH v5 09/11] clk: qcom: gdsc: Use PM clocks to control gdsc clocks
Date: Tue, 12 May 2015 08:32:12 +0530	[thread overview]
Message-ID: <55516D34.1000501@codeaurora.org> (raw)
In-Reply-To: <554249AF.6070909@mm-sol.com>

[]
>>
>> +static int gdsc_attach(struct generic_pm_domain *domain, struct device *dev)
>> +{
>> +	int ret;
>> +	struct gdsc *sc = domain_to_gdsc(domain);
>> +	char **con_id;
>> +
>> +	if (!sc->con_ids[0])
>> +		return 0;
>
> Did you test this on your side? It panic kernel badly cause the flexible
> array is not initialised.
>
> Could you revisit the above check. Or you could add below initialisation
> for every gdsc structure in gcc-xxx.c files.

Hey, that does seem like a problem. Not sure how I did not end up
seeing it. I'll fix it up, thanks.

>
> static struct gdsc venus_gdsc = {
> 	.gdscr = 0x4c018,
> 	.pd = {
> 		.name = "venus",
> 	},
> 	.con_ids = { NULL },
> };
>
>
>> +
>> +	ret = pm_clk_create(dev);
>> +	if (ret) {
>> +		dev_err(dev, "pm_clk_create failed %d\n", ret);
>> +		return ret;
>> +	}
>> +
>> +	for (con_id = sc->con_ids; *con_id; con_id++) {
>> +		ret = pm_clk_add(dev, *con_id);
>> +		if (ret) {
>> +			dev_err(dev, "pm_clk_add failed %d\n", ret);
>> +			goto fail;
>> +		}
>> +	}
>> +	return 0;
>> +fail:
>> +	pm_clk_destroy(dev);
>> +	return ret;
>> +};
>> +
>
> <snip>
>
>

-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation

WARNING: multiple messages have this Message-ID (diff)
From: rnayak@codeaurora.org (Rajendra Nayak)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 09/11] clk: qcom: gdsc: Use PM clocks to control gdsc clocks
Date: Tue, 12 May 2015 08:32:12 +0530	[thread overview]
Message-ID: <55516D34.1000501@codeaurora.org> (raw)
In-Reply-To: <554249AF.6070909@mm-sol.com>

[]
>>
>> +static int gdsc_attach(struct generic_pm_domain *domain, struct device *dev)
>> +{
>> +	int ret;
>> +	struct gdsc *sc = domain_to_gdsc(domain);
>> +	char **con_id;
>> +
>> +	if (!sc->con_ids[0])
>> +		return 0;
>
> Did you test this on your side? It panic kernel badly cause the flexible
> array is not initialised.
>
> Could you revisit the above check. Or you could add below initialisation
> for every gdsc structure in gcc-xxx.c files.

Hey, that does seem like a problem. Not sure how I did not end up
seeing it. I'll fix it up, thanks.

>
> static struct gdsc venus_gdsc = {
> 	.gdscr = 0x4c018,
> 	.pd = {
> 		.name = "venus",
> 	},
> 	.con_ids = { NULL },
> };
>
>
>> +
>> +	ret = pm_clk_create(dev);
>> +	if (ret) {
>> +		dev_err(dev, "pm_clk_create failed %d\n", ret);
>> +		return ret;
>> +	}
>> +
>> +	for (con_id = sc->con_ids; *con_id; con_id++) {
>> +		ret = pm_clk_add(dev, *con_id);
>> +		if (ret) {
>> +			dev_err(dev, "pm_clk_add failed %d\n", ret);
>> +			goto fail;
>> +		}
>> +	}
>> +	return 0;
>> +fail:
>> +	pm_clk_destroy(dev);
>> +	return ret;
>> +};
>> +
>
> <snip>
>
>

-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation

  reply	other threads:[~2015-05-12  3:02 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-14 13:12 [PATCH v5 00/11] Add support for QCOM GDSCs Rajendra Nayak
2015-04-14 13:12 ` Rajendra Nayak
2015-04-14 13:12 ` [PATCH v5 01/11] clk: qcom: Add support for GDSCs Rajendra Nayak
2015-04-14 13:12   ` Rajendra Nayak
2015-04-14 13:12 ` [PATCH v5 02/11] clk: qcom: gdsc: Prepare common clk probe to register gdscs Rajendra Nayak
2015-04-14 13:12   ` Rajendra Nayak
2015-04-14 13:12 ` [PATCH v5 03/11] clk: qcom: gdsc: Add GDSCs in msm8916 GCC Rajendra Nayak
2015-04-14 13:12   ` Rajendra Nayak
2015-04-14 13:12 ` [PATCH v5 04/11] clk: qcom: gdsc: Add GDSCs in msm8974 GCC Rajendra Nayak
2015-04-14 13:12   ` Rajendra Nayak
2015-04-14 13:12 ` [PATCH v5 05/11] clk: qcom: gdsc: Add GDSCs in msm8974 MMCC Rajendra Nayak
2015-04-14 13:12   ` Rajendra Nayak
2015-04-14 13:12 ` [PATCH v5 06/11] clk: qcom: gdsc: Add GDSCs in apq8084 GCC Rajendra Nayak
2015-04-14 13:12   ` Rajendra Nayak
2015-04-14 13:12 ` [PATCH v5 07/11] clk: qcom: gdsc: Add GDSCs in apq8084 MMCC Rajendra Nayak
2015-04-14 13:12   ` Rajendra Nayak
2015-04-14 13:12 ` [PATCH v5 08/11] arm: dts: qcom: Add #power-domain-cells property Rajendra Nayak
2015-04-14 13:12   ` Rajendra Nayak
2015-04-24  9:45   ` Ulf Hansson
2015-04-24  9:45     ` Ulf Hansson
2015-04-24 10:55     ` Rajendra Nayak
2015-04-24 10:55       ` Rajendra Nayak
2015-04-24 11:00       ` Rajendra Nayak
2015-04-24 11:00         ` Rajendra Nayak
2015-04-24 15:43       ` Ulf Hansson
2015-04-24 15:43         ` Ulf Hansson
2015-04-27  2:32         ` Rajendra Nayak
2015-04-27  2:32           ` Rajendra Nayak
2015-04-27  7:52           ` Ulf Hansson
2015-04-27  7:52             ` Ulf Hansson
2015-04-27  9:33             ` Rajendra Nayak
2015-04-27  9:33               ` Rajendra Nayak
2015-04-14 13:12 ` [PATCH v5 09/11] clk: qcom: gdsc: Use PM clocks to control gdsc clocks Rajendra Nayak
2015-04-14 13:12   ` Rajendra Nayak
2015-04-30 15:26   ` Stanimir Varbanov
2015-04-30 15:26     ` Stanimir Varbanov
2015-05-12  3:02     ` Rajendra Nayak [this message]
2015-05-12  3:02       ` Rajendra Nayak
2015-04-14 13:12 ` [PATCH v5 10/11] clk: qcom: gdsc: Enable an RCG before turning on the gdsc Rajendra Nayak
2015-04-14 13:12   ` Rajendra Nayak
2015-04-14 13:12 ` [PATCH v5 11/11] clk: qcom: gdsc: Add oxili GDSC for msm8916 Rajendra Nayak
2015-04-14 13:12   ` Rajendra Nayak

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=55516D34.1000501@codeaurora.org \
    --to=rnayak@codeaurora.org \
    --cc=georgi.djakov@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=mturquette@linaro.org \
    --cc=sboyd@codeaurora.org \
    --cc=srinivas.kandagatla@linaro.org \
    --cc=svarbanov@mm-sol.com \
    --cc=sviau@codeaurora.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.