From: Vaibhav Gupta <vaibhav.varodek@gmail.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: Hans Verkuil <hverkuil@xs4all.nl>,
Vaibhav Gupta <vaibhavgupta40@gmail.com>,
Bjorn Helgaas <bhelgaas@google.com>,
bjorn@helgaas.com, Mauro Carvalho Chehab <mchehab@kernel.org>,
linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
linux-kernel-mentees@lists.linuxfoundation.org,
skhan@linuxfoundation.org
Subject: Re: [PATCH v1 2/6] [media] cx23885: use generic power management
Date: Tue, 14 Jul 2020 16:22:59 +0530 [thread overview]
Message-ID: <20200714105259.GA1792@gmail.com> (raw)
In-Reply-To: <20200714003814.GA292013@bjorn-Precision-5520>
On Mon, Jul 13, 2020 at 07:38:14PM -0500, Bjorn Helgaas wrote:
> On Mon, Jul 13, 2020 at 12:01:51PM +0200, Hans Verkuil wrote:
> > On 29/06/2020 09:36, Vaibhav Gupta wrote:
> >
> > I don't entirely understand this. Wouldn't it be sufficient to just
> > drop the .suspend/.resume assignments here? It is now required for
> > driver.pm to be non-NULL?
> >
> > I'm not up to speed on the changes, but normally you can leave things
> > NULL if you don't support a feature (PM in this case).
>
> I think this patch will break things. Previously, we had:
>
> cx23885_pci_driver.suspend == NULL
> cx23885_pci_driver.resume == NULL
> cx23885_pci_driver.driver.pm == NULL
>
> pci_pm_suspend() looks like:
>
> if (pci_has_legacy_pm_support(pci_dev))
> return pci_legacy_suspend(dev, PMSG_SUSPEND);
>
> if (!pm) {
> pci_pm_default_suspend(pci_dev);
> return 0;
> }
>
> pci_has_legacy_pm_support() was false since drv->suspend and
> drv->resume are both NULL, so we'd take the pci_pm_default_suspend()
> path. After this patch, driver.pm would no longer be NULL, so we'd
> take a different path that is clearly not equivalent.
>
> I think you should do this:
>
> - /* TODO */
> - .suspend = NULL,
> - .resume = NULL,
>
> and leave .driver.pm NULL by not mentioning it at all. That should be
> identical at the object code level since those are the defaults
> anyway.
>
> That almost looks like useless churn, but the point of this patch is
> to remove use of PCI legacy PM (pci_driver.suspend and .resume) so we
> can completely remove that infrastructure from the PCI core, including
> the .suspend and .resume members of struct pci_driver, so we really do
> need to do it.
Okay!
Thanks!
-- Vaibhav Gupta
>
> Bjorn
next prev parent reply other threads:[~2020-07-14 10:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-29 7:35 [PATCH v1 0/6] [media] pci: use generic power management Vaibhav Gupta
2020-06-29 7:35 ` [PATCH v1 1/6] [media] sta2x11: " Vaibhav Gupta
2020-06-29 7:36 ` [PATCH v1 2/6] [media] cx23885: " Vaibhav Gupta
2020-07-13 10:01 ` Hans Verkuil
2020-07-14 0:38 ` Bjorn Helgaas
2020-07-14 10:52 ` Vaibhav Gupta [this message]
2020-06-29 7:36 ` [PATCH v1 3/6] [media] cx25821: " Vaibhav Gupta
2020-07-13 10:03 ` Hans Verkuil
2020-06-29 7:36 ` [PATCH v1 4/6] [media] cx88: " Vaibhav Gupta
2020-06-29 7:36 ` [PATCH v1 5/6] [media] meye: " Vaibhav Gupta
2020-06-29 7:36 ` [PATCH v1 6/6] [media] tw68: " 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=20200714105259.GA1792@gmail.com \
--to=vaibhav.varodek@gmail.com \
--cc=bhelgaas@google.com \
--cc=bjorn@helgaas.com \
--cc=helgaas@kernel.org \
--cc=hverkuil@xs4all.nl \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=skhan@linuxfoundation.org \
--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;
as well as URLs for NNTP newsgroup(s).