From: "Chunfeng Yun (云春峰)" <Chunfeng.Yun@mediatek.com>
To: "matthias.bgg@gmail.com" <matthias.bgg@gmail.com>,
"frank.li@vivo.com" <frank.li@vivo.com>,
"vkoul@kernel.org" <vkoul@kernel.org>,
"angelogioacchino.delregno@collabora.com"
<angelogioacchino.delregno@collabora.com>,
"kishon@kernel.org" <kishon@kernel.org>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-phy@lists.infradead.org" <linux-phy@lists.infradead.org>,
"linux-mediatek@lists.infradead.org"
<linux-mediatek@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 4/4] phy: mediatek: tphy: Convert to devm_platform_ioremap_resource()
Date: Tue, 11 Jul 2023 08:57:18 +0000 [thread overview]
Message-ID: <c8795995227b3a83e9285d8e87befe6393d97d21.camel@mediatek.com> (raw)
In-Reply-To: <be88f6db-8b07-1767-f48c-24a215006a4f@collabora.com>
On Wed, 2023-07-05 at 12:00 +0200, AngeloGioacchino Del Regno wrote:
>
> External email : Please do not click links or open attachments until
> you have verified the sender or the content.
> Il 05/07/23 11:30, Yangtao Li ha scritto:
> > HI AngeloGioacchino,
> >
> > On 2023/7/5 17:22, AngeloGioacchino Del Regno wrote:
> >> Il 05/07/23 11:01, Yangtao Li ha scritto:
> >>> Use devm_platform_ioremap_resource() to simplify code.
> >>>
> >>> Signed-off-by: Yangtao Li <frank.li@vivo.com>
> >>> ---
> >>> drivers/phy/mediatek/phy-mtk-tphy.c | 10 +++-------
> >>> 1 file changed, 3 insertions(+), 7 deletions(-)
> >>>
> >>> diff --git a/drivers/phy/mediatek/phy-mtk-tphy.c
> >>> b/drivers/phy/mediatek/phy-mtk-tphy.c
> >>> index 0d110e50bbfd..cb7a4e6ea017 100644
> >>> --- a/drivers/phy/mediatek/phy-mtk-tphy.c
> >>> +++ b/drivers/phy/mediatek/phy-mtk-tphy.c
> >>> @@ -1554,7 +1554,6 @@ static int mtk_tphy_probe(struct
> platform_device *pdev)
> >>> struct device_node *np = dev->of_node;
> >>> struct device_node *child_np;
> >>> struct phy_provider *provider;
> >>> - struct resource *sif_res;
> >>> struct mtk_tphy *tphy;
> >>> struct resource res;
> >>> int port, retval;
> >>> @@ -1576,15 +1575,12 @@ static int mtk_tphy_probe(struct
> platform_device *pdev)
> >>> tphy->dev = dev;
> >>> platform_set_drvdata(pdev, tphy);
> >>> - sif_res = platform_get_resource(pdev, IORESOURCE_MEM, 0);
> >>> /* SATA phy of V1 needn't it if not shared with PCIe or USB
> */
> >>> - if (sif_res && tphy->pdata->version == MTK_PHY_V1) {
> >>> + if (tphy->pdata->version == MTK_PHY_V1) {
> >>> /* get banks shared by multiple phys */
> >>> - tphy->sif_base = devm_ioremap_resource(dev, sif_res);
> >>> - if (IS_ERR(tphy->sif_base)) {
> >>> - dev_err(dev, "failed to remap sif regs\n");
> >>> + tphy->sif_base = devm_platform_ioremap_resource(pdev,
> 0);
> >>> + if (IS_ERR(tphy->sif_base) && PTR_ERR(tphy->sif_base) !=
> -EINVAL)
> >>
> >> That's wrong. You want to return any error unconditionally, as the
> V1 PHY *needs*
> >> the sif iospace and there's nothing afterwards retrying this.
> >
> >
> > When sif_res is not configured, an IOMEM_ERR_PTR(-EINVAL) error
> will be returned in
> > __devm_ioremap_resource.
> >
> > This kind of error is ignored in the newly added code, and the
> driving probe
> > process will not be interrupted at this time.
> >
> > What did I miss?
> >
>
> As I said, MTK_PHY_V1 *needs* sif; devm_platform_ioremap_resource()
> returns a
> handle to that iospace, or error.
>
> tphy->sif_base = devm_platform_ioremap_resource(pdev, 0);
> if (IS_ERR(tphy->sif_base))
> return PTR_ERR(tphy->sif_base);
Yes, it's right, thanks
>
> Regards,
> Angelo
>
> > Thx,
> >
> > Yangtao
> >
> >
> >>
> >> Please fix.
> >>
> >> Regards,
> >> Angelo
> >>
> >>> return PTR_ERR(tphy->sif_base);
> >>> - }
> >>> }
> >>> if (tphy->pdata->version < MTK_PHY_V3) {
> >>
> >>
>
>
>
prev parent reply other threads:[~2023-07-11 8:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230705090126.26854-1-frank.li@vivo.com>
2023-07-05 9:01 ` [PATCH 4/4] phy: mediatek: tphy: Convert to devm_platform_ioremap_resource() Yangtao Li
2023-07-05 9:22 ` AngeloGioacchino Del Regno
2023-07-05 9:30 ` Yangtao Li
2023-07-05 10:00 ` AngeloGioacchino Del Regno
2023-07-11 5:07 ` Vinod Koul
2023-07-11 8:57 ` Chunfeng Yun (云春峰) [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c8795995227b3a83e9285d8e87befe6393d97d21.camel@mediatek.com \
--to=chunfeng.yun@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=frank.li@vivo.com \
--cc=kishon@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-phy@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=vkoul@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox