From: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
To: Kai-Heng Feng <kai.heng.feng@canonical.com>
Cc: Jiri Kosina <jikos@kernel.org>,
Benjamin Tissoires <benjamin.tissoires@redhat.com>,
Zhang Lixu <lixu.zhang@intel.com>, Even Xu <even.xu@intel.com>,
Song Hongyan <hongyan.song@intel.com>,
"open list:INTEL INTEGRATED SENSOR HUB DRIVER"
<linux-input@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] HID: intel-ish-hid: Replace PCI_DEV_FLAGS_NO_D3 with pci_save_state
Date: Fri, 19 Jun 2020 12:34:39 -0700 [thread overview]
Message-ID: <a27d9ebf83fde4dd596ff426e6413b12b947d973.camel@linux.intel.com> (raw)
In-Reply-To: <20200619140215.11779-1-kai.heng.feng@canonical.com>
On Fri, 2020-06-19 at 22:02 +0800, Kai-Heng Feng wrote:
> PCI_DEV_FLAGS_NO_D3 should not be used outside of PCI core.
>
> Instead, we can use pci_save_state() to hint PCI core that the device
> should stay at D0 during suspend. By doing so, PCI core will let the
> upstream bridges also stays at D0 so the entire hierachy is in the
> correct power state as PCI spec mandates.
>
> Signed-off-by: Kai-Heng Feng <kai.heng.feng@canonical.com>
> ---
> v2:
> - Wording change.
>
> drivers/hid/intel-ish-hid/ipc/pci-ish.c | 15 ++++++++++-----
> 1 file changed, 10 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/hid/intel-ish-hid/ipc/pci-ish.c
> b/drivers/hid/intel-ish-hid/ipc/pci-ish.c
> index f491d8b4e24c..ab588b9c8d09 100644
> --- a/drivers/hid/intel-ish-hid/ipc/pci-ish.c
> +++ b/drivers/hid/intel-ish-hid/ipc/pci-ish.c
> @@ -106,6 +106,11 @@ static inline bool ish_should_enter_d0i3(struct
> pci_dev *pdev)
> return !pm_suspend_via_firmware() || pdev->device ==
> CHV_DEVICE_ID;
> }
>
> +static inline bool ish_should_leave_d0i3(struct pci_dev *pdev)
> +{
> + return !pm_resume_via_firmware() || pdev->device ==
> CHV_DEVICE_ID;
> +}
> +
> /**
> * ish_probe() - PCI driver probe callback
> * @pdev: pci device
> @@ -215,9 +220,7 @@ static void __maybe_unused
> ish_resume_handler(struct work_struct *work)
> struct ishtp_device *dev = pci_get_drvdata(pdev);
> int ret;
>
> - /* Check the NO_D3 flag to distinguish the resume paths */
> - if (pdev->dev_flags & PCI_DEV_FLAGS_NO_D3) {
> - pdev->dev_flags &= ~PCI_DEV_FLAGS_NO_D3;
> + if (ish_should_leave_d0i3(pdev) && !dev->suspend_flag) {
> disable_irq_wake(pdev->irq);
>
> ishtp_send_resume(dev);
> @@ -281,8 +284,10 @@ static int __maybe_unused ish_suspend(struct
> device *device)
> */
> ish_disable_dma(dev);
> } else {
> - /* Set the NO_D3 flag, the ISH would enter D0i3
> */
> - pdev->dev_flags |= PCI_DEV_FLAGS_NO_D3;
> + /* Save state so PCI core will keep the device
> at D0,
> + * the ISH would enter D0i3
> + */
Better to use multi-line comment style.
Otherwise you can add my ACK.
Thanks,
Srinivas
> + pci_save_state(pdev);
>
> enable_irq_wake(pdev->irq);
> }
prev parent reply other threads:[~2020-06-19 19:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-19 14:02 [PATCH v2] HID: intel-ish-hid: Replace PCI_DEV_FLAGS_NO_D3 with pci_save_state Kai-Heng Feng
2020-06-19 19:34 ` Srinivas Pandruvada [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=a27d9ebf83fde4dd596ff426e6413b12b947d973.camel@linux.intel.com \
--to=srinivas.pandruvada@linux.intel.com \
--cc=benjamin.tissoires@redhat.com \
--cc=even.xu@intel.com \
--cc=hongyan.song@intel.com \
--cc=jikos@kernel.org \
--cc=kai.heng.feng@canonical.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lixu.zhang@intel.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).