On Wed, Mar 10, 2010 at 7:09 PM, Alex Deucher <alexdeuc...@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. Alex
0001-i2c-algo-bit-Add-pre-and-post-xfer-hooks.patch
Description: application/mbox
0002-drm-radeon-kms-use-new-pre-post_xfer-i2c-bit-algo-h.patch
Description: application/mbox
------------------------------------------------------------------------------ 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
