All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Jocelyn Falempe <jfalempe@redhat.com>,
	tzimmermann@suse.de, airlied@redhat.com,
	kuohsiang_chou@aspeedtech.com, jammy_huang@aspeedtech.com
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/ast: Fix default resolution when no monitor is connected on DP
Date: Thu, 06 Jul 2023 12:32:46 +0300	[thread overview]
Message-ID: <87h6qhxu4h.fsf@intel.com> (raw)
In-Reply-To: <ed075f2f-861d-74d1-efc0-5baa2cd601fd@redhat.com>

On Thu, 06 Jul 2023, Jocelyn Falempe <jfalempe@redhat.com> wrote:
> On 04/07/2023 18:45, Jocelyn Falempe wrote:
>> On 04/07/2023 16:54, Jani Nikula wrote:
>>> On Fri, 23 Jun 2023, Jocelyn Falempe <jfalempe@redhat.com> wrote:
>>>> Since commit fae7d186403e ("drm/probe-helper: Default to 640x480 if no
>>>>   EDID on DP")
>>>> The default resolution is now 640x480 when no monitor is connected.
>>>> But Aspeed graphics is mostly used in servers, where no monitor
>>>> is attached. This also affects the "remote" resolution to 640x480, 
>>>> which is
>>>> inconvenient, and breaks the anaconda installer.
>>>> So when no EDID is present, set 1024x768 as preferred resolution.
>>>
>>> This conflates "monitor connected" and "EDID present", which are not
>>> necessarily the same thing.
>>>
>>> The fallback in drm_helper_probe_single_connector_modes() is for no
>>> modes, but connector status is connected or unknown.
>> 
>> When debugging the issue, I found it surprising that the status is 
>> "connected" when nothing is plugged in the DP port.
>>>
>>> You could add a connector ->detect callback that returns disconnected
>>> when there's no display, and the problem should go away. If there's no
>>> ->detect callback, it'll default to connected.
>> 
>> ok, I'll try that. I don't know how the hardware detect something is 
>> connected, but looking at the dp code, maybe checking 
>> "AST_IO_CRTC_PORT,0xDC, ASTDP_LINK_SUCCESS" would be good enough.
>
> I've tested this approach, and it works.

\o/

> But on the server I'm testing, 
> there are VGA and DP output. I think on a server that has only one DP 
> output, if no monitor is connected, then no modes will be reported to 
> userspace, and the remote BMC may not work ?

I couldn't say, but having the driver lie about the connected status to
make it work feels wrong.

> Also I don't have physical access to the server, so I only tested when 
> no monitor is plugged.
>
> I will send shortly a v2 with this change, so others can help me test 
> this case.

Thanks,
Jani.


>
> Best regards,

-- 
Jani Nikula, Intel Open Source Graphics Center

  reply	other threads:[~2023-07-06  9:32 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-23  9:46 [PATCH] drm/ast: Fix default resolution when no monitor is connected on DP Jocelyn Falempe
2023-07-04 14:19 ` Thomas Zimmermann
2023-07-04 14:21   ` Thomas Zimmermann
2023-07-04 14:54 ` Jani Nikula
2023-07-04 16:45   ` Jocelyn Falempe
2023-07-06  9:16     ` Jocelyn Falempe
2023-07-06  9:32       ` Jani Nikula [this message]
2023-07-06 10:07         ` Jocelyn Falempe
2023-07-06 10:14           ` Jani Nikula
2023-07-06 10:26       ` Thomas Zimmermann
2023-07-06 11:31         ` Jocelyn Falempe
2023-07-06 16:37           ` Jocelyn Falempe
2023-07-07  7:30             ` Thomas Zimmermann
2023-07-10  8:07               ` Jocelyn Falempe
2023-07-12 15:05                 ` Sui Jingfeng
2023-07-12 15:25                   ` Jocelyn Falempe
2023-07-13  8:32                     ` Michel Dänzer
2023-07-13  8:49                       ` Thomas Zimmermann
2023-07-13  8:53                         ` Michel Dänzer
2023-07-13  9:09                           ` Thomas Zimmermann
2023-07-13  9:41                             ` Michel Dänzer
2023-07-13  8:53                       ` Jocelyn Falempe
2023-07-13  8:55                         ` Michel Dänzer
2023-07-13  8:50                   ` Thomas Zimmermann

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=87h6qhxu4h.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=airlied@redhat.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jammy_huang@aspeedtech.com \
    --cc=jfalempe@redhat.com \
    --cc=kuohsiang_chou@aspeedtech.com \
    --cc=tzimmermann@suse.de \
    /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.