On Tue 24 Sep 2019 at 13:38, Ankur Tyagi <Ankur.Tyagi@xxxxxxxxxxxxx> wrote:
> Hi,
>
> I am no expert here but just looked at the patch and found few
> discrepancy that I have mentioned inline.
>
[...]
>
> Aren't all functions returning 0 always?
>
Yes, on purpose. This patch is an API conversion to let the init()
callback of the clock ops return an error code or 0.
The patch is not meant to change anything in the prior behavior of the
clock drivers which is why every exit path return 0 with this change.
IOW, yes there are all returning 0 for now, but it will eventually
change.
>> *
>> * @debug_init:Set up type-specific debugfs entries for this clock. This
>> *is called once, after the debugfs directory entry for this
>> @@ -243,7 +247,7 @@ struct clk_ops {
>> struct clk_duty *duty);
>> int(*set_duty_cycle)(struct clk_hw *hw,
>> struct clk_duty *duty);
>> -void(*init)(struct clk_hw *hw);
>> +int(*init)(struct clk_hw *hw);
>> void(*debug_init)(struct clk_hw *hw, struct dentry *dentry);
>> };
>>
>> --
>> 2.21.0
>
> ________________________________
> This email is confidential and may contain information subject to legal privilege. If you are not the intended recipient please advise us of our error by return e-mail then delete this email and any attached files. You may not copy, disclose or use the contents in any way. The views expressed in this email may not be those of Gallagher Group Ltd or subsidiary companies thereof.
> ________________________________
