From: Thomas Zimmermann <tzimmermann@suse.de>
To: Jammy Huang <jammy_huang@aspeedtech.com>,
Jocelyn Falempe <jfalempe@redhat.com>,
airlied@redhat.com, kuohsiang_chou@aspeedtech.com,
jani.nikula@linux.intel.com, dianders@chromium.org
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v5 2/2] drm/ast: report connection status on Display Port.
Date: Thu, 13 Jul 2023 11:12:00 +0200 [thread overview]
Message-ID: <7f1ccdf6-dadf-c25f-a972-f3c8add488f9@suse.de> (raw)
In-Reply-To: <2b1c2a6c-c912-d24f-b622-7a3f1cec89aa@aspeedtech.com>
[-- Attachment #1.1: Type: text/plain, Size: 726 bytes --]
Hi
Am 13.07.23 um 11:05 schrieb Jammy Huang:
[...]
>>
>>
>> For the BMC connector patch, you know if there is a register setting I
>> can check to see if a BMC is present or not ?
>
> I think you can use VGA CRD0[7] whose definition is as below:
>
> DRAM Initial Selection (see note 1)
> 0: VBIOS Initial the DRAM
> 1: SOC Firmware Initial the DRAM
>
> If CRD0[7] is 1, there is BMC.
Thank you. That seems very helpful.
Best regards
Thomas
>
>>
>> Best regards,
>>
--
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Frankenstrasse 146, 90461 Nuernberg, Germany
GF: Ivo Totev, Andrew Myers, Andrew McDonald, Boudien Moerman
HRB 36809 (AG Nuernberg)
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
next prev parent reply other threads:[~2023-07-13 9:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-13 6:40 [PATCH v5 1/2] drm/ast: Add BMC virtual connector Jocelyn Falempe
2023-07-13 6:40 ` [PATCH v5 2/2] drm/ast: report connection status on Display Port Jocelyn Falempe
2023-07-13 7:00 ` Jammy Huang
2023-07-13 8:17 ` Jocelyn Falempe
2023-07-13 9:00 ` Jocelyn Falempe
2023-07-13 9:05 ` Jammy Huang
2023-07-13 9:12 ` Thomas Zimmermann [this message]
2023-07-13 9:31 ` Jocelyn Falempe
2023-07-13 13:34 ` Jocelyn Falempe
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=7f1ccdf6-dadf-c25f-a972-f3c8add488f9@suse.de \
--to=tzimmermann@suse.de \
--cc=airlied@redhat.com \
--cc=dianders@chromium.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jammy_huang@aspeedtech.com \
--cc=jani.nikula@linux.intel.com \
--cc=jfalempe@redhat.com \
--cc=kuohsiang_chou@aspeedtech.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.