All of lore.kernel.org
 help / color / mirror / Atom feed
* i2c-dev
@ 2014-10-22  1:54 John de la Garza
  2014-10-22 16:35 ` i2c-dev Paul Bolle
  0 siblings, 1 reply; 6+ messages in thread
From: John de la Garza @ 2014-10-22  1:54 UTC (permalink / raw)
  To: kernelnewbies

I have my kernel built with dev-i2c and i2c_i801 but do not have
a /dev entry.

lspci shows this:
00:1f.3 SMBus: Intel Corporation 5 Series/3400 Series Chipset SMBus Controller (rev 06)

dmesg shows this:
[    1.566003] i801_smbus 0000:00:1f.3: enabling device (0000 -> 0003)

ls /sys/bus/i2c/devices/ shows nothing...

on running this on a MacBookPro6,2


What am I missing?  Shouldn't I see a i2c device?  I think SMBus is
a subset of i2c and I should be able to use that subset, right?

^ permalink raw reply	[flat|nested] 6+ messages in thread

* i2c-dev
  2014-10-22  1:54 i2c-dev John de la Garza
@ 2014-10-22 16:35 ` Paul Bolle
       [not found]   ` <20141022172729.GA3098@vega.jjdev.com>
  0 siblings, 1 reply; 6+ messages in thread
From: Paul Bolle @ 2014-10-22 16:35 UTC (permalink / raw)
  To: kernelnewbies

Having looked into this a bit, but failing to come up with something
helpful, I decided to ask some additional info.

On Tue, 2014-10-21 at 21:54 -0400, John de la Garza wrote:
> I have my kernel

Which version (roughly)?

>  built with dev-i2c and i2c_i801

.config, please?

>  but do not have
> a /dev entry.
> 
> lspci shows this:
> 00:1f.3 SMBus: Intel Corporation 5 Series/3400 Series Chipset SMBus Controller (rev 06)

What are the PCI vendor and device codes? See "lspci -nn".

> dmesg shows this:
> [    1.566003] i801_smbus 0000:00:1f.3: enabling device (0000 -> 0003)
> 
> ls /sys/bus/i2c/devices/ shows nothing...
> 
> on running this on a MacBookPro6,2
> 
> What am I missing?  Shouldn't I see a i2c device?  I think SMBus is
> a subset of i2c and I should be able to use that subset, right?


Paul Bolle

^ permalink raw reply	[flat|nested] 6+ messages in thread

* i2c-dev
       [not found]   ` <20141022172729.GA3098@vega.jjdev.com>
@ 2014-10-23 18:15     ` Paul Bolle
  2014-10-26 16:04       ` i2c-dev John de la Garza
  0 siblings, 1 reply; 6+ messages in thread
From: Paul Bolle @ 2014-10-23 18:15 UTC (permalink / raw)
  To: kernelnewbies

On Wed, 2014-10-22 at 13:27 -0400, John de la Garza wrote:
> On Wed, Oct 22, 2014 at 06:35:02PM +0200, Paul Bolle wrote:
> > Having looked into this a bit, but failing to come up with something
> > helpful, I decided to ask some additional info.
> > 
> > On Tue, 2014-10-21 at 21:54 -0400, John de la Garza wrote:
> > > I have my kernel
> > 
> > Which version (roughly)?
> 
> Linux vega 3.18.0-rc1+ #71 SMP Wed Oct 22 00:49:21 EDT 2014 x86_64 GNU/Linux
> > 
> > >  built with dev-i2c and i2c_i801
> > 
> > .config, please?
> > 
> see below
> 
> > >  but do not have
> > > a /dev entry.
> > > 
> > > lspci shows this:
> > > 00:1f.3 SMBus: Intel Corporation 5 Series/3400 Series Chipset SMBus Controller (rev 06)
> > 
> > What are the PCI vendor and device codes? See "lspci -nn".
> > 
> 00:1f.3 SMBus [0c05]: Intel Corporation 5 Series/3400 Series Chipset SMBus Controller [8086:3b30] (rev 06)
> > > dmesg shows this:
> > > [    1.566003] i801_smbus 0000:00:1f.3: enabling device (0000 -> 0003)

I'm afraid I can't really help you here, sorry. That is, except for the
obvious question whether this is a regression (ie, do releases v3.17 or
earlier show something in /sys/bus/i2c/devices/?) or a configuration
issue (perhaps a distribution provided kernel does show what you want).

Hope this helps,


Paul Bolle

^ permalink raw reply	[flat|nested] 6+ messages in thread

* i2c-dev
  2014-10-23 18:15     ` i2c-dev Paul Bolle
@ 2014-10-26 16:04       ` John de la Garza
  0 siblings, 0 replies; 6+ messages in thread
From: John de la Garza @ 2014-10-26 16:04 UTC (permalink / raw)
  To: kernelnewbies

On Thu, Oct 23, 2014 at 08:15:53PM +0200, Paul Bolle wrote:
> I'm afraid I can't really help you here, sorry. That is, except for the
> obvious question whether this is a regression (ie, do releases v3.17 or
> earlier show something in /sys/bus/i2c/devices/?) or a configuration
> issue (perhaps a distribution provided kernel does show what you want).
> 

I didn't have any devices drivers loaded for things that had
i2c devices.  I loaded the i915 gpu driver and now I see stuff.

root at vega:/home/john/linux# i2cdetect  -l
i2c-0	i2c       	i915 gmbus ssc                  	I2C adapter
i2c-1	i2c       	i915 gmbus vga                  	I2C adapter
i2c-2	i2c       	i915 gmbus panel                	I2C adapter
i2c-3	i2c       	i915 gmbus dpc                  	I2C adapter
i2c-4	i2c       	i915 gmbus dpb                  	I2C adapter
i2c-5	i2c       	i915 gmbus dpd                  	I2C adapter
i2c-6	i2c       	DPDDC-B                         	I2C adapter

^ permalink raw reply	[flat|nested] 6+ messages in thread

* i2c-dev
  2005-05-19  6:24 i2c-dev gianluca interbartolo
@ 2005-05-19  6:24 ` Mark Studebaker
  0 siblings, 0 replies; 6+ messages in thread
From: Mark Studebaker @ 2005-05-19  6:24 UTC (permalink / raw)
  To: lm-sensors

recent versions of sensors-detect should find the busses under /sys.
Get our latest userspace tools and it should work.

gianluca interbartolo wrote:
> Hi,
> I'm using kernel 2.6.4 and module i2c-viapro (I have an Asus A7V8X).
> When I load i2c-dev I get no error, but under /proc/bus there is no i2c
> directory. So using sensors-detect gives an error trying to open
> /proc/bus/i2c.
> Instead there is a /sys/bus/i2c directory, with subdirs that have no
> files. What does it mean? There is a different approach despite of
> documentation or a bug in i2c-dev?
> Bye,
> 
> Gianluca Interbartolo
> 
> 
> 
> 

^ permalink raw reply	[flat|nested] 6+ messages in thread

* i2c-dev
@ 2005-05-19  6:24 gianluca interbartolo
  2005-05-19  6:24 ` i2c-dev Mark Studebaker
  0 siblings, 1 reply; 6+ messages in thread
From: gianluca interbartolo @ 2005-05-19  6:24 UTC (permalink / raw)
  To: lm-sensors

Hi,
I'm using kernel 2.6.4 and module i2c-viapro (I have an Asus A7V8X).
When I load i2c-dev I get no error, but under /proc/bus there is no i2c
directory. So using sensors-detect gives an error trying to open
/proc/bus/i2c.
Instead there is a /sys/bus/i2c directory, with subdirs that have no
files. What does it mean? There is a different approach despite of
documentation or a bug in i2c-dev?
Bye,

Gianluca Interbartolo



^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2014-10-26 16:04 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-10-22  1:54 i2c-dev John de la Garza
2014-10-22 16:35 ` i2c-dev Paul Bolle
     [not found]   ` <20141022172729.GA3098@vega.jjdev.com>
2014-10-23 18:15     ` i2c-dev Paul Bolle
2014-10-26 16:04       ` i2c-dev John de la Garza
  -- strict thread matches above, loose matches on Subject: below --
2005-05-19  6:24 i2c-dev gianluca interbartolo
2005-05-19  6:24 ` i2c-dev Mark Studebaker

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.