From: Jean Delvare <khali@linux-fr.org>
To: Alex Deucher <alexdeucher@gmail.com>
Cc: DRI Development Mailing List <dri-devel@lists.sourceforge.net>
Subject: Re: [PATCHES] radeon drm kms i2c fixes
Date: Mon, 15 Mar 2010 13:56:49 +0100 [thread overview]
Message-ID: <20100315135649.76236154@hyperion.delvare> (raw)
In-Reply-To: <a728f9f91003140937ifb9ec5cjdb19ddb443dfbc64@mail.gmail.com>
On Sun, 14 Mar 2010 11:37:02 -0500, Alex Deucher wrote:
> On Wed, Mar 10, 2010 at 7:09 PM, Alex Deucher <alexdeucher@gmail.com> wrote:
> > Thanks to Jean for helping me with the i2c stuff. I've attached
> > Jean's bit algo patch as my radeon patch depends on it. I'm not sure
> > how we want to get that one upstream (either via drm or i2c).
> > Previously, the radeon drm registered i2c buses using the radeon algo
> > which would use either the hw i2c engine or bit banging depending on
> > the bus in question (some are hw capable, others are not, some chips
> > don't have support for their hw engines yet, etc.). The tricky part
> > was that the radeon i2c bit buses require some gpio magic before and
> > after a transaction which bit algo didn't previously support.
> > Unfortunately, it exposed the internal bit algo bus as well we as the
> > radeon algo bus which is bad. With these patches, if the hw engine is
> > supported, we use the radeon algo, if not, we use bit algo directly
> > with the pre/post_xfer functions to fix up the gpios. I've tested on
> > several radeons, but more tested would be nice.
>
> Updated patch based on Jean's new version of the pre/post_xfer patch
> (also attached) which he plans to push upstream via the i2c tree.
FYI, the pre/post-xfer patch is upstream now:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=0a9c14751377a1407f5e35791e13651d2fc7801c
--
Jean Delvare
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
--
_______________________________________________
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel
prev parent reply other threads:[~2010-03-15 12:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-11 0:09 [PATCHES] radeon drm kms i2c fixes Alex Deucher
2010-03-11 18:00 ` Jean Delvare
2010-03-11 18:35 ` Alex Deucher
2010-03-15 13:03 ` Jean Delvare
2010-03-15 16:17 ` Johannes Engel
2010-03-14 16:37 ` Alex Deucher
2010-03-15 12:56 ` Jean Delvare [this message]
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=20100315135649.76236154@hyperion.delvare \
--to=khali@linux-fr.org \
--cc=alexdeucher@gmail.com \
--cc=dri-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 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.