From: Biju Das <biju.das.jz@bp.renesas.com>
To: Claudiu.Beznea <claudiu.beznea@tuxon.dev>,
"s.shtylyov@omp.ru" <s.shtylyov@omp.ru>,
"davem@davemloft.net" <davem@davemloft.net>,
"edumazet@google.com" <edumazet@google.com>,
"kuba@kernel.org" <kuba@kernel.org>,
"pabeni@redhat.com" <pabeni@redhat.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-renesas-soc@vger.kernel.org"
<linux-renesas-soc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Claudiu Beznea <claudiu.beznea.uj@bp.renesas.com>
Subject: RE: [PATCH net-next v3 5/6] net: ravb: Do not apply features to hardware if the interface is down
Date: Tue, 13 Feb 2024 11:39:34 +0000 [thread overview]
Message-ID: <TYCPR01MB11269FF7BA40379E09DB21673864F2@TYCPR01MB11269.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <368ca0a8-a005-4371-a959-297fd4f58cb1@tuxon.dev>
Hi Claudiu,
> -----Original Message-----
> From: claudiu beznea <claudiu.beznea@tuxon.dev>
> Sent: Tuesday, February 13, 2024 11:07 AM
> Subject: Re: [PATCH net-next v3 5/6] net: ravb: Do not apply features to
> hardware if the interface is down
>
> Hi, Biju,
>
> On 13.02.2024 12:13, Biju Das wrote:
> >
> > Hi Claudiu,
> >
> >> -----Original Message-----
> >> From: Claudiu <claudiu.beznea@tuxon.dev>
> >> Sent: Tuesday, February 13, 2024 9:41 AM
> >> Subject: [PATCH net-next v3 5/6] net: ravb: Do not apply features to
> >> hardware if the interface is down
> >>
> >> From: Claudiu Beznea <claudiu.beznea.uj@bp.renesas.com>
> >>
> >> Do not apply features to hardware if the interface is down. In case
> >> runtime PM is enabled, and while the interface is down, the IP will
> >> be in reset mode (as for some platforms disabling the clocks will
> >> switch the IP to reset mode, which will lead to losing register
> >> contents) and applying settings in reset mode is not an option.
> >> Instead, cache the features and apply them in ravb_open() through
> ravb_emac_init().
> >>
> >> To avoid accessing the hardware while the interface is down
> >> pm_runtime_active() check was introduced. Along with it the device
> >> runtime PM usage counter has been incremented to avoid disabling the
> >> device clocks while the check is in progress (if any).
> >>
> >> Commit prepares for the addition of runtime PM.
> >>
> >> Signed-off-by: Claudiu Beznea <claudiu.beznea.uj@bp.renesas.com>
> >> ---
> >>
> >> Changes in v3:
> >> - updated patch title and description
> >> - updated patch content due to patch 4/6
> >>
> >> Changes in v2:
> >> - fixed typo in patch description
> >> - adjusted ravb_set_features_gbeth(); didn't collect the Sergey's Rb
> >> tag due to this
> >>
> >> Changes since [2]:
> >> - use pm_runtime_get_noresume() and pm_runtime_active() and updated the
> >> commit message to describe that
> >> - fixed typos
> >> - s/CSUM/checksum in patch title and description
> >>
> >> Changes in v3 of [2]:
> >> - this was patch 20/21 in v2
> >> - fixed typos in patch description
> >> - removed code from ravb_open()
> >> - use ndev->flags & IFF_UP checks instead of netif_running()
> >>
> >> Changes in v2 of [2]:
> >> - none; this patch is new
> >>
> >>
> >> drivers/net/ethernet/renesas/ravb_main.c | 16 ++++++++++++----
> >> 1 file changed, 12 insertions(+), 4 deletions(-)
> >>
> >> diff --git a/drivers/net/ethernet/renesas/ravb_main.c
> >> b/drivers/net/ethernet/renesas/ravb_main.c
> >> index b3b91783bb7a..4dd0520dea90 100644
> >> --- a/drivers/net/ethernet/renesas/ravb_main.c
> >> +++ b/drivers/net/ethernet/renesas/ravb_main.c
> >> @@ -2566,15 +2566,23 @@ static int ravb_set_features(struct
> >> net_device *ndev, {
> >> struct ravb_private *priv = netdev_priv(ndev);
> >> const struct ravb_hw_info *info = priv->info;
> >> - int ret;
> >> + struct device *dev = &priv->pdev->dev;
> >> + int ret = 0;
> >> +
> >> + pm_runtime_get_noresume(dev);
> >> +
> >> + if (!pm_runtime_active(dev))
> >> + goto out_set_features;
> >
> > This can be simplified, which avoids 1 goto statement and Unnecessary
> > ret initialization. I am leaving to you and Sergey.
> >
> > if (!pm_runtime_active(dev))
> > ret = 0;
> > else
> > ret = info->set_feature(ndev, features);
> >
> > pm_runtime_put_noidle(dev);
> > if (ret)
> > goto err;
> >
> > ndev->features = features;
> >
> > err:
> > return ret;
> >
>
> I find it a bit difficult to follow this way.
I find this patch complicated by doing unnecessary intiailzation
And goto statements for non-err cases..
Maybe others can suggest how to do it in a better way.
Cheers,
Biju
>
> Thank you,
> Claudiu Beznea
>
> > Cheers,
> > Biju
> >
> >>
> >> ret = info->set_feature(ndev, features);
> >> if (ret)
> >> - return ret;
> >> + goto out_rpm_put;
> >>
> >> +out_set_features:
> >> ndev->features = features;
> >> -
> >> - return 0;
> >> +out_rpm_put:
> >> + pm_runtime_put_noidle(dev);
> >> + return ret;
> >> }
> >>
> >> static const struct net_device_ops ravb_netdev_ops = {
> >> --
> >> 2.39.2
> >
next prev parent reply other threads:[~2024-02-13 11:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-13 9:41 [PATCH net-next v3 0/6] net: ravb: Add runtime PM support (part 2) Claudiu
2024-02-13 9:41 ` [PATCH net-next v3 1/6] net: ravb: Get rid of the temporary variable irq Claudiu
2024-02-13 9:41 ` [PATCH net-next v3 2/6] net: ravb: Keep the reverse order of operations in ravb_close() Claudiu
2024-02-13 9:41 ` [PATCH net-next v3 3/6] net: ravb: Return cached statistics if the interface is down Claudiu
2024-02-13 9:41 ` [PATCH net-next v3 4/6] net: ravb: Move the update of ndev->features to ravb_set_features() Claudiu
2024-02-13 19:36 ` Sergey Shtylyov
2024-02-13 19:58 ` Sergey Shtylyov
2024-02-13 19:52 ` Sergey Shtylyov
2024-02-14 5:45 ` claudiu beznea
2024-02-13 9:41 ` [PATCH net-next v3 5/6] net: ravb: Do not apply features to hardware if the interface is down Claudiu
2024-02-13 10:13 ` Biju Das
2024-02-13 11:07 ` claudiu beznea
2024-02-13 11:39 ` Biju Das [this message]
2024-02-13 18:55 ` claudiu beznea
2024-02-13 19:48 ` Sergey Shtylyov
2024-02-13 9:41 ` [PATCH net-next v3 6/6] net: ravb: Add runtime PM support Claudiu
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=TYCPR01MB11269FF7BA40379E09DB21673864F2@TYCPR01MB11269.jpnprd01.prod.outlook.com \
--to=biju.das.jz@bp.renesas.com \
--cc=claudiu.beznea.uj@bp.renesas.com \
--cc=claudiu.beznea@tuxon.dev \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=s.shtylyov@omp.ru \
/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