11 Jul, 2011
1 commit
-
Signed-off-by: Michael Witten
Signed-off-by: Jiri Kosina
22 Nov, 2010
1 commit
-
This reverts commit 0a57274ea026c2b7670683947b6cc08b195148cf.
Signed-off-by: Arnaud Lacombe
Signed-off-by: Mauro Carvalho Chehab
25 Oct, 2010
1 commit
-
drivers/i2c/algos/Kconfig makes all the algorithms dependent on
!I2C_HELPER_AUTO, which triggers a Kconfig warning about broken
dependencies when some driver selects one of the algorithms. Ideally
we would make only the prompts dependent on !I2C_HELPER_AUTO, however
Kconfig doesn't currently support that. So we have to redefine the
symbols separately for the I2C_HELPER_AUTO=y case.Signed-off-by: Jean Delvare
Acked-by: Michal Marek
12 Aug, 2010
2 commits
-
I2C driver for PCA954x I2C multiplexer series.
Signed-off-by: Michael Lawnick
Acked-by: Rodolfo Giometti
Signed-off-by: Jean Delvare -
Add multiplexed bus core support. I2C multiplexer and switches
like pca954x get instantiated as new adapters per port.Signed-off-by: Michael Lawnick
Acked-by: Rodolfo Giometti
Signed-off-by: Jean Delvare
14 Mar, 2010
2 commits
-
Now that directory drivers/i2c/chips is gone, configuration option
I2C_DEBUG_CHIP no longer has any effect, so we can drop it.Signed-off-by: Jean Delvare
Acked-by: Wolfram Sang -
Move the last remaining driver from i2c/chips to misc. Good ridance!
Signed-off-by: Jean Delvare
Acked-by: Wolfram Sang
Acked-by: Jonathan Cameron
02 Mar, 2010
1 commit
-
Having a separate Kconfig option for i2c-smbus makes it possible to
build that support as a module even when i2c-core itself is built-in.
Bus drivers which implement SMBus alert should select this option, so
in most cases this option is hidden and the user doesn't have to care
about it.Signed-off-by: Jean Delvare
Cc: David Brownell
Cc: Trent Piepho
07 Dec, 2009
1 commit
-
Low priority thread holding the i2c bus mutex could block higher
priority threads to access the bus resulting in unacceptable
latencies. Change the mutex type to rt_mutex preventing priority
inversion.Tested-by: Peter Ujfalusi
Signed-off-by: Mika Kuoppala
Signed-off-by: Jean Delvare
19 Sep, 2009
1 commit
-
Some user-space applications may be relying on i2c adapters showing up
as class devices in sysfs. Provide compatibility links for them for
the time being. We will remove them after a long transition period.Signed-off-by: Jean Delvare
Cc: Kay Sievers
11 Aug, 2008
1 commit
-
In kernel 2.6.26, the ability to select I2C algorithm drivers manually
was removed, as all in-kernel drivers do that automatically. However
there were some complaints that it was a problem for out-of-tree I2C
bus drivers. In order to address these complaints, let's allow manual
selection of these drivers again, but still hide them by default for
better general user experience.This closes bug #11140:
http://bugzilla.kernel.org/show_bug.cgi?id=11140Signed-off-by: Jean Delvare
10 May, 2007
1 commit
-
Add "depends on HAS_IOMEM" to a number of menus to make them
disappear for s390 which does not have I/O memory.Signed-off-by: Martin Schwidefsky
02 May, 2007
2 commits
-
Allow the whole I2C menu to be disabled at once without diving into
the submenus for deselecting all options (should the user desire so).Signed-off-by: Jan Engelhardt
Signed-off-by: Jean Delvare -
This provides partial support for new-style I2C driver binding. It builds
on "struct i2c_board_info" declarations that identify I2C devices on a given
board. This is needed on systems with I2C devices that can't be fully probed
and/or autoconfigured, such as many embedded Linux configurations where the
way a given I2C device is wired may affect how it must be used.There are two models for declaring such devices:
* LATE -- using a public function i2c_new_device(). This lets modules
declare I2C devices found *AFTER* a given I2C adapter becomes available.For example, a PCI card could create adapters giving access to utility
chips on that card, and this would be used to associate those chips with
those adapters.* EARLY -- from arch_initcall() level code, using a non-exported function
i2c_register_board_info(). This copies the declarations *BEFORE* such
an i2c_adapter becomes available, arranging that i2c_new_device() will
be called later when i2c-core registers the relevant i2c_adapter.For example, arch/.../.../board-*.c files would declare the I2C devices
along with their platform data, and I2C devices would behave much like
PNPACPI devices. (That is, both enumerate from board-specific tables.)To match the exported i2c_new_device(), the previously-private function
i2c_unregister_device() is now exported.Pending later patches using these new APIs, this is effectively a NOP.
Signed-off-by: David Brownell
Signed-off-by: Jean Delvare
27 Sep, 2006
1 commit
-
i2c: Fix copy-n-paste in subsystem Kconfig
We have:
drivers/i2c/Kconfig:2:# Character device configuration
Which is obviously not true..Signed-off-by: Arthur Othieno
Signed-off-by: Jean Delvare
Signed-off-by: Greg Kroah-Hartman
17 Apr, 2005
1 commit
-
Initial git repository build. I'm not bothering with the full history,
even though we have it. We can create a separate "historical" git
archive of that later if we want to, and in the meantime it's about
3.2GB when imported into git - space that would just make the early
git days unnecessarily complicated, when we don't have a lot of good
infrastructure for it.Let it rip!
