From: "Pandruvada, Srinivas" <srinivas.pandruvada@intel.com>
To: "hirofumi@mail.parknet.co.jp" <hirofumi@mail.parknet.co.jp>
Cc: "Zhang, Rui" <rui.zhang@intel.com>,
"edubezval@gmail.com" <edubezval@gmail.com>,
"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 20:15:57 +0000 [thread overview]
Message-ID: <1476821756.132953.56.camel@intel.com> (raw)
In-Reply-To: <87eg3dctaj.fsf@mail.parknet.co.jp>
On Wed, 2016-10-19 at 05:10 +0900, OGAWA Hirofumi wrote:
> "Pandruvada, Srinivas" <srinivas.pandruvada@intel.com> writes:
>
> >
> > 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.
>
> Exactly. I thought the patch is enough easy to read, and changelog
> would
> be better to not explain what code itself, and wrote note of code
> (registers are same with current).
Reviewers will look at the description before to look at 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)
>
> I don't think it helps anything actually, because no users of define
> anymore. Well, anyway, ok, I don't care either case.
Only for the sake consistency with rest of the ids defined here.
Thanks,
Srinivas
next prev parent reply other threads:[~2016-10-18 20:15 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
2016-10-18 20:10 ` OGAWA Hirofumi
2016-10-18 20:15 ` Pandruvada, Srinivas [this message]
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=1476821756.132953.56.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).