[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20d38311-ce10-4d4e-996b-24f79c051f69@quicinc.com>
Date: Tue, 27 Aug 2024 12:21:51 +0530
From: Sricharan Ramabadhran <quic_srichara@...cinc.com>
To: Krzysztof Kozlowski <krzk@...nel.org>
CC: <bhelgaas@...gle.com>, <lpieralisi@...nel.org>, <kw@...ux.com>,
<manivannan.sadhasivam@...aro.org>, <robh@...nel.org>,
<krzk+dt@...nel.org>, <conor+dt@...nel.org>, <vkoul@...nel.org>,
<kishon@...nel.org>, <andersson@...nel.org>, <konradybcio@...nel.org>,
<p.zabel@...gutronix.de>, <dmitry.baryshkov@...aro.org>,
<quic_nsekar@...cinc.com>, <linux-arm-msm@...r.kernel.org>,
<linux-pci@...r.kernel.org>, <devicetree@...r.kernel.org>,
<linux-kernel@...r.kernel.org>, <linux-phy@...ts.infradead.org>,
<robimarko@...il.com>
Subject: Re: [PATCH V2 3/6] phy: qcom: Introduce PCIe UNIPHY 28LP driver
On 8/27/2024 11:55 AM, Krzysztof Kozlowski wrote:
> On Tue, Aug 27, 2024 at 10:27:54AM +0530, Sricharan R wrote:
>> From: Nitheesh Sekar <quic_nsekar@...cinc.com>
>>
>> Add Qualcomm PCIe UNIPHY 28LP driver support present
>> in Qualcomm IPQ5018 SoC and the phy init sequence.
>>
>> Signed-off-by: Nitheesh Sekar <quic_nsekar@...cinc.com>
>> Signed-off-by: Sricharan Ramabadhran <quic_srichara@...cinc.com>
>
> ...
>
>> +static int qcom_uniphy_pcie_probe(struct platform_device *pdev)
>> +{
>> + struct qcom_uniphy_pcie *phy;
>> + int ret;
>> + struct phy *generic_phy;
>> + struct phy_provider *phy_provider;
>> + struct device *dev = &pdev->dev;
>> + struct device_node *np = of_node_get(dev->of_node);
>> +
>> + phy = devm_kzalloc(&pdev->dev, sizeof(*phy), GFP_KERNEL);
>> + if (!phy)
>> + return -ENOMEM;
>> +
>> + platform_set_drvdata(pdev, phy);
>> + phy->dev = &pdev->dev;
>> +
>> + phy->data = of_device_get_match_data(dev);
>> + if (!phy->data)
>> + return -EINVAL;
>> +
>> + ret = qcom_uniphy_pcie_get_resources(pdev, phy);
>> + if (ret < 0)
>> + dev_err_probe(&pdev->dev, ret, "Failed to get resources:\n");
>
> What the hell happened here? Read my review one more time and then git
> grep for usage of dev_err_probe.
>
Ho ok, understood, missed it, will fix and resend.
Regards,
Sricharan
> NAK.
>
> Best regards,
> Krzysztof
>
>
Powered by blists - more mailing lists