From: Harry Wentland <hwentlan-5C7GfCeVMHo@public.gmane.org>
To: "Kazlauskas,
Nicholas" <Nicholas.Kazlauskas-5C7GfCeVMHo@public.gmane.org>,
"Wentland, Harry" <Harry.Wentland-5C7GfCeVMHo@public.gmane.org>,
"amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org"
<amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org>
Cc: "Deucher,
Alexander" <Alexander.Deucher-5C7GfCeVMHo@public.gmane.org>,
"Cheng, Tony" <Tony.Cheng-5C7GfCeVMHo@public.gmane.org>
Subject: Re: [PATCH 1/3] drm/amd/display: Add ASICREV_IS_PICASSO
Date: Tue, 14 May 2019 20:24:15 +0000 [thread overview]
Message-ID: <76f60775-72bd-7a36-a2d9-88b9475dd2eb@amd.com> (raw)
In-Reply-To: <387c6572-f872-44e1-3b41-de6ae957646d-5C7GfCeVMHo@public.gmane.org>
On 2019-05-14 2:20 p.m., Kazlauskas, Nicholas wrote:
> [CAUTION: External Email]
>
> On 5/14/19 1:49 PM, Harry Wentland wrote:
>>
>> [WHY]
>> We only want to load DMCU FW on Picasso and Raven 2, not on Raven 1.
>>
>> Signed-off-by: Harry Wentland <harry.wentland@amd.com>
>> ---
>> drivers/gpu/drm/amd/display/include/dal_asic_id.h | 7 ++++---
>> 1 file changed, 4 insertions(+), 3 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/amd/display/include/dal_asic_id.h b/drivers/gpu/drm/amd/display/include/dal_asic_id.h
>> index 1a9b7507784f..072d8d7debf5 100644
>> --- a/drivers/gpu/drm/amd/display/include/dal_asic_id.h
>> +++ b/drivers/gpu/drm/amd/display/include/dal_asic_id.h
>> @@ -139,13 +139,14 @@
>> #define RAVEN1_F0 0xF0
>> #define RAVEN_UNKNOWN 0xFF
>>
>> -#if defined(CONFIG_DRM_AMD_DC_DCN1_01)
>> -#define ASICREV_IS_RAVEN2(eChipRev) ((eChipRev >= RAVEN2_A0) && (eChipRev < 0xF0))
>> -#endif /* DCN1_01 */
>> #define ASIC_REV_IS_RAVEN(eChipRev) ((eChipRev >= RAVEN_A0) && eChipRev < RAVEN_UNKNOWN)
>> #define RAVEN1_F0 0xF0
>> #define ASICREV_IS_RV1_F0(eChipRev) ((eChipRev >= RAVEN1_F0) && (eChipRev < RAVEN_UNKNOWN))
>>
>> +#if defined(CONFIG_DRM_AMD_DC_DCN1_01)
>> +#define ASICREV_IS_PICASSO(eChipRev) ((eChipRev >= PICASSO_A0) && (eChipRev < RAVEN2_A0))
>> +#define ASICREV_IS_RAVEN2(eChipRev) ((eChipRev >= RAVEN2_A0) && (eChipRev < 0xF0))
>> +#endif /* DCN1_01 */
>
> Actually, I just realized a problem with doing this. You'll break builds
> that don't have DCN enabled with the second patch because you're
> guarding these behind the define and the second patch checks
> ASICREV_IS_PICASSO outside of any guard at all.
>
Whoops. I missed that. The subsequent change ("Drop DCN1_01 guards")
fixes that.
I probably should've ordered these differently.
Harry
> Nicholas Kazlauskas
>
>>
>> #define FAMILY_RV 142 /* DCN 1*/
>>
>> --
>> 2.21.0
>>
>> _______________________________________________
>> amd-gfx mailing list
>> amd-gfx@lists.freedesktop.org
>> https://lists.freedesktop.org/mailman/listinfo/amd-gfx
>>
>
> _______________________________________________
> amd-gfx mailing list
> amd-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/amd-gfx
>
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
prev parent reply other threads:[~2019-05-14 20:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-14 17:49 [PATCH 1/3] drm/amd/display: Add ASICREV_IS_PICASSO Harry Wentland
[not found] ` <20190514174935.28605-1-harry.wentland-5C7GfCeVMHo@public.gmane.org>
2019-05-14 17:49 ` [PATCH 2/3] drm/amd/display: Don't load DMCU for Raven 1 Harry Wentland
2019-05-14 17:49 ` [PATCH 3/3] drm/amd/display: Drop DCN1_01 guards Harry Wentland
[not found] ` <20190514174935.28605-3-harry.wentland-5C7GfCeVMHo@public.gmane.org>
2019-05-14 18:02 ` Kazlauskas, Nicholas
[not found] ` <6373fba9-967a-8ea0-ceb4-45dc8f599a73-5C7GfCeVMHo@public.gmane.org>
2019-05-14 18:16 ` Harry Wentland
2019-05-14 18:20 ` [PATCH 1/3] drm/amd/display: Add ASICREV_IS_PICASSO Kazlauskas, Nicholas
[not found] ` <387c6572-f872-44e1-3b41-de6ae957646d-5C7GfCeVMHo@public.gmane.org>
2019-05-14 20:24 ` Harry Wentland [this message]
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=76f60775-72bd-7a36-a2d9-88b9475dd2eb@amd.com \
--to=hwentlan-5c7gfcevmho@public.gmane.org \
--cc=Alexander.Deucher-5C7GfCeVMHo@public.gmane.org \
--cc=Harry.Wentland-5C7GfCeVMHo@public.gmane.org \
--cc=Nicholas.Kazlauskas-5C7GfCeVMHo@public.gmane.org \
--cc=Tony.Cheng-5C7GfCeVMHo@public.gmane.org \
--cc=amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.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