amd-gfx.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: "Guilherme G. Piccoli" <gpiccoli@igalia.com>
To: wenyou.yang@amd.com, amd-gfx list <amd-gfx@lists.freedesktop.org>
Cc: weiyuan2@amd.com, ying.li@amd.com,
	xinhui pan <Xinhui.Pan@amd.com>,
	Mario Limonciello <mario.limonciello@amd.com>,
	"kernel-dev@igalia.com" <kernel-dev@igalia.com>,
	"Deucher, Alexander" <alexander.deucher@amd.com>,
	kunliu13@amd.com, Christian Koenig <christian.koenig@amd.com>,
	"Liang, Richard qi" <Richardqi.Liang@amd.com>
Subject: Re: [Resend PATCH v1 0/3] send message to pmfw when SMT changes
Date: Thu, 23 Mar 2023 18:43:44 -0300	[thread overview]
Message-ID: <a75662b0-7e5b-16d9-735d-11b00a385a58@igalia.com> (raw)

Hi Wenyou Yang, first of all thanks for the improvement!

I'd like to ask you (and all CCed) if it would be possible to explain a
bit the goal / functionality behind these patches.

By reading the commit descriptions and code, I can understand code-wise
what's going on and how this will message the FW on SMT changes. What I
couldn't parse is the purpose of this, or in other words, what does it
gain for us? Also, why only on Vangogh?

Since I don't have the spec I couldn't read and learn myself - apologies
if this is somewhat a silly question. Also, if for some reason you
cannot respond (like a HW "NDA"), it's fine too.

Thanks in advance,


Guilherme

             reply	other threads:[~2023-03-23 21:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-23 21:43 Guilherme G. Piccoli [this message]
2023-03-27  2:49 ` [Resend PATCH v1 0/3] send message to pmfw when SMT changes Yang, WenYou
2023-03-27 14:08   ` Guilherme G. Piccoli
2023-03-28  6:07     ` Yang, WenYou
2023-03-28 12:09       ` Guilherme G. Piccoli
  -- strict thread matches above, loose matches on Subject: below --
2023-03-22  9:16 Wenyou Yang

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=a75662b0-7e5b-16d9-735d-11b00a385a58@igalia.com \
    --to=gpiccoli@igalia.com \
    --cc=Richardqi.Liang@amd.com \
    --cc=Xinhui.Pan@amd.com \
    --cc=alexander.deucher@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=christian.koenig@amd.com \
    --cc=kernel-dev@igalia.com \
    --cc=kunliu13@amd.com \
    --cc=mario.limonciello@amd.com \
    --cc=weiyuan2@amd.com \
    --cc=wenyou.yang@amd.com \
    --cc=ying.li@amd.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 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).