Hi,
I'm adding support for the i2c controllers on radeon hardware and
I have a few questions. I have a radeon-algo that encapsulates all
the various hw i2c controller functionality, however, it uses a
bit-algo bus internally for cases where you have to use bit-banging
rather than the hardware i2c engines. Also, for bit banging to work
properly, you need to do some things before the bit-algo transaction
(basically masking the gpios for software use). Right now we use
bit-algo i2c for the ddc buses, but they won't work externally to the
driver without the proper gpio masking prior to using them. In the
radeon-algo patches, I use bit algo internally when I cannot use the
hardware i2c engines, or in cases where I haven't implemented support
yet for the hardware engine (as most gpios can be driven by sw or the
hw engine). The problem is, this exposes the i2c bit-algo buses as
well as the radeon-algo buses. Is there a way to not expose the
bit-algo buses that are used internally? I've attached the patches
for reference. Please cc: me as I'm not subscribed to this list.
Alex
Attachment:
0001-drm-radeon-kms-add-radeon-i2c-algo.patch
Description: application/mbox
Attachment:
0002-drm-radeon-kms-add-support-for-hw-i2c-on-r1xx-r5xx.patch
Description: application/mbox
