From: Ondrej Zary <linux@rainbow-software.org>
To: Francois Romieu <romieu@fr.zoreil.com>
Cc: netdev@vger.kernel.org, David Miller <davem@davemloft.net>,
Kernel development list <linux-kernel@vger.kernel.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>
Subject: Re: [PATCH 3/3] dl2k: Implement suspend
Date: Wed, 18 Nov 2015 10:10:41 +0100 [thread overview]
Message-ID: <201511181010.41920.linux@rainbow-software.org> (raw)
In-Reply-To: <20151117225610.GB3362@electric-eye.fr.zoreil.com>
On Tuesday 17 November 2015, Francois Romieu wrote:
> Ondrej Zary <linux@rainbow-software.org> :
> [...]
>
> > diff --git a/drivers/net/ethernet/dlink/dl2k.c
> > b/drivers/net/ethernet/dlink/dl2k.c index 9e9baa0..b53dfa7 100644
> > --- a/drivers/net/ethernet/dlink/dl2k.c
> > +++ b/drivers/net/ethernet/dlink/dl2k.c
> > @@ -1824,11 +1824,57 @@ rio_remove1 (struct pci_dev *pdev)
> > }
> > }
> >
> > +#ifdef CONFIG_PM
> > +static int rio_suspend(struct pci_dev *pdev, pm_message_t state)
> > +{
> > + struct net_device *dev = pci_get_drvdata(pdev);
> > + struct netdev_private *np = netdev_priv(dev);
> > +
> > + pci_save_state(pdev);
>
> Cargo-cultism ?
>
> > +
> > + if (netif_running(dev)) {
> > + netif_device_detach(dev);
> > + del_timer_sync(&np->timer);
> > + rio_hw_stop(dev);
> > + free_list(dev);
>
> If free_list is used here, so must alloc_list be in resume, whence
> an extra failure opportunity.
>
> You may not need to free both Tx and Rx here.
I'll better drop the free_list/alloc_list from suspend/resume (as you
suggested before).
> [...]
>
> > static struct pci_driver rio_driver = {
> > .name = "dl2k",
> > .id_table = rio_pci_tbl,
> > .probe = rio_probe1,
> > .remove = rio_remove1,
> > +#ifdef CONFIG_PM
> > + .suspend = rio_suspend,
> > + .resume = rio_resume,
> > +#endif /* CONFIG_PM */
>
> It looks a bit old school.
>
> See Documentation/power/pci.txt and drivers/net/ethernet/via/via-rhine.c
> for an instance of SIMPLE_DEV_PM_OPS.
>
> At some point you'll probably support runtime power management though.
Thanks for suggestion, I've been looking at the wrong drivers as none of them
used dev_pm_ops.
--
Ondrej Zary
next prev parent reply other threads:[~2015-11-18 9:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-17 17:28 [PATCH 1/3] dl2k: Handle memory allocation errors in alloc_list Ondrej Zary
2015-11-17 17:28 ` [PATCH 2/3] dl2k: Reorder and cleanup initialization Ondrej Zary
2015-11-17 17:28 ` [PATCH 3/3] dl2k: Implement suspend Ondrej Zary
2015-11-17 22:56 ` Francois Romieu
2015-11-18 9:10 ` Ondrej Zary [this message]
2015-11-17 22:54 ` [PATCH 1/3] dl2k: Handle memory allocation errors in alloc_list Francois Romieu
2015-11-18 8:10 ` Ondrej Zary
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=201511181010.41920.linux@rainbow-software.org \
--to=linux@rainbow-software.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=romieu@fr.zoreil.com \
/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;
as well as URLs for NNTP newsgroup(s).