From: Jose Abreu <Jose.Abreu@synopsys.com>
To: Nick Bowler <nbowler@draconx.ca>, Jose Abreu <Jose.Abreu@synopsys.com>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>,
<linux-kernel@vger.kernel.org>, <dri-devel@lists.freedesktop.org>,
Dave Airlie <airlied@redhat.com>,
"Linus Torvalds" <torvalds@linux-foundation.org>
Subject: Re: PROBLEM: Asus C201 video mode problems on HDMI hotplug (regression)
Date: Mon, 4 Dec 2017 10:04:31 +0000 [thread overview]
Message-ID: <3c938f3f-fa1f-b08a-5ca5-b2044ed6fb4c@synopsys.com> (raw)
In-Reply-To: <20171203052045.5povltrffufaic7o@aura.draconx.ca>
On 03-12-2017 05:20, Nick Bowler wrote:
>
> Your patch changes things. With this applied on top of 4.15-rc1
> it is failing 100% of the time instead of only half of the time.
Ok, it was a long shot anyway.
>
> I brought the original test equipment back to the setup so I can
> see the video and pink bar again. The symptoms remain the same
> (unexpected size, pink bar, and no audio).
>
Can you tell me which test equipment are you using?
> It is very consistent: pink bar <=> no audio.
>
> My suspicion is that the audio problem is just the wrong video mode
> on the sink side messing things up, but I have no way of confirming
> that (that I know of).
Hmmm, my first thought was that audio is being configured first
because of the phy lock wait time, I've seen this happening before.
Lets try this:
- Disable all alsa clients (e.g. pulseaudio, ...) so that no one
tries to configure audio.
- Plug out/in the cable until the issue appears
- When the issue appears use aplay to play audio through the HDMI
output
- Repeat several times with different audio rates and with no
resample (you can use the plughw interface in aplay).
>
> Thanks,
> Nick
next prev parent reply other threads:[~2017-12-04 10:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-02 5:16 Nick Bowler
2017-11-05 16:41 ` Nick Bowler
2017-11-16 6:28 ` Nick Bowler
2017-11-27 4:05 ` Archit Taneja
2017-11-27 9:00 ` Laurent Pinchart
2017-11-27 16:34 ` Nick Bowler
2017-11-28 3:30 ` Nick Bowler
2017-12-01 0:11 ` Nick Bowler
2017-12-02 17:11 ` Jose Abreu
2017-12-03 5:20 ` Nick Bowler
2017-12-04 10:04 ` Jose Abreu [this message]
2017-12-04 18:33 ` Nick Bowler
2017-12-05 6:18 ` Nick Bowler
2017-12-04 19:06 ` Laurent Pinchart
2017-12-04 19:30 ` Nick Bowler
2017-12-04 19:34 ` Laurent Pinchart
2017-12-05 3:22 ` Nick Bowler
2017-12-05 9:41 ` Laurent Pinchart
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=3c938f3f-fa1f-b08a-5ca5-b2044ed6fb4c@synopsys.com \
--to=jose.abreu@synopsys.com \
--cc=airlied@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nbowler@draconx.ca \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®