| Age | Commit message (Collapse) | Author |
|---|
|
cookie down to the device. the most obvious use of this is to pass a
device its ofw node on sparc64 and macppc so it can configure itself more
appropriately.
ok kettenis@ henning@ deraadt@
|
|
after teaching it to use a function pointer to get back to the OFW
scan.. this will also help the sparc64 later; ok kettenis
|
|
|
|
banks at other addresses, but there are issues with accessing these other
devices. so allow a driver to "knock" these out from future probing.
tested by kettenis -- unfortunate enough to have one of these winbond pieces
of poo
|
|
|
|
|
|
|
|
have drivers for. iic(4) will scan the bus for them and try to
attach an appropriate driver.
For now iic(4) scans for all possible addresses for debugging purposes.
ok deraadt@
|
|
pointers. This lets their match() functions actually make real decisions.
OF-capable machines will pass name/compat pointers, but other machines
will not. grudging ok kettenis
|
|
for NetBSD (r).
This framework supports various i2c master controllers:
- dumb bit-bang controllers
- a few styles of automated controllers that give you control
over sending start/stop conditions on the i2c bus
- automated controllers that are too smart for its own good,
giving software no control over start/stop conditions
- smbus controllers by emulating smbus protocol with i2c commands
i2c slave devices need their addresses to be specified in the kernel
config file, no device discovery presented.
ok deraadt@
|
