All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Brad Campbell <lists2009@fnarfbargle.com>
Cc: linux-kernel@vger.kernel.org, michael.jamet@intel.com,
	YehezkelShB@gmail.com
Subject: Re: Thunderbolt DP oddity on v5.2.9 on iMac 12,2
Date: Fri, 13 Sep 2019 11:24:15 +0300	[thread overview]
Message-ID: <20190913082415.GA28281@lahna.fi.intel.com> (raw)
In-Reply-To: <20190903133319.GG2691@lahna.fi.intel.com>

Hi Brad,

On Tue, Sep 03, 2019 at 04:33:23PM +0300, Mika Westerberg wrote:
> On Tue, Sep 03, 2019 at 08:54:02PM +0800, Brad Campbell wrote:
> > On 3/9/19 7:55 pm, Mika Westerberg wrote:
> > > On Tue, Sep 03, 2019 at 07:11:32PM +0800, Brad Campbell wrote:
> > > 
> > > I think the problem is that for some reason, probably because this is
> > > first generation hardware with all the bugs included, you cannot read
> > > the second dword from DP adapter path config space (you can write it
> > > though).
> > > 
> > > I've updated the patch so that it reads only the first dword when it
> > > discovers paths and also when it disables them. Can you try it out and
> > > see if it makes a difference? This should also get rid of the warnings
> > > you get.
> > > 
> > 
> > It would seem so. Now I get 3 heads on a cold or warm boot and no warnings
> > in the log, so it looks like that did the job. I've attached the dmesg from
> > the last cold boot for reference.
> 
> Great, thanks for checking. I will create a proper patch and submit
> upstream hopefully later this week or early next.

Unfortunately I did not have time to create a proper patch yet. I've
been busy with other things currently. Since merge window opens next
week this would have to wait until it closes anyway. I'm trying to get
this as part of a patch series I plan to submit after v5.4-rc1 is
released.

      reply	other threads:[~2019-09-13  8:24 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-28  7:09 Thunderbolt DP oddity on v5.2.9 on iMac 12,2 Brad Campbell
2019-08-28  7:33 ` Mika Westerberg
2019-08-28  9:12   ` Brad Campbell
2019-08-28  9:34     ` Brad Campbell
2019-08-28 10:23     ` Mika Westerberg
2019-08-28 10:43       ` Brad Campbell
2019-08-28 13:19         ` Mika Westerberg
2019-08-28 16:27           ` Brad Campbell
2019-09-03 10:13             ` Mika Westerberg
2019-09-03 10:36               ` Mika Westerberg
2019-09-03 11:11               ` Brad Campbell
2019-09-03 11:55                 ` Mika Westerberg
2019-09-03 12:54                   ` Brad Campbell
2019-09-03 13:33                     ` Mika Westerberg
2019-09-13  8:24                       ` Mika Westerberg [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=20190913082415.GA28281@lahna.fi.intel.com \
    --to=mika.westerberg@linux.intel.com \
    --cc=YehezkelShB@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lists2009@fnarfbargle.com \
    --cc=michael.jamet@intel.com \
    /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.