intel-gfx.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Jiri Slaby <jirislaby@gmail.com>
To: Rodrigo Vivi <rodrigo.vivi@intel.com>, Peter Jones <pjones@redhat.com>
Cc: David Airlie <airlied@linux.ie>,
	intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
	linux-kernel@vger.kernel.org
Subject: Re: [Intel-gfx] [PATCH] Make the "Reducing compressed framebufer size" message be DRM_INFO_ONCE()
Date: Tue, 7 Apr 2020 11:02:57 +0200	[thread overview]
Message-ID: <37f3c0dd-265e-e6a9-47d5-3a6195ca4a7c@gmail.com> (raw)
In-Reply-To: <20180706203015.GC23473@intel.com>

On 06. 07. 18, 22:30, Rodrigo Vivi wrote:
> On Fri, Jul 06, 2018 at 03:04:24PM -0400, Peter Jones wrote:
>> This was sort of annoying me:
>>
>> random:~$ dmesg | tail -1
>> [523884.039227] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS.
>> random:~$ dmesg | grep -c "Reducing the compressed"
>> 47
>>
>> This patch makes it DRM_INFO_ONCE() just like the similar message
>> farther down in that function is pr_info_once().
>>
>> Signed-off-by: Peter Jones <pjones@redhat.com>
>> ---
>>  drivers/gpu/drm/i915/intel_fbc.c | 2 +-
>>  1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/gpu/drm/i915/intel_fbc.c b/drivers/gpu/drm/i915/intel_fbc.c
>> index b431b6733cc..88b013758da 100644
>> --- a/drivers/gpu/drm/i915/intel_fbc.c
>> +++ b/drivers/gpu/drm/i915/intel_fbc.c
>> @@ -585,7 +585,7 @@ static int intel_fbc_alloc_cfb(struct intel_crtc *crtc)
>>  	if (!ret)
>>  		goto err_llb;
>>  	else if (ret > 1) {
>> -		DRM_INFO("Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS.\n");
>> +		DRM_INFO_ONCE("Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS.\n");
> 
> I know the feeling of seeing a message over and over again when you are already aware of that.
> Specially something that tells you to change BIOS configuration...
> for this reason I think it makes sense, so:
> 
> Acked-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
> 
> I will just wait for CI and give a couple days to someone else to challenge.
> If I end up forgetting to push it please ping me...

After almost two years, ping :).

> 
>>  
>>  	}
>>  
>> -- 
>> 2.17.1

thanks,
-- 
js
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2020-04-07 13:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-06 19:04 [PATCH] Make the "Reducing compressed framebufer size" message be DRM_INFO_ONCE() Peter Jones
2018-07-06 19:38 ` ✓ Fi.CI.BAT: success for " Patchwork
2018-07-06 20:30 ` [PATCH] " Rodrigo Vivi
2020-04-07  9:02   ` Jiri Slaby [this message]
2018-07-07 21:13 ` ✓ Fi.CI.IGT: success for " Patchwork

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=37f3c0dd-265e-e6a9-47d5-3a6195ca4a7c@gmail.com \
    --to=jirislaby@gmail.com \
    --cc=airlied@linux.ie \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pjones@redhat.com \
    --cc=rodrigo.vivi@intel.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).