From: Jani Nikula <jani.nikula@intel.com>
To: Hamza Mahfooz <hamza.mahfooz@amd.com>,
dri-devel@lists.freedesktop.org, amd-gfx@lists.freedesktop.org
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [RESEND 3/3] drm/amd/display: switch to guid_gen() to generate valid GUIDs
Date: Wed, 28 Aug 2024 18:10:49 +0300 [thread overview]
Message-ID: <87h6b4y96u.fsf@intel.com> (raw)
In-Reply-To: <87mskwyc6p.fsf@intel.com>
On Wed, 28 Aug 2024, Jani Nikula <jani.nikula@intel.com> wrote:
> On Wed, 28 Aug 2024, Hamza Mahfooz <hamza.mahfooz@amd.com> wrote:
>> On 8/12/24 08:23, Jani Nikula wrote:
>>> Instead of just smashing jiffies into a GUID, use guid_gen() to generate
>>> RFC 4122 compliant GUIDs.
>>>
>>> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
>>>
>>> ---
>>
>> Acked-by: Hamza Mahfooz <hamza.mahfooz@amd.com>
>>
>> I would prefer to take this series through the amdgpu tree though,
>> assuming nobody minds.
>
> How long is it going to take for that to get synced back to
> drm-misc-next though?
Also getting acks from Alex and Harry to merge via drm-misc-next.
BR,
Jani.
>
> BR,
> Jani.
>
>
>>
>>>
>>> Side note, it baffles me why amdgpu has a copy of this instead of
>>> plumbing it into drm mst code.
>>> ---
>>> .../gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c | 23 ++++++++++---------
>>> 1 file changed, 12 insertions(+), 11 deletions(-)
>>>
>>> diff --git a/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c b/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c
>>> index 72c10fc2c890..ce05e7e2a383 100644
>>> --- a/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c
>>> +++ b/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c
>>> @@ -2568,9 +2568,9 @@ static int dm_late_init(void *handle)
>>>
>>> static void resume_mst_branch_status(struct drm_dp_mst_topology_mgr *mgr)
>>> {
>>> + u8 buf[UUID_SIZE];
>>> + guid_t guid;
>>> int ret;
>>> - u8 guid[16];
>>> - u64 tmp64;
>>>
>>> mutex_lock(&mgr->lock);
>>> if (!mgr->mst_primary)
>>> @@ -2591,26 +2591,27 @@ static void resume_mst_branch_status(struct drm_dp_mst_topology_mgr *mgr)
>>> }
>>>
>>> /* Some hubs forget their guids after they resume */
>>> - ret = drm_dp_dpcd_read(mgr->aux, DP_GUID, guid, 16);
>>> - if (ret != 16) {
>>> + ret = drm_dp_dpcd_read(mgr->aux, DP_GUID, buf, sizeof(buf));
>>> + if (ret != sizeof(buf)) {
>>> drm_dbg_kms(mgr->dev, "dpcd read failed - undocked during suspend?\n");
>>> goto out_fail;
>>> }
>>>
>>> - if (memchr_inv(guid, 0, 16) == NULL) {
>>> - tmp64 = get_jiffies_64();
>>> - memcpy(&guid[0], &tmp64, sizeof(u64));
>>> - memcpy(&guid[8], &tmp64, sizeof(u64));
>>> + import_guid(&guid, buf);
>>>
>>> - ret = drm_dp_dpcd_write(mgr->aux, DP_GUID, guid, 16);
>>> + if (guid_is_null(&guid)) {
>>> + guid_gen(&guid);
>>> + export_guid(buf, &guid);
>>>
>>> - if (ret != 16) {
>>> + ret = drm_dp_dpcd_write(mgr->aux, DP_GUID, buf, sizeof(buf));
>>> +
>>> + if (ret != sizeof(buf)) {
>>> drm_dbg_kms(mgr->dev, "check mstb guid failed - undocked during suspend?\n");
>>> goto out_fail;
>>> }
>>> }
>>>
>>> - import_guid(&mgr->mst_primary->guid, guid);
>>> + guid_copy(&mgr->mst_primary->guid, &guid);
>>>
>>> out_fail:
>>> mutex_unlock(&mgr->lock);
--
Jani Nikula, Intel
next prev parent reply other threads:[~2024-08-28 15:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-12 12:23 [RESEND 1/3] drm/mst: switch to guid_t type for GUID Jani Nikula
2024-08-12 12:23 ` [RESEND 2/3] drm/mst: switch to guid_gen() to generate valid GUIDs Jani Nikula
2024-08-28 13:16 ` Daniel Vetter
2024-08-12 12:23 ` [RESEND 3/3] drm/amd/display: " Jani Nikula
2024-08-28 13:20 ` Daniel Vetter
2024-08-28 13:40 ` Jani Nikula
2024-08-28 13:58 ` Alex Deucher
2024-08-28 15:08 ` Harry Wentland
2024-08-29 9:32 ` Jani Nikula
2024-08-28 13:53 ` Hamza Mahfooz
2024-08-28 14:06 ` Jani Nikula
2024-08-28 15:10 ` Jani Nikula [this message]
2024-08-28 15:13 ` Hamza Mahfooz
2024-08-28 13:00 ` [RESEND 1/3] drm/mst: switch to guid_t type for GUID Daniel Vetter
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=87h6b4y96u.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=hamza.mahfooz@amd.com \
--cc=intel-gfx@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).