public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
To: Anthony Drake <agmotorsvc-H+0wwilmMs3R7s880joybQ@public.gmane.org>
Cc: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: rtc-ds3232 driver
Date: Thu, 1 Mar 2012 21:34:14 +0100	[thread overview]
Message-ID: <20120301213414.501c5189@endymion.delvare> (raw)
In-Reply-To: <61_2012_13540_GON-2AO0Uh8ossnZ+VzJOa5vwg@public.gmane.org>

On Thu, 1 Mar 2012 19:54:00 +0000 (UTC), Anthony Drake wrote:
> On Thu, 1 Mar 2012 20:12:00 +0100,
> Wolfram Sang <w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org> wrote 
> 
> > 
> > Documentation/rtc.txt
> > 
> > --=20
> Thank you.  I am familiar with the /dev/rtc0 character device special 
> file interface, and can access it well.  My problem is that there is no
> device special file created for rtc-ds3232 module.

Odds are that the underlying I2C slave device was not instantiated.
Please read:
Documentation/i2c/instantiating-devices

Note that the rtc-ds3232 driver doesn't support method 3 (presumably
the device lacks identification and thus can't be autodetected.

-- 
Jean Delvare

  parent reply	other threads:[~2012-03-01 20:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-01 17:09 rtc-ds3232 driver Anthony Drake
     [not found] ` <61_2012_11913_GON-2AO0Uh8ossnZ+VzJOa5vwg@public.gmane.org>
2012-03-01 19:12   ` Wolfram Sang
2012-03-01 19:54     ` Anthony Drake
     [not found]       ` <61_2012_13540_GON-2AO0Uh8ossnZ+VzJOa5vwg@public.gmane.org>
2012-03-01 20:34         ` Jean Delvare [this message]
2012-03-02 17:27           ` Anthony Drake

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=20120301213414.501c5189@endymion.delvare \
    --to=khali-puyad+kwke1g9huczpvpmw@public.gmane.org \
    --cc=agmotorsvc-H+0wwilmMs3R7s880joybQ@public.gmane.org \
    --cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@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