All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jocelyn Falempe <jfalempe@redhat.com>
To: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/ast: Fix default resolution when no monitor is connected on DP
Date: Thu, 13 Jul 2023 10:53:23 +0200	[thread overview]
Message-ID: <90f7b5f9-9805-39d3-801a-babd10f1a0cf@redhat.com> (raw)
In-Reply-To: <36e04e4c-c2ac-64cf-9503-ea43a29b66d0@mailbox.org>

On 13/07/2023 10:32, Michel Dänzer wrote:
> On 7/12/23 17:25, Jocelyn Falempe wrote:
>> On 12/07/2023 17:05, Sui Jingfeng wrote:
>>> On 2023/7/10 16:07, Jocelyn Falempe wrote:
>>>
>>>> On the other hand, are there any drawback to present a BMC connector even when the hardware doesn't have it ?
>>>
>>> If not properly setting up, I think you will create two encoder and two connector in the system.
>>
>> Yes, but I think it won't have any visible effect for the end-user.
> 
> I'm afraid user-space display servers would waste effort producing content for a non-existing BMC (assuming its connector status is connected or unknown).
> 
> 
I think it's already the case, as AST's DP and VGA connectors currently 
always report "connected" status. And they all share the same crtc, so 
there is only one framebuffer, that is always active.

Best regards,

-- 

Jocelyn


  parent reply	other threads:[~2023-07-13  8:53 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
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 [this message]
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=90f7b5f9-9805-39d3-801a-babd10f1a0cf@redhat.com \
    --to=jfalempe@redhat.com \
    --cc=dri-devel@lists.freedesktop.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 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.