ATH11K Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: wi nk <wink@technolu.st>
Cc: Mitchell Nordine <mail@mitchellnordine.com>,
	"ath11k\@lists.infradead.org" <ath11k@lists.infradead.org>
Subject: Re: Have the QCA6390 patches for XPS 9310 landed yet?
Date: Mon, 02 Aug 2021 17:06:08 +0300	[thread overview]
Message-ID: <875ywodjqn.fsf@codeaurora.org> (raw)
In-Reply-To: <CAHUdJJWAbwnjUgSXEwVCu7TL6byD26FxZyMN4ZaR4o1eHQypYA@mail.gmail.com> (wi nk's message of "Fri, 30 Jul 2021 22:08:17 +0200")

wi nk <wink@technolu.st> writes:

> I've been running 5.12 and 5.13 without WIFI issues. Occasionally I
> still have bluetooth problems and the i915 drivers are causing video
> artifacts randomly, but the wireless connection seems pretty solid at
> this point.

I also see the random video artifacts but reverting this commit (ie.
adding back the tigerlake workaround) fixes the issue:

f9c914a5b946 Revert "drm/i915/display/fbc: Disable fbc by default on TGL"

I have not reported this bug yet to i915 developers, it would be great
if someone else could do it.

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

-- 
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k

  parent reply	other threads:[~2021-08-02 14:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-18 16:30 Have the QCA6390 patches for XPS 9310 landed yet? Mitchell Nordine
2021-07-30 20:00 ` Kalle Valo
2021-07-30 20:08   ` wi nk
2021-07-30 21:52     ` Justin Mazzola Paluska
2021-07-30 21:57       ` wi nk
2021-07-30 22:11       ` Jens Gecius
2021-08-02  7:20         ` Dominik Förderer
2021-08-02 14:06     ` Kalle Valo [this message]
2021-08-04 13:06     ` Mitchell Nordine
2021-08-26 14:40       ` Kalle Valo

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=875ywodjqn.fsf@codeaurora.org \
    --to=kvalo@codeaurora.org \
    --cc=ath11k@lists.infradead.org \
    --cc=mail@mitchellnordine.com \
    --cc=wink@technolu.st \
    /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