All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wojciech Kromer <krom@dgt-lab.com.pl>
To: linuxppc-embedded@lists.linuxppc.org
Subject: pcf8563 and i2c kernel abstarct
Date: Thu, 26 Jun 2003 14:37:05 +0200	[thread overview]
Message-ID: <3EFAE8F1.4010406@dgt-lab.com.pl> (raw)


Hell there.

I have some toubles using pcf8563_rtc driver. It causes 'kernel panic'
in rtc_rd function. I've done some debugging, ad discoverd what
back-follows:

- i2c_client *clnt is not set on call to rtc_rd
- it was called from pcf8563_rtc_init (by now = pcf8563_get_rtc_time();)
- clnt is created in pcf8563_attach
- prior call to i2c_add_driver(&pcf8563_driver) does not call
   pcf8563_attach, which should be caled from this part of
   i2c-core.c:i2c_add_driver:

/* now look for instances of driver on our adapters

               if (driver->flags& (I2C_DF_NOTIFY|I2C_DF_DUMMY)) {
                                for (i=0;i<I2C_ADAP_MAX;i++)
                                                 if (adapters[i]!=NULL)
                                                                  /*
Ignore errors */
      driver->attach_adapter(adapters[i]);


-this is because adapters[...] are not set


Q:
- did i miss anything adding this driver
- where and how adaptes should be set


?
I need only add support in ppc_md, so I can write my own functions to
implement talking with pcf8563. But... why to reinvent working (or not
?) code?


--
* * * * * * * * * * * *
* per pedes ad astra! *
* * * * * * * * * * * *    mailto:krom@dgt-lab.com.pl


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

             reply	other threads:[~2003-06-26 12:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-26 12:37 Wojciech Kromer [this message]
2003-06-26 13:09 ` pcf8563 and i2c kernel abstarct Wojciech Kromer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3EFAE8F1.4010406@dgt-lab.com.pl \
    --to=krom@dgt-lab.com.pl \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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.