From: Kalle Valo <kvalo@codeaurora•org>
To: Vaibhav Gupta <vaibhavgupta40@gmail•com>
Cc: Bjorn Helgaas <helgaas@kernel•org>,
Bjorn Helgaas <bhelgaas@google•com>,
Bjorn Helgaas <bjorn@helgaas•com>,
Vaibhav Gupta <vaibhav.varodek@gmail•com>,
"David S. Miller" <davem@davemloft•net>, Jouni Malinen <j@w1•fi>,
Vaibhav Gupta <vaibhavgupta40@gmail•com>,
linux-wireless@vger•kernel.org, netdev@vger•kernel.org,
linux-kernel@vger•kernel.org,
linux-kernel-mentees@lists•linuxfoundation.org,
Shuah Khan <skhan@linuxfoundation•org>
Subject: Re: [PATCH v1] hostap: use generic power management
Date: Sun, 2 Aug 2020 15:18:32 +0000 (UTC) [thread overview]
Message-ID: <20200802151832.65606C433CA@smtp.codeaurora.org> (raw)
In-Reply-To: <20200721150547.371763-1-vaibhavgupta40@gmail.com>
Vaibhav Gupta <vaibhavgupta40@gmail•com> wrote:
> Drivers using legacy power management .suspen()/.resume() callbacks
> have to manage PCI states and device's PM states themselves. They also
> need to take care of standard configuration registers.
>
> Switch to generic power management framework using a single
> "struct dev_pm_ops" variable to take the unnecessary load from the driver.
> This also avoids the need for the driver to directly call most of the PCI
> helper functions and device power state control functions as through
> the generic framework, PCI Core takes care of the necessary operations,
> and drivers are required to do only device-specific jobs.
>
> Signed-off-by: Vaibhav Gupta <vaibhavgupta40@gmail•com>
Patch applied to wireless-drivers-next.git, thanks.
99aaa1aafa5c hostap: use generic power management
--
https://patchwork.kernel.org/patch/11675851/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
prev parent reply other threads:[~2020-08-02 15:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-21 15:05 [PATCH v1] hostap: use generic power management Vaibhav Gupta
2020-07-21 15:08 ` Vaibhav Gupta
2020-08-02 15:18 ` Kalle Valo [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=20200802151832.65606C433CA@smtp.codeaurora.org \
--to=kvalo@codeaurora$(echo .)org \
--cc=bhelgaas@google$(echo .)com \
--cc=bjorn@helgaas$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=helgaas@kernel$(echo .)org \
--cc=j@w1$(echo .)fi \
--cc=linux-kernel-mentees@lists$(echo .)linuxfoundation.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-wireless@vger$(echo .)kernel.org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=skhan@linuxfoundation$(echo .)org \
--cc=vaibhav.varodek@gmail$(echo .)com \
--cc=vaibhavgupta40@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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