From: Igor Russkikh <irusskikh@marvell.com>
To: Vaibhav Gupta <vaibhavgupta40@gmail.com>,
Bjorn Helgaas <helgaas@kernel.org>,
Bjorn Helgaas <bhelgaas@google.com>, <bjorn@helgaas.com>,
Vaibhav Gupta <vaibhav.varodek@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
"Manish Chopra" <manishc@marvell.com>
Cc: <netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-kernel-mentees@lists.linuxfoundation.org>,
<skhan@linuxfoundation.org>
Subject: Re: [EXT] [PATCH v1 2/2] qlcninc: use generic power management
Date: Thu, 2 Jul 2020 16:22:44 +0300 [thread overview]
Message-ID: <3aa3a243-6e9a-c80d-95d1-9c6a143e7eb4@marvell.com> (raw)
In-Reply-To: <20200702063632.289959-3-vaibhavgupta40@gmail.com>
On 02/07/2020 9:36 am, Vaibhav Gupta wrote:
> External Email
>
> ----------------------------------------------------------------------
> With legacy PM, drivers themselves were responsible for managing the
> device's power states and takes care of register states. And they use PCI
> helper functions to do it.
>
> After upgrading to the generic structure, PCI core will take care of
> required tasks and drivers should do only device-specific operations.
>
> .suspend() calls __qlcnic_shutdown, which then calls qlcnic_82xx_shutdown;
> .resume() calls __qlcnic_resume, which then calls qlcnic_82xx_resume;
>
> Both ...82xx..() are define in
> drivers/net/ethernet/qlogic/qlcnic/qlcnic_hw.c and are used only in
> drivers/net/ethernet/qlogic/qlcnic/qlcnic_main.c.
>
> Hence upgrade them and remove PCI function calls, like pci_save_state()
> and
> pci_enable_wake(), inside them
>
> Compile-tested only.
>
> Signed-off-by: Vaibhav Gupta <vaibhavgupta40@gmail.com>
Acked-by: Igor Russkikh <irusskikh@marvell.com>
Thanks!
next prev parent reply other threads:[~2020-07-02 13:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-02 6:36 [PATCH v1 0/2] qlogic: " Vaibhav Gupta
2020-07-02 6:36 ` [PATCH v1 1/2] netxen_nic: " Vaibhav Gupta
2020-07-02 6:36 ` [PATCH v1 2/2] qlcninc: " Vaibhav Gupta
2020-07-02 13:22 ` Igor Russkikh [this message]
2020-07-02 16:36 ` Jakub Kicinski
2020-07-02 17:02 ` Vaibhav Gupta
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=3aa3a243-6e9a-c80d-95d1-9c6a143e7eb4@marvell.com \
--to=irusskikh@marvell.com \
--cc=bhelgaas@google.com \
--cc=bjorn@helgaas.com \
--cc=davem@davemloft.net \
--cc=helgaas@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manishc@marvell.com \
--cc=netdev@vger.kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=vaibhav.varodek@gmail.com \
--cc=vaibhavgupta40@gmail.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
all inboxes | Powered by JetHome®