linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Pandruvada, Srinivas" <srinivas.pandruvada@intel.com>
To: "Zhang, Rui" <rui.zhang@intel.com>,
	"edubezval@gmail.com" <edubezval@gmail.com>,
	"hirofumi@mail.parknet.co.jp" <hirofumi@mail.parknet.co.jp>
Cc: "linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>
Subject: Re: [PATCH] thermal: intel_pch_thermal: Support skylake PCH 100 series thermal
Date: Tue, 18 Oct 2016 18:03:36 +0000	[thread overview]
Message-ID: <1476813814.132953.50.camel@intel.com> (raw)
In-Reply-To: <87pomyd515.fsf@mail.parknet.co.jp>

On Tue, 2016-10-18 at 06:44 +0900, OGAWA Hirofumi wrote:
> Using registers are compatible with current driver.
This description is not enough. Without going through the whole code, I
was not able to find out what this patch is doing.

Basically you want to tie the themal_zone name and device operations to
a board, rather than to PCI devices ids. In this way multiple PCI ids
for the same board can be accounted for.

Also need to consider another patch sent to mailing list for supporting
Haswell PCH.

One comment below in the code.

[...]
 
>  static struct pci_device_id intel_pch_thermal_id[] = {
> -	{ PCI_DEVICE(PCI_VENDOR_ID_INTEL, PCH_THERMAL_DID_WPT) },
> -	{ PCI_DEVICE(PCI_VENDOR_ID_INTEL, PCH_THERMAL_DID_SKL) },
> +	{ PCI_DEVICE(PCI_VENDOR_ID_INTEL, PCH_THERMAL_DID_WPT),
> +	  .driver_data = board_wpt, },
> +	{ PCI_DEVICE(PCI_VENDOR_ID_INTEL, PCH_THERMAL_DID_SKL),
> +	  .driver_data = board_skl, },
> +	/* skylake PCH 100 series */
> +	{ PCI_DEVICE(PCI_VENDOR_ID_INTEL, 0xa131),
Change a131 to a define (PCH_THERMAL_DID_SKL_H)

Thanks,
Srinivas

  reply	other threads:[~2016-10-18 18:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-17 21:44 [PATCH] thermal: intel_pch_thermal: Support skylake PCH 100 series thermal OGAWA Hirofumi
2016-10-18 18:03 ` Pandruvada, Srinivas [this message]
2016-10-18 20:10   ` OGAWA Hirofumi
2016-10-18 20:15     ` Pandruvada, Srinivas
2016-10-18 20:57       ` OGAWA Hirofumi
2016-10-18 20:59         ` [PATCH v2] " OGAWA Hirofumi
2016-10-18 21:04           ` Pandruvada, Srinivas
2016-11-15 12:20             ` Zhang Rui
2016-11-15 14:13               ` OGAWA Hirofumi

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=1476813814.132953.50.camel@intel.com \
    --to=srinivas.pandruvada@intel.com \
    --cc=edubezval@gmail.com \
    --cc=hirofumi@mail.parknet.co.jp \
    --cc=linux-pm@vger.kernel.org \
    --cc=rui.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).