Am 12.09.2010 um 19:45 schrieb Dr. H. Nikolaus Schaller:
>
> Am 11.09.2010 um 16:21 schrieb Daniel Gloeckner:
>
>> Hi,
>>
>> On Sat, Sep 11, 2010 at 03:53:47PM +0200, Dr. H. Nikolaus Schaller wrote:
>>> Or do you mean changeing the module_init(i2c_adap_jz_init); to
>>> subsys_initcall(i2c_adap
Am 11.09.2010 um 16:21 schrieb Daniel Gloeckner:
> Hi,
>
> On Sat, Sep 11, 2010 at 03:53:47PM +0200, Dr. H. Nikolaus Schaller wrote:
>> Or do you mean changeing the module_init(i2c_adap_jz_init); to
>> subsys_initcall(i2c_adap_jz_init); ?
>
> yes, that's what I ment.
I now tried to replace
MO
Ok,
I will give that a try!
But I am not sure if it solves the i2c_get_adapter(0) problem.
Or are there two lists of adapters? One where adapters are prepared for
initialization
and another one where the really probed adapters are searched in? If that is the
case, a pure change in the initializa
Hi,
On Sat, Sep 11, 2010 at 03:53:47PM +0200, Dr. H. Nikolaus Schaller wrote:
> Or do you mean changeing the module_init(i2c_adap_jz_init); to
> subsys_initcall(i2c_adap_jz_init); ?
yes, that's what I ment.
Daniel
___
Mipsbook-devel mailing list
Mip
Hi Daniel,
thanks for the infos!
The code to register the platform device is in a arch_initcall:
struct platform_device jz_i2c_device = {
.name = "jz_i2c",
.id = 0,
.dev = {
.dma_mask = &jz_i2c_dmamask,
.coherent_dma_mask
On Fri, Sep 10, 2010 at 09:54:57PM +0200, Dr. H. Nikolaus Schaller wrote:
> Does anyone have an idea or knowledge how initialization of the
> i2c subsystem really works in the 2.6.24 kernel?
>
> As far as I did understand, the platform initialization file just registers
> a i2c adapter in some lis
Am 07.09.2010 um 19:28 schrieb Dr. H. Nikolaus Schaller:
> Hi,
> I finally have fixed (at least I think so) all bugs in that *!:#x)
> drivers/i2c/busses/i2c-jz47xx.c
>
> 1. i2c_transfer (resp. the platform specific driver i2c_jz_xfer) has
> been completely reworked to do correctly:
>
> * send m
