public inbox for dri-devel@lists.freedesktop.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 215436] admgpu: suspend and resuming from suspend don't work
Date: Fri, 31 Dec 2021 15:10:50 +0000	[thread overview]
Message-ID: <bug-215436-2300-XpVkDfsMO0@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-215436-2300@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=215436

--- Comment #8 from spasswolf@web.de ---
Just did a bit of experimentation and changed dc_get_hpd_state_dcn21 (in
5.16-rc7) to

uint32_t dc_get_hpd_state_dcn21(struct irq_service *irq_service, enum
dc_irq_source source)
{
        const struct irq_source_info *info;
        uint32_t addr;
        uint32_t value;
        uint32_t current_status;

        info = find_irq_source_info(irq_service, source);
        if (!info)
                return 0;

        addr = info->status_reg;
        if (!addr)
                return 0;

        value = dm_read_reg(irq_service->ctx, addr);
        //current_status =
        //      get_reg_field_value(
        //              value,
        //              HPD0_DC_HPD_INT_STATUS,
        //              DC_HPD_SENSE);

        //return current_status;
        return 0;
}
This also leads to working suspend resume, the get_reg_field_value seems to
trigger the problems.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2021-12-31 15:10 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-29 12:28 [Bug 215436] New: admgpu: suspend and resuming from suspend don't work bugzilla-daemon
2021-12-29 15:08 ` [Bug 215436] " bugzilla-daemon
2021-12-29 15:10 ` bugzilla-daemon
2021-12-30 13:03 ` bugzilla-daemon
2021-12-30 13:16 ` bugzilla-daemon
2021-12-30 14:33 ` bugzilla-daemon
2021-12-31  0:17 ` bugzilla-daemon
2021-12-31  0:22 ` bugzilla-daemon
2021-12-31 15:10 ` bugzilla-daemon [this message]
2021-12-31 16:14 ` bugzilla-daemon
2022-01-01  1:42 ` bugzilla-daemon
2022-01-03  9:29 ` bugzilla-daemon
2022-01-03  9:35 ` bugzilla-daemon
2022-01-03  9:36 ` bugzilla-daemon
2022-01-03 10:20 ` bugzilla-daemon
2022-01-03 10:29 ` bugzilla-daemon
2022-01-03 15:48 ` bugzilla-daemon
2022-01-03 17:12 ` bugzilla-daemon
2022-01-03 17:49 ` bugzilla-daemon
2022-01-03 17:51 ` bugzilla-daemon
2022-01-04 10:17 ` bugzilla-daemon
2022-01-04 10:25 ` bugzilla-daemon
2022-01-04 11:15 ` bugzilla-daemon
2022-01-04 11:27 ` bugzilla-daemon
2022-01-04 14:14 ` bugzilla-daemon
2022-01-04 14:59 ` bugzilla-daemon
2022-01-04 15:03 ` bugzilla-daemon
2022-01-04 15:27 ` bugzilla-daemon
2022-01-04 15:28 ` bugzilla-daemon
2022-01-24 22:45 ` bugzilla-daemon
2022-01-25 20:25 ` bugzilla-daemon

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=bug-215436-2300-XpVkDfsMO0@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox