On 10/08, Rajendra Nayak wrote:
> @@ -3520,11 +3522,26 @@ static int gcc_msm8960_probe(struct platform_device
> *pdev)
> if (IS_ERR(clk))
> return PTR_ERR(clk);
>
> - return qcom_cc_probe(pdev, match->data);
> + ret = qcom_cc_probe(pdev, match->data);
> + if
On 10/08/2015 11:35 AM, Stephen Boyd wrote:
> On 10/08, Rajendra Nayak wrote:
>> @@ -3520,11 +3522,26 @@ static int gcc_msm8960_probe(struct platform_device
>> *pdev)
>> if (IS_ERR(clk))
>> return PTR_ERR(clk);
>>
>> -return qcom_cc_probe(pdev, match->data);
>> +ret
On 10/07, Stephen Boyd wrote:
> On 10/08, Rajendra Nayak wrote:
>
> I've also been considering putting some devm stuff inside
> qcom_cc_probe() itself so that in the normal case you don't even
> need to call qcom_cc_remove(), it just gets done automatically.
> That would open up the possibility
On 10/08, Rajendra Nayak wrote:
> 8960 family of devices have TSENS as part of GCC in hardware.
> Hence DT would represent a GCC node with GCC properties as well
> as TSENS. Create a virtual platform child device here for TSENS
> so the driver can probe it and use the parent (GCC) to extract DT
>
