linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jon Ringle <jon-7zJyie9iPacdnm+yROfE0A@public.gmane.org>
To: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
Cc: Wolfram Sang <w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>,
	Alexander Bigga <ab-g5CePrrZ5ROELgA04lAiVw@public.gmane.org>,
	rtc-linux-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org,
	linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [rtc-linux] Re: i2c/rtc init dependency problem
Date: Fri, 25 Sep 2009 15:13:43 -0400	[thread overview]
Message-ID: <152584230909251213l8f9663eo39151206e9ec8cd4@mail.gmail.com> (raw)
In-Reply-To: <20090925204533.69681f35-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>

On Fri, Sep 25, 2009 at 2:45 PM, Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org> wrote:
> On Fri, 25 Sep 2009 14:38:39 -0400, Jon Ringle wrote:
>> I think the problem is that rtc-m41t80 does not provide either of the following:
>>     struct i2c_driver: detect and address_data (both are null)
>> as required by i2c_detect()
>
> This should be OK. detect and address_data are optional and only needed
> for drivers which autodetect their devices. The rtc-m41t80 probably
> doesn't want to do this. The device should be declared by the arch or
> platform.

Can you point me to an example of how one declares a i2c device?

Thanks,
Jon

  parent reply	other threads:[~2009-09-25 19:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <152584230909240758h674ffe3cw4d5e6baef5efc9b8@mail.gmail.com>
     [not found] ` <152584230909240758h674ffe3cw4d5e6baef5efc9b8-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-09-24 15:19   ` [rtc-linux] i2c/rtc init dependency problem Wolfram Sang
     [not found]     ` <8b192c78-6ebf-42ec-b334-756f56cc5400@g6g2000vbr.googlegroups.com>
     [not found]       ` <8b192c78-6ebf-42ec-b334-756f56cc5400-kR2RjjGg49OEYCl0FQ7J0FYGCWtFR9XvQQ4Iyu8u01E@public.gmane.org>
2009-09-25  6:58         ` [rtc-linux] " Wolfram Sang
     [not found]           ` <20090925065843.GA4125-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2009-09-25 14:49             ` Jon Ringle
     [not found]               ` <152584230909250749w305b5202tba55bfedd742fea9-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-09-25 18:38                 ` Jon Ringle
     [not found]                   ` <152584230909251138r7051a279k71e10ac778e28742-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-09-25 18:45                     ` Jean Delvare
     [not found]                       ` <20090925204533.69681f35-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2009-09-25 19:13                         ` Jon Ringle [this message]
     [not found]                           ` <152584230909251213l8f9663eo39151206e9ec8cd4-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-09-25 20:19                             ` Jon Ringle

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=152584230909251213l8f9663eo39151206e9ec8cd4@mail.gmail.com \
    --to=jon-7zjyie9ipacdnm+yrofe0a@public.gmane.org \
    --cc=ab-g5CePrrZ5ROELgA04lAiVw@public.gmane.org \
    --cc=khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org \
    --cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=rtc-linux-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
    --cc=w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).