[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <7d9bb653-5ea6-e2d3-d130-83a9cf2974f5@microchip.com>
Date: Mon, 7 Dec 2020 09:26:01 +0000
From: <Claudiu.Beznea@...rochip.com>
To: <andrew@...n.ch>
CC: <davem@...emloft.net>, <kuba@...nel.org>, <robh+dt@...nel.org>,
<Nicolas.Ferre@...rochip.com>, <linux@...linux.org.uk>,
<paul.walmsley@...ive.com>, <palmer@...belt.com>,
<yash.shah@...ive.com>, <netdev@...r.kernel.org>,
<devicetree@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<linux-riscv@...ts.infradead.org>
Subject: Re: [PATCH 3/7] net: macb: unprepare clocks in case of failure
Hi Andrew,
On 05.12.2020 16:30, Andrew Lunn wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>
> On Fri, Dec 04, 2020 at 02:34:17PM +0200, Claudiu Beznea wrote:
>> Unprepare clocks in case of any failure in fu540_c000_clk_init().
>
> Hi Claudiu
>
> Nice patchset. Simple to understand.
>>
>
>> +err_disable_clocks:
>> + clk_disable_unprepare(*tx_clk);
>
>> + clk_disable_unprepare(*hclk);
>> + clk_disable_unprepare(*pclk);
>> + clk_disable_unprepare(*rx_clk);
>> + clk_disable_unprepare(*tsu_clk);
>
> This looks correct, but it would be more symmetrical to add a
>
> macb_clk_uninit()
>
> function for the four main clocks. I'm surprised it does not already
> exist.
I was in balance b/w added and not added it taking into account that the
disable unprepares are not taking care of all the clocks, in all the
places, in the same way. Anyway, I will add one function for the main
clocks, as you proposed, in the next version.
Thank you for your review,
Claudiu
>
> Andrew
>
Powered by blists - more mailing lists