- 28 Oct, 2005 40 commits
-
-
John W. Linville authored
Cleanup the need_restore switch statement in pci_set_power_state(). This makes it more safe by explicitly handling all the PCI power states instead of handling them as the default case. It also reads a little better IMHO. Signed-off-by:
John W. Linville <linville@tuxdriver.com> Signed-off-by:
Greg Kroah-Hartman <gregkh@suse.de>
-
Brian King authored
IPR scsi adapter have an exposure today in that they issue BIST to the adapter to reset the card. If, during the time it takes to complete BIST, userspace attempts to access PCI config space, the host bus bridge will master abort the access since the ipr adapter does not respond on the PCI bus for a brief period of time when running BIST. On PPC64 hardware, this master abort results in the host PCI bridge isolating that PCI device from the rest of the system, making the device unusable until Linux is rebooted. This patch makes use of some newly added PCI layer APIs that allow for protection from userspace accessing config space of a device in scenarios such as this. Signed-off-by:
Brian King <brking@us.ibm.com> Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org> Cc: James Bottomley <James.Bottomley@steeleye.com> Signed-off-by:
Andrew Morton <akpm@osdl.org> Signed-off-by:
-
Brian King authored
Some PCI adapters (eg. ipr scsi adapters) have an exposure today in that they issue BIST to the adapter to reset the card. If, during the time it takes to complete BIST, userspace attempts to access PCI config space, the host bus bridge will master abort the access since the ipr adapter does not respond on the PCI bus for a brief period of time when running BIST. On PPC64 hardware, this master abort results in the host PCI bridge isolating that PCI device from the rest of the system, making the device unusable until Linux is rebooted. This patch is an attempt to close that exposure by introducing some blocking code in the PCI code. When blocked, writes will be humored and reads will return the cached value. Ben Herrenschmidt has also mentioned that he plans to use this in PPC power management. Signed-off-by:
-
R.Marek@sh.cvut.cz authored
This patch just adds ACPI and GPIO regions to its LPC bridge, similar way as ICH4 did. I would like to thank Michal Mleczko for testing. Signed-off-by:
Rudolf Marek <r.marek@sh.cvut.cz> Signed-off-by:
-
Linus Torvalds authored
-
Greg Kroah-Hartman authored
This is the start of adding hotplug-like support for i2c devices. Signed-off-by: -
Greg Kroah-Hartman authored
as devfs is gone, this isn't needed anymore. Signed-off-by: -
Jean Delvare authored
The SMSC LPC47M997 Super-I/O chip seems to be compatible with the LPC47M192, so it is supported by the smsc47m1 driver. Signed-off-by:
Jean Delvare <khali@linux-fr.org> Signed-off-by:
-
Jean Delvare authored
Update the I2C addresses for the ADM1032 and ADT7461 chips. Also update the links to the Analog Devices web site. Signed-off-by:
-
Jean Delvare authored
Add PEC support to the lm90 driver. Only the ADM1032 chip supports it, and in a rather tricky way, which is why this patch comes with documentation reinforcements. At least, this demonstrates that the new PEC support logic in i2c-core can properly deal with chips with partial PEC support. As enabling PEC causes a significant performance drop, it can be disabled through a sysfs file (unsurprisingly named "pec"). Signed-off-by:
-
Jean Delvare authored
Preparatory patch to add PEC support to the lm90 driver. We need a centralized function to read register values, where the PEC code will be later inserted. A positive side effect is that read errors are now handled properly. Signed-off-by:
-
Jean Delvare authored
The tests leading to the use of hardware PEC in the i2c-i801 driver can be simplified. Signed-off-by:
-
Jean Delvare authored
The new SMBus PEC implementation doesn't support PEC emulation on non-PEC non-I2C SMBus masters, so we can drop all related code. Signed-off-by:
-
Jean Delvare authored
This is my rewrite of the SMBus PEC support. The original implementation was known to have bugs (credits go to Hideki Iwamoto for reporting many of them recently), and was incomplete due to a conceptual limitation. The rewrite affects only software PEC. Hardware PEC needs very little code and is mostly untouched. Technically, both implementations differ in that the original one was emulating PEC in software by modifying the contents of an i2c_smbus_data union (changing the transaction to a different type), while the new one works one level lower, on i2c_msg structures (working on message contents). Due to the definition of the i2c_smbus_data union, not all SMBus transactions could be handled (at least not without changing the definition of this union, which would break user-space compatibility), and those which could had to be implemented individually. At the opposite, adding PEC to an i2c_msg structure can be done on any SMBus transaction with common code. Advantages of the new implementation: * It's about twice as small (from ~136 lines before to ~70 now, only counting i2c-core, including blank and comment lines). The memory used by i2c-core is down by ~640 bytes (~3.5%). * Easier to validate, less tricky code. The code being common to all transactions by design, the risk that a bug can stay uncovered is lower. * All SMBus transactions have PEC support in I2C emulation mode (providing the non-PEC transaction is also implemented). Transactions which have no emulation code right now will get PEC support for free when they finally get implemented. * Allows for code simplifications in header files and bus drivers (patch follows). Drawbacks (I guess there had to be at least one): * PEC emulation for non-PEC capable non-I2C SMBus masters was dropped. It was based on SMBus tricks and doesn't quite fit in the new design. I don't think it's really a problem, as the benefit was certainly not worth the additional complexity, but it's only fair that I at least mention it. Lastly, let's note that the new implementation does slightly affect compatibility (both in kernel and user-space), but doesn't actually break it. Some defines will be dropped, but the code can always be changed in a way that will work with both the old and the new implementations. It shouldn't be a problem as there doesn't seem to be many users of SMBus PEC to date anyway. Signed-off-by:
-
Jean Delvare authored
Discard I2C_FUNC_SMBUS_*_PEC defines. i2c clients are not supposed to check for PEC support of i2c bus drivers on individual SMBus transactions, and i2c bus drivers are not supposed to advertise them. Signed-off-by:
-
Jean Delvare authored
Update the documented list of devices supported by the i2c-i810 driver. Signed-off-by:
-
Jean Delvare authored
Drop unused i2c-over-parallel-port i2c IDs: * I2C_HW_B_LPC was never actually used as far as I could search. * I2C_HW_B_ELV and I2C_HW_B_VELLE are no more used since the introduction of the unified i2c-parport driver in Linux 2.6.2. Signed-off-by:
-
Jean Delvare authored
Fix several redefinitions of i2c IDs. i2c IDs must not be defined outside of i2c-id.h. Signed-off-by:
Henk Vergonet <henk@god.dyndns.org> Acked-by:
Mark McClelland <mark@alpha.dyndns.org> Signed-off-by:
-
Ben Dooks authored
Fix functions declared static and then implemented without the static in drivers/i2c/chips. Signed-off-by:
Ben Dooks <ben-linux@fluff.org> Signed-off-by:
-
Ben Dooks authored
Fixup functions that have been declared static and then actually defined without the static on. Signed-off-by:
-
Ben Dooks authored
lm78.c and lm85.c have a number of items declared static then implemented without the static on them. The following patch fixes these sparse errors. Signed-off-by:
-
Ben Dooks authored
eeprom_detect is first declared static and then when the function is actually implemented, there is no static. Signed-off-by:
-
Jean Delvare authored
Update the i2c documentation: kzalloc should be used instead of kmalloc. I also fixed a couple other things nearby in writing-clients, as several past changes had never been reported there. Signed-off-by:
-
Jean Delvare authored
Use kzalloc instead of kmalloc in the S4882 SMBus multiplexing driver. I guess it's safer that way. Signed-off-by:
-
Jean Delvare authored
Drop useless casts on kzalloc returned values, as suggested by Jiri Slaby. Signed-off-by:
-
Deepak Saxena authored
Use kzalloc instead of kmalloc+memset in all remaining i2c bus and chip drivers. Signed-off-by:
Deepak Saxena <dsaxena@plexity.net> Signed-off-by:
-
Deepak Saxena authored
Use kzalloc instead of kmalloc+memset in all hardware monitoring drivers. Signed-off-by:
-
Deepak Saxena authored
Use kzalloc instead of kmalloc+memzero in the ixp2000 and ixp4xx I2C bus drivers. Signed-off-by:
Deepak Saxena <dsaxena@mvista.com> Signed-off-by:
-
Alessandro Zummo authored
New driver for the Xicor X1205 RTC chip. Signed-off-by:
Alessandro Zummo <alessandro.zummo@towertech.it> Signed-off-by:
-
Jean Delvare authored
The atxp1 and ds1621 drivers should make sure they do not probe non-hwmon i2c adapters. Signed-off-by:
-
Mark M. Hoffman authored
This patch adds a new ID to the SMSC LPC47B397-NC hardware monitoring driver - for a chip that is claimed to be 100% compatible otherwise. Signed-off-by: Bryan Young (Utilitek Systems, Inc.) Signed-off-by:
Mark M. Hoffman <mhoffman@lightlink.com> Signed-off-by:
-
Laurent Riffard authored
In function i2c_isa_add_driver, copied driver should inherit the owner field as well as the name field. Signed-off-by:
Laurent Riffard <laurent.riffard@free.fr> Signed-off-by:
-
Laurent Riffard authored
This patch updates the .owner field for the i2c core struct xxxx_driver variables. Signed-off-by:
-
Laurent Riffard authored
This patch updates the .owner field for various struct xxxx_driver variables which are available on PPC_MAC arch. This one was _not_ even compile-tested... Signed-off-by:
-
Laurent Riffard authored
This patch updates the .owner field for various struct xxxx_driver variables, other than pci_driver. Signed-off-by:
Jean Delvare <khali@linux-fr> Acked-by:
Mark A. Greer <mgreer@mvista.com> Acked-by:
-
Laurent Riffard authored
This patch updates .owner field for various struct pci_driver variables. Signed-off-by:
-
Stig Telfer authored
Cleanups to the i2c-elektor driver: * Set the i2c_adapter name field to "i2c-elektor" and use this string in all resource requests and printks. * Change space-padding for tab indentation, kill trailing white space, remove space before comma. * Use dev_info, pr_info and pr_debug instead of printk. * Lines chopped to 80 columns. Signed-off-by:
Stig Telfer <stig@lizardlogic.co.uk> Signed-off-by:
-
Stig Telfer authored
This patch updates the i2c-elektor driver, enabling it to compile cleanly, load and run. The key change is that it uses the new __iomem/iowrite8/ioread8 functions to abstract the direct or memory-mapped variants of register access. Also, the original driver would crash on module load on the Alpha because the PCI memory region was not remapped into kernel memory. I have managed the following testing: * compiled and tested it on my Alpha UP2000+ system. * compiles cleanly for x86 but I don't have the hardware to test. Signed-off-by:
-
Jean Delvare authored
I2C_DF_NOTIFY is an i2c_driver flag, using it as an i2c_client flag doesn't make any sense. Signed-off-by:
Randy Vinson <rvinson@mvista.com> Signed-off-by:
-
Jean Delvare authored
It's a bit confusing to name a variable the same as an unrelated structure. The compiler doesn't complain, but it certainly makes the code harder to understand, and could confuse grep and LXR among others. Signed-off-by:
-
