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@xxxxxxxxxxxxx> 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] > > >
