From: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>,
kitestramuort <kitestramuort@autistici.org>,
Rajneesh Bhardwaj <rajneesh.bhardwaj@intel.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Platform Driver <platform-driver-x86@vger.kernel.org>
Subject: Re: intel_pmc_core does not initialize intel 8th gen PMC
Date: Tue, 13 Feb 2018 10:00:52 -0800 [thread overview]
Message-ID: <1518544852.2708.1.camel@linux.intel.com> (raw)
In-Reply-To: <CAHp75VdquuTLRgSbzKTBvyLmeFkGyDmP+U=GdOxLhBsU=w6Log@mail.gmail.com>
On Tue, 2018-02-13 at 18:21 +0200, Andy Shevchenko wrote:
> +Cc: Authors and correct ML
>
> On Mon, Feb 12, 2018 at 11:09 AM, kitestramuort
> <kitestramuort@autistici.org> wrote:
> > don't know if this is intended. In 4.15.2 i have:
>
> AFAIU the driver now binds to the hardcoded value of a PA of the
> device. So, you still have driver enabled.
>
> Srinivas, is my understanding correct?
Yes. This doesn't bind to PCI device. But the driver is still doing
what it is supposed to do.
You should still see
/sys/kernel/debug/pmc_core/* as before.
Thanks,
Srinivas
>
> > dmesg:
> > intel_pmc_core 0000:00:1f.2: enabling device (0000 -> 0002)
> >
> > lspci:
> > 00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC
> > (rev
> > 21)
> > Subsystem: Intel Corporation Sunrise Point-LP PMC
> > Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop-
> > ParErr- Stepping- SERR- FastB2B- DisINTx-
> > Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast
> > >TAbort-
> > <TAbort- <MAbort- >SERR- <PERR- INTx-
> > Region 0: Memory at dff00000 (32-bit, non-prefetchable)
> > [size=16K]
> > Kernel driver in use: intel_pmc_core
> > in 4.16.0-rc1 this becomes
> > dmesg:
> > intel_pmc_core: initialized
> >
> > lspci:
> > 00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC
> > (rev
> > 21)
> > Subsystem: Intel Corporation Sunrise Point-LP PMC
> > Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop-
> > ParErr- Stepping- SERR- FastB2B- DisINTx-
> > Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast
> > >TAbort-
> > <TAbort- <MAbort- >SERR- <PERR- INTx-
> > Region 0: Memory at dff00000 (32-bit, non-prefetchable)
> > [disabled] [size=16K]
>
>
>
prev parent reply other threads:[~2018-02-13 18:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-12 9:09 intel_pmc_core does not initialize intel 8th gen PMC kitestramuort
2018-02-13 16:21 ` Andy Shevchenko
2018-02-13 18:00 ` 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=1518544852.2708.1.camel@linux.intel.com \
--to=srinivas.pandruvada@linux.intel.com \
--cc=andy.shevchenko@gmail.com \
--cc=kitestramuort@autistici.org \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rajneesh.bhardwaj@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.