From: Kronos <kronos@kronoz.cjb.net>
To: Jon Smirl <jonsmirl@yahoo.com>
Cc: Linux Fbdev development list <linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: Re: [PATCH] Remove voodoo code from i2c
Date: Sat, 6 Mar 2004 16:08:45 +0100 [thread overview]
Message-ID: <20040306150845.GB901@dreamland.darkstar.lan> (raw)
In-Reply-To: <20040306021016.46831.qmail@web14916.mail.yahoo.com>
Il Fri, Mar 05, 2004 at 06:10:16PM -0800, Jon Smirl ha scritto:
> Can this be written as a generic i2c probe function by calling i2c chanel
> functions instead of directly calling radeon_gpio_setscl, etc? The i2c chanel
> functions will then in turn call radeon_gpio_setscl, etc.
You can't use the i2c layer because you just send empty start-stop
sequencies on the bus, no real data. You must use bit banging functions:
struct i2c_algo_bit_data *bits = adapter->algo_data;
Then you use ->{s,g}et{scl,sda}. Remeber to pass bits->data to those
functions.
Luca
--
Home: http://kronoz.cjb.net
"It is more complicated than you think"
-- The Eighth Networking Truth from RFC 1925
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
next prev parent reply other threads:[~2004-03-06 15:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-05 21:52 [PATCH] Remove voodoo code from i2c Kronos
2004-03-05 23:55 ` Benjamin Herrenschmidt
2004-03-06 0:47 ` Kronos
2004-03-06 2:10 ` Jon Smirl
2004-03-06 3:42 ` Benjamin Herrenschmidt
2004-03-06 4:02 ` Jon Smirl
2004-03-06 15:08 ` Kronos [this message]
2004-03-08 22:17 ` Richard Smith
2004-03-08 22:56 ` Benjamin Herrenschmidt
2004-03-06 0:12 ` Michel Dänzer
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=20040306150845.GB901@dreamland.darkstar.lan \
--to=kronos@kronoz.cjb.net \
--cc=jonsmirl@yahoo.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/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).