From: Jean Delvare <jdelvare@suse.de>
To: linux-fbdev@vger.kernel.org
Subject: Question on s3fb DDC support
Date: Sun, 03 Aug 2014 12:42:36 +0000 [thread overview]
Message-ID: <20140803144236.0494b47a@endymion.delvare> (raw)
Hi Onderj,
Are you still involved in the s3fb driver? So you still have the
hardware to test it?
I am looking at the DDC / I2C implementation in that driver and I'm not
sure I understand how it works. Specifically I am wondering about bit
DDC_DRIVE_EN. It is set unconditionally in s3fb_ddc_setscl() and
s3fb_ddc_setsda() and never cleared explicitly. If this bit is a
regular bit then I don't understand why it is not just set at driver
initialization time. Or is this bit self-clearing and/or not-sticking?
The reason why I am asking is that I don't think the code in these
functions is completely correct. For the I2C protocol, 1 is the natural
state of both lines and the devices on the bus should only ever pull
the lines low to force a 0 state. They should never force a 1 state, as
this breaks some protocol features (specifically arbitration and clock
stretching.) My interpretation of the current code is that the lines
are forced to both 0 and 1 by the master, which is not correct. But as
I don't know how DDC_DRIVE_EN works, I'm not sure, and if it's indeed
broken [1], I'm also not sure how to fix it.
So if you could clarify how bit DDC_DRIVE_EN works, that would be great.
[1] A broken implementation would work fine in most cases and fail only
seldom and randomly, so it could easily go unnoticed.
Thanks,
--
Jean Delvare
SUSE L3 Support
next reply other threads:[~2014-08-03 12:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-03 12:42 Jean Delvare [this message]
2014-08-03 14:47 ` Question on s3fb DDC support Geert Uytterhoeven
2014-08-03 15:15 ` Ondrej Zary
2014-08-03 16:03 ` Jean Delvare
2014-08-03 16:13 ` Ondrej Zary
2014-08-03 16:20 ` Jean Delvare
2014-08-03 16:33 ` Ondrej Zary
2014-08-03 20:56 ` Jean Delvare
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=20140803144236.0494b47a@endymion.delvare \
--to=jdelvare@suse.de \
--cc=linux-fbdev@vger.kernel.org \
/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).