From: hongyan.song@intel.com
To: jikos@kernel.org, jic23@kernel.org, linux-iio@vger.kernel.org,
linux-input@vger.kernel.org
Cc: srinivas.pandruvada@intel.com, hdegoede@redhat.com, even.xu@intel.com
Subject: [PATCH] hid: remove NO_D3 flag for ish not CHV platform
Date: Fri, 17 May 2019 16:46:22 +0800 [thread overview]
Message-ID: <1558082782-29279-1-git-send-email-hongyan.song@intel.com> (raw)
From: Song Hongyan <hongyan.song@intel.com>
NO_D3 flag is set for CHV and the older platforms, the other platform
suppose can enter D3, if have this NO_D3 flag set it can never enter D3
Signed-off-by: Song Hongyan <hongyan.song@intel.com>
---
drivers/hid/intel-ish-hid/ipc/pci-ish.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/drivers/hid/intel-ish-hid/ipc/pci-ish.c b/drivers/hid/intel-ish-hid/ipc/pci-ish.c
index a6e1ee7..de1459b 100644
--- a/drivers/hid/intel-ish-hid/ipc/pci-ish.c
+++ b/drivers/hid/intel-ish-hid/ipc/pci-ish.c
@@ -154,7 +154,9 @@ static int ish_probe(struct pci_dev *pdev, const struct pci_device_id *ent)
/* mapping IO device memory */
hw->mem_addr = pcim_iomap_table(pdev)[0];
ishtp->pdev = pdev;
- pdev->dev_flags |= PCI_DEV_FLAGS_NO_D3;
+ /*This NO_D3 flag is only for CHV and older platforms*/
+ if (pdev->device == CHV_DEVICE_ID)
+ pdev->dev_flags |= PCI_DEV_FLAGS_NO_D3;
/* request and enable interrupt */
ret = pci_alloc_irq_vectors(pdev, 1, 1, PCI_IRQ_ALL_TYPES);
--
2.7.4
next reply other threads:[~2019-05-17 8:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-17 8:46 hongyan.song [this message]
2019-05-22 10:36 ` [PATCH] hid: remove NO_D3 flag for ish not CHV platform Jiri Kosina
2019-05-22 18:04 ` Pandruvada, Srinivas
2019-05-24 9:10 ` Jiri Kosina
2019-05-29 3:27 ` Pandruvada, Srinivas
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=1558082782-29279-1-git-send-email-hongyan.song@intel.com \
--to=hongyan.song@intel.com \
--cc=even.xu@intel.com \
--cc=hdegoede@redhat.com \
--cc=jic23@kernel.org \
--cc=jikos@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=srinivas.pandruvada@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).