From mboxrd@z Thu Jan 1 00:00:00 1970 From: simon-wM4F9T/ekXmXDw4h08c5KA@public.gmane.org Subject: Re: Poulsbo I2C - /dev/i2c not seen when loading i2c-dev Date: Tue, 5 Apr 2011 13:05:02 -0400 Message-ID: References: <20110401121027.49ce012b@endymion.delvare> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: In-Reply-To: <20110401121027.49ce012b-R0o5gVi9kd7kN2dkZ6Wm7A@public.gmane.org> Sender: linux-i2c-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Jean Delvare Cc: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-Id: linux-i2c@vger.kernel.org >> The board is built around the Poulsbo and therefore using the 'i2c-i= sch' >> driver. > > Check for error messages when you load the i2c-isch driver. Note that > in kernel 2.6.34 the structure of the i2c-isch driver was changed, fr= om > a standalone PCI driver to a MFD driver. Please make sure that you ha= ve > CONFIG_LPC_SCH installed and driver lpc_sch loaded, otherwise i2c-isc= h > will never see the platform device it is looking for. Thanks for the suggestion, unfortunately there is an issue with lpc_sch loading, and error is reported via dmesg. -- [ 403.809826] ACPI: resource (null) [io 0x0480-0x04bf] conflicts with ACPI region PHO_ [io 0x4bc-0x4bc] [ 403.809834] ACPI: If an ACPI driver is available for this device, yo= u should use it instead of the native driver [ 403.809921] lpc_sch: probe of 0000:00:1f.0 failed with error -16 -- 34 rmmod i2c_isch 35 rmmod lpc_sch 36 rmmod i2c_gpio 37 tree /sys/bus/i2c/ 38 modprobe i2c_isch 39 modprobe i2c_gpio 40 modprobe lpc_sch 41 dmesg | tail -- Any further suggestions would be much appreciated. The system reports t= he poulsbo under 'lspci' as: -- 00:1b.0 Audio device: Intel Corporation System Controller Hub (SCH Poulsbo) HD Audio Controller (rev 07) Subsystem: Intel Corporation Device 8119 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=3Dfast >TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: [40] Express (v1) Root Port (Slot+), MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s unlimited, L1 unlimited ExtTag- RBE+ FLReset- DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ TransPend- LnkCap: Port #1, Speed 2.5GT/s, Width x1, ASPM L0s L1, Latency L0 <256ns, L1 <4us ClockPM+ Surprise- LLActRep+ BwNot- LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk+ ExtSynch- ClockPM+ AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive+ BWMgmt- ABWMgmt- SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug+ Surprise+ Slot #0, PowerLimit 0.000W; Interlock- NoCompl- SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- LinkCh= g- Control: AttnInd Unknown, PwrInd Unknown, Power- Interlock- SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet+ Interlock- Changed: MRL- PresDet+ LinkState+ RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna- CRSVisibl= e- RootCap: CRSVisible- RootSta: PME ReqID 0000, PMEStatus- PMEPending- Capabilities: [90] Subsystem: Intel Corporation Device 8119 Capabilities: [a0] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=3D0mA PME(D0+,D1-,D2-,D3hot+,D= 3cold+) Status: D0 NoSoftRst- PME-Enable- DSel=3D0 DScale=3D0 PME- Kernel driver in use: pcieport 00:1d.0 USB Controller: Intel Corporation System Controller Hub (SCH Poulsbo) USB UHCI #1 (rev 07) (prog-if 00 [UHCI]) Subsystem: Intel Corporation Device 8119 Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=3Dfast >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- > Reviewing the schematic I see that there are several buses, each goi= ng >> to >> individual components: >> IT8516 U5/110+111 -> LTC1760 U6/18+22 [battery charger =E2=80=93 0x1= A/0x12] >> IT8516 U5/115+116 -> W83L771 U60/8+7 [thermal sensor =E2=80=93 0x18?= ?] >> IT8516 U5/117+118 -> LSM303DLH U64/19+20 [accel/compass =E2=80=93 0x= 19] >> POULSBO U2/G37+H38 -> PCI Express Socket > > This suggests that the board uses the SMBus controllers in the ITE IT= 8516 > Super-I/O chip rather than the Intel SCH south bridge. Unfortunately = we > have no support for the SMBus controllers of the IT8516, and I doubt = we > get support anytime soon as I was unable to find a datasheet for the > ITE IT8516. > I believe that Jean is correct, we have exchanged a few emails regardin= g the IT8516 SuperIO chip and have some ideas about getting some support. Simon.