From: "Pandruvada, Srinivas" <srinivas.pandruvada@intel.com>
To: "jikos@kernel.org" <jikos@kernel.org>,
"Song, Hongyan" <hongyan.song@intel.com>
Cc: "linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
"hdegoede@redhat.com" <hdegoede@redhat.com>,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
"jic23@kernel.org" <jic23@kernel.org>,
"Xu, Even" <even.xu@intel.com>
Subject: Re: [PATCH] hid: remove NO_D3 flag for ish not CHV platform
Date: Wed, 22 May 2019 18:04:34 +0000 [thread overview]
Message-ID: <497b1b7fe4fca84f1a2bf450db196950c1e98310.camel@intel.com> (raw)
In-Reply-To: <nycvar.YFH.7.76.1905221235140.1962@cbobk.fhfr.pm>
[-- Attachment #1: Type: text/plain, Size: 1514 bytes --]
On Wed, 2019-05-22 at 12:36 +0200, Jiri Kosina wrote:
> On Fri, 17 May 2019, hongyan.song@intel.com wrote:
>
> > From: Song Hongyan <hongyan.song@intel.com>
Also commit summary "hid: remove NO_D3 flag for non Cherry Trail (CHT)"
> >
> > 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
>
> Could you please provide a little bit more descriptive changelog --
> namely
> what observable problem is it fixing.
In addition, I don't think this is a rc2+ release fix.
Thanks,
Srinivas
>
> > 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*/
>
> ... and while you're updating the changelog, please also stick a
> space
> before and after the comment mark.
>
> Thanks,
>
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 3290 bytes --]
next prev parent reply other threads:[~2019-05-22 18:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-17 8:46 [PATCH] hid: remove NO_D3 flag for ish not CHV platform hongyan.song
2019-05-22 10:36 ` Jiri Kosina
2019-05-22 18:04 ` Pandruvada, Srinivas [this message]
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=497b1b7fe4fca84f1a2bf450db196950c1e98310.camel@intel.com \
--to=srinivas.pandruvada@intel.com \
--cc=even.xu@intel.com \
--cc=hdegoede@redhat.com \
--cc=hongyan.song@intel.com \
--cc=jic23@kernel.org \
--cc=jikos@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
/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).