All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kumba <kumba@gentoo.org>
To: Manuel Lauss <manuel.lauss@googlemail.com>
Cc: Lars-Peter Clausen <lars@metafoo.de>,
	Linux MIPS List <linux-mips@linux-mips.org>,
	rtc-linux@googlegroups.com
Subject: Re: [PATCH 1/2]: Add support for Dallas/Maxim DS1685/1687 RTC
Date: Thu, 17 Feb 2011 03:17:34 -0500	[thread overview]
Message-ID: <4D5CD99E.6030300@gentoo.org> (raw)
In-Reply-To: <AANLkTimLjhY+sNuMh_gOXNuxZuFOvi25KMYFU4Xp1hbY@mail.gmail.com>

On 02/17/2011 02:31, Manuel Lauss wrote:
>
> Have a look at i2c-ocores.c:    Basically you use platform_data to specify
> register spacing on the bus.
>
> Manuel

I think I get most of it here.  i2c-ocores.c defines `struct ocores_i2c`, which 
has regstep in it.  I assume the equivalent to this in the RTC driver is going 
to be ds1685_priv.  But in i2c_ocores.h, `struct ocores_i2c_platform_data` is 
defined, which also carries a regstep.  In i2c-ocores.c, this struct becomes 
*pdata while ocores_i2c becomes *i2c, and *i2c is used to access the registers.

I don't think I have an equivalent to either of these two with the way the 
driver was originally written and how I modified it.  The ds1685_priv kinda does 
both right now.  I assume platform_data is not really defined...I have to 
implement one specific to this RTC driver, giving it specific variables that 
need to be customizable at the platform level, and then set those in the 
machine-specific areas, i.e., somewhere in IP32's platform file.

Sound correct?

-- 
Joshua Kinard
Gentoo/MIPS
kumba@gentoo.org

"The past tempts us, the present confuses us, the future frightens us.  And our 
lives slip away, moment by moment, lost in that vast, terrible in-between."

--Emperor Turhan, Centauri Republic

  reply	other threads:[~2011-02-17  8:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-15 11:39 [PATCH 1/2]: Add support for Dallas/Maxim DS1685/1687 RTC Kumba
2011-02-16 23:23 ` Lars-Peter Clausen
2011-02-17  5:45   ` Kumba
2011-02-17  7:31     ` Manuel Lauss
2011-02-17  8:17       ` Kumba [this message]
2011-02-17  8:39         ` Manuel Lauss
2011-02-17  9:57   ` Kumba
2011-02-17 11:43     ` Lars-Peter Clausen
2011-02-17 18:47       ` Kumba
2011-02-18 11:02       ` Kumba

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=4D5CD99E.6030300@gentoo.org \
    --to=kumba@gentoo.org \
    --cc=lars@metafoo.de \
    --cc=linux-mips@linux-mips.org \
    --cc=manuel.lauss@googlemail.com \
    --cc=rtc-linux@googlegroups.com \
    /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.