[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <438d21a46fffebdf858c327c92155b5b91646376.camel@mediatek.com>
Date: Tue, 19 Apr 2022 16:15:36 +0800
From: Rex-BC Chen <rex-bc.chen@...iatek.com>
To: Chen-Yu Tsai <wenst@...omium.org>
CC: <mturquette@...libre.com>, <sboyd@...nel.org>,
<matthias.bgg@...il.com>, <p.zabel@...gutronix.de>,
<angelogioacchino.delregno@...labora.com>,
<chun-jie.chen@...iatek.com>, <yong.liang@...iatek.com>,
<runyang.chen@...iatek.com>, <linux-kernel@...r.kernel.org>,
<allen-kh.cheng@...iatek.com>, <linux-clk@...r.kernel.org>,
<linux-arm-kernel@...ts.infradead.org>,
<linux-mediatek@...ts.infradead.org>,
<Project_Global_Chrome_Upstream_Group@...iatek.com>
Subject: Re: [PATCH 3/7] clk: mediatek: reset: Merge and revise reset
register function
On Tue, 2022-04-19 at 15:26 +0800, Chen-Yu Tsai wrote:
> On Mon, Apr 18, 2022 at 9:22 PM Rex-BC Chen <rex-bc.chen@...iatek.com
> > wrote:
> >
> > Merge the reset register function of v1 and v2 into one function.
> > - Input the version number to determine which version we will use.
> > - Add return value of reset register function for error handling.
>
> Please do this in a separate patch. Also you are adding error
> messages
> for when of_clk_add_provider() fails, which is not mentioned either.
>
> Most of these platform drivers require a good cleanup of their error
> handling anyway. It might be a good idea to tackle them later. Or if
> they look the same, you could try using coccinelle to do a bulk
> cleanup.
>
>
> Thanks
> ChenYu
Hello ChenYu,
I will separate the error handle in another patch.
I think I will just add a return value. As for cleanup the clock error
handling flow, it's not the purpose of this series.
BRs,
Rex
>
> > - Rename reset register function to "mtk_clk_register_rst_ctrl"
Powered by blists - more mailing lists