From: Brad Campbell <lists2009@fnarfbargle.com>
To: Alex Deucher <alexdeucher@gmail.com>
Cc: airlied@redhat.com, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: Re: Radeon regression fix
Date: Fri, 30 Sep 2011 13:14:56 +0800 [thread overview]
Message-ID: <4E855050.8080403@fnarfbargle.com> (raw)
In-Reply-To: <CADnq5_NJuGLWB-1d+TGqTxW6ZOOQ4QeQj1e6dXOffL5egZuw1g@mail.gmail.com>
On 30/09/11 12:59, Alex Deucher wrote:
> On Thu, Sep 29, 2011 at 8:23 PM, Brad Campbell
>> Looking at it with a nights sleep, it's obvious the code path in
>> aux_native_write is ok. Is this a bit cleaner than the last patch?
>
> Looks pretty good. I was thinking of something more like this (sorry
> for the lack of a patch, I'm away from my source trees at the moment):
>
> while (1) {
> ret = radeon_process_aux_ch(dig_connector->dp_i2c_bus,
> msg, msg_bytes, recv, recv_bytes, delay,&ack);
>
> if (ret< 0)
> return ret;
> if ((ack& AUX_NATIVE_REPLY_MASK) == AUX_NATIVE_REPLY_ACK)
> return ret;
> else if ((ack& AUX_NATIVE_REPLY_MASK) == AUX_NATIVE_REPLY_DEFER)
> udelay(400);
> else if (ret == 0)
> return -EPROTO;
> else
> return -EIO;
> }
Yep, that looks cleaner.
My only thought was the pre-3.0 code had a limit to the number of
retries. Was that for a specific reason or is it ok to attempt to retry
indefinitely if we receive a DEFER ?
>
> Thanks for tracking this down.
No worries. I learned quite a bit about some kernel internals and more
than a few quirks about apple hardware while muddling around.
next prev parent reply other threads:[~2011-09-30 5:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-29 14:21 Radeon regression fix Brad Campbell
2011-09-29 14:36 ` Alex Deucher
2011-09-29 15:10 ` Brad Campbell
2011-09-29 15:21 ` Brad Campbell
2011-09-30 0:23 ` Brad Campbell
2011-09-30 4:59 ` Alex Deucher
2011-09-30 5:14 ` Brad Campbell [this message]
2011-09-30 5:39 ` Alex Deucher
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=4E855050.8080403@fnarfbargle.com \
--to=lists2009@fnarfbargle.com \
--cc=airlied@redhat.com \
--cc=alexdeucher@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@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