| Message ID | 20240207120733.1746920-5-claudiu.beznea.uj@bp.renesas.com (mailing list archive) |
|---|---|
| State | Superseded |
| Delegated to: | Geert Uytterhoeven |
| Headers | show |
| Series | net: ravb: Add runtime PM support (part 2) | expand |
On 2/7/24 3:07 PM, Claudiu wrote: > From: Claudiu Beznea <claudiu.beznea.uj@bp.renesas.com> > > Do not apply the RX checksum settings 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 registers content) and The register contents? I thought I'd pointed out all of these... > applying settings in reset mode is not an option. Instead, cache the RX > checksum settings and apply them in ravb_open() through ravb_emac_init(). > This has been solved by introducing pm_runtime_active() check. 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> Reviewed-by: Sergey Shtylyov <s.shtylyov@omp.ru> I'm afraid such check now needs to be added to ravb_set_features_gbeth() that's populated by Biju Das' checksum patches (which I've already ACKed)... [...] MBR, Sergey
Hi Sergey, > -----Original Message----- > From: Sergey Shtylyov <s.shtylyov@omp.ru> > Sent: Wednesday, February 7, 2024 8:50 PM > Subject: Re: [PATCH net-next 4/5] net: ravb: Do not apply RX checksum > settings to hardware if the interface is down > > On 2/7/24 3:07 PM, Claudiu wrote: > > > From: Claudiu Beznea <claudiu.beznea.uj@bp.renesas.com> > > > > Do not apply the RX checksum settings 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 registers > > content) and > > The register contents? I thought I'd pointed out all of these... > > > applying settings in reset mode is not an option. Instead, cache the > > RX checksum settings and apply them in ravb_open() through > ravb_emac_init(). > > This has been solved by introducing pm_runtime_active() check. 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> > > Reviewed-by: Sergey Shtylyov <s.shtylyov@omp.ru> > > I'm afraid such check now needs to be added to > ravb_set_features_gbeth() that's populated by Biju Das' checksum patches > (which I've already ACKed)... You mean this check to be moved to ravb_set_features_rcar() instead of ravb_set_rx_csum() as ravb_set_rx_csum() is called in receive path as well which is interface up case. ON reset mode, anyway we don't get any interrupts so there is no rx. Then possibility is through set_features?? Cheers, Biju
> -----Original Message----- > From: Biju Das <biju.das.jz@bp.renesas.com> > Sent: Thursday, February 8, 2024 8:09 AM > Subject: RE: [PATCH net-next 4/5] net: ravb: Do not apply RX checksum > settings to hardware if the interface is down > > Hi Sergey, > > > -----Original Message----- > > From: Sergey Shtylyov <s.shtylyov@omp.ru> > > Sent: Wednesday, February 7, 2024 8:50 PM > > Subject: Re: [PATCH net-next 4/5] net: ravb: Do not apply RX checksum > > settings to hardware if the interface is down > > > > On 2/7/24 3:07 PM, Claudiu wrote: > > > > > From: Claudiu Beznea <claudiu.beznea.uj@bp.renesas.com> > > > > > > Do not apply the RX checksum settings 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 > > > registers > > > content) and > > > > The register contents? I thought I'd pointed out all of these... > > > > > applying settings in reset mode is not an option. Instead, cache the > > > RX checksum settings and apply them in ravb_open() through > > ravb_emac_init(). > > > This has been solved by introducing pm_runtime_active() check. 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> > > > > Reviewed-by: Sergey Shtylyov <s.shtylyov@omp.ru> > > > > I'm afraid such check now needs to be added to > > ravb_set_features_gbeth() that's populated by Biju Das' checksum > > patches (which I've already ACKed)... > > You mean this check to be moved to ravb_set_features_rcar() instead of > ravb_set_rx_csum() as ravb_set_rx_csum() is called in receive path as well > which is interface up case. > ON reset mode, anyway we don't get any interrupts so there is no rx. > Then possibility is through set_features?? Or are you suggesting to have a common code to avoid code duplication? On interface down case, just cache the feature and return? Active cases, call the family specific callback()? Cheers, Biju
On 07.02.2024 22:50, Sergey Shtylyov wrote: > On 2/7/24 3:07 PM, Claudiu wrote: > >> From: Claudiu Beznea <claudiu.beznea.uj@bp.renesas.com> >> >> Do not apply the RX checksum settings 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 registers content) and > > The register contents? I thought I'd pointed out all of these... > >> applying settings in reset mode is not an option. Instead, cache the RX >> checksum settings and apply them in ravb_open() through ravb_emac_init(). >> This has been solved by introducing pm_runtime_active() check. 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> > > Reviewed-by: Sergey Shtylyov <s.shtylyov@omp.ru> > > I'm afraid such check now needs to be added to ravb_set_features_gbeth() > that's populated by Biju Das' checksum patches (which I've already ACKed)... Yes, it's on my radar. I'll check it and update it (if any) in the next version. Thank you, Claudiu Beznea > > [...] > > MBR, Sergey
diff --git a/drivers/net/ethernet/renesas/ravb_main.c b/drivers/net/ethernet/renesas/ravb_main.c index 4f8d5c9e9e03..df47d3e057c5 100644 --- a/drivers/net/ethernet/renesas/ravb_main.c +++ b/drivers/net/ethernet/renesas/ravb_main.c @@ -2385,8 +2385,14 @@ static int ravb_change_mtu(struct net_device *ndev, int new_mtu) static void ravb_set_rx_csum(struct net_device *ndev, bool enable) { struct ravb_private *priv = netdev_priv(ndev); + struct device *dev = &priv->pdev->dev; unsigned long flags; + pm_runtime_get_noresume(dev); + + if (!pm_runtime_active(dev)) + goto out_rpm_put; + spin_lock_irqsave(&priv->lock, flags); /* Disable TX and RX */ @@ -2399,6 +2405,9 @@ static void ravb_set_rx_csum(struct net_device *ndev, bool enable) ravb_rcv_snd_enable(ndev); spin_unlock_irqrestore(&priv->lock, flags); + +out_rpm_put: + pm_runtime_put_noidle(dev); } static int ravb_set_features_gbeth(struct net_device *ndev,