[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ac325385-cb3e-4002-b100-de73eb5a9ac7@kernel.org>
Date: Tue, 8 Oct 2024 16:35:40 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Frank Wang <frawang.cn@...il.com>
Cc: vkoul@...nel.org, kishon@...nel.org, robh@...nel.org, krzk+dt@...nel.org,
conor+dt@...nel.org, heiko@...ech.de, linux-phy@...ts.infradead.org,
devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org, linux-rockchip@...ts.infradead.org,
william.wu@...k-chips.com, tim.chen@...k-chips.com, frank.wang@...k-chips.com
Subject: Re: [PATCH v4 1/3] phy: rockchip: inno-usb2: convert clock management
to bulk
On 08/10/2024 05:07, Frank Wang wrote:
>>> + }
>>> +
>>> + if (!IS_ERR(refclk)) {
>>> + clk_name = __clk_get_name(refclk);
>>> init.parent_names = &clk_name;
>>> init.num_parents = 1;
>>> } else {
>>> @@ -1406,18 +1424,29 @@ static int rockchip_usb2phy_probe(struct platform_device *pdev)
>>> if (IS_ERR(rphy->phy_reset))
>>> return PTR_ERR(rphy->phy_reset);
>>>
>>> - rphy->clk = devm_clk_get_optional_enabled(dev, "phyclk");
>>> - if (IS_ERR(rphy->clk)) {
>>> - return dev_err_probe(&pdev->dev, PTR_ERR(rphy->clk),
>>> + ret = devm_clk_bulk_get_all(dev, &rphy->clks);
>>> + if (ret == -EPROBE_DEFER) {
>> This does not make much sense. Why would you proceed on other critical
>> errors?
>>
>> You want to use optional variant, I guess?
>
> Yes, the clock properties are optional.
And? So are you going to use optional variant of clk get or not? Is it
appropriate? Are you going to improve it?
Best regards,
Krzysztof
Powered by blists - more mailing lists