From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Tomi Valkeinen <tomi.valkeinen@ti.com>
Cc: dri-devel@lists.freedesktop.org, Jyri Sarha <jsarha@ti.com>
Subject: Re: [PATCH] drm/omapdrm: dispc: Refuse x-decimation above 4 for all but 8-bit formats
Date: Wed, 08 Feb 2017 20:03:33 +0200 [thread overview]
Message-ID: <1653182.o8SOMWbSOr@avalon> (raw)
In-Reply-To: <f8c0f171-1955-294d-0127-bc08a266bba5@ti.com>
Hi Tomi,
On Wednesday 08 Feb 2017 15:51:08 Tomi Valkeinen wrote:
> On 07/02/17 16:41, Jyri Sarha wrote:
> > Let's disable all scaling that requires horizontal decimation with
> > higher factor than 4, until we have better estimates of what we can
> > and can not do. However, 1 byte per pixel color format appear to work
> > Ok with all decimation factors.
> >
> > When decimating horizontally by more that 4 the dss is not able to
> > fetch the data in burst mode. When this happens it is hard to tell if
> > there enough bandwidth. Despite what theory says this appears to be
> > true also for 16-bit color formats.
> >
> > Signed-off-by: Jyri Sarha <jsarha@ti.com>
> > ---
> >
> > drivers/gpu/drm/omapdrm/dss/dispc.c | 19 +++++++++++++++++++
> > 1 file changed, 19 insertions(+)
> >
> > diff --git a/drivers/gpu/drm/omapdrm/dss/dispc.c
> > b/drivers/gpu/drm/omapdrm/dss/dispc.c index 5554b72..61daef6 100644
> > --- a/drivers/gpu/drm/omapdrm/dss/dispc.c
> > +++ b/drivers/gpu/drm/omapdrm/dss/dispc.c
> > @@ -2506,6 +2506,25 @@ static int dispc_ovl_calc_scaling_44xx(unsigned
> > long pclk, unsigned long lclk,>
> > return -EINVAL;
> >
> > }
> >
> > + if (*decim_x > 4 && color_mode_to_bpp(color_mode) > 8) {
> > + /*
> > + Let's disable all scaling that requires horizontal
> > + decimation with higher factor than 4, until we have
> > + better estimates of what we can and can not
> > + do. However, 1 byte per pixel color format appear to
> > + work Ok with all decimation factors.
> > +
> > + When decimating horizontally by more that 4 the dss
> > + is not able to fetch the data in burst mode. When
> > + this happens it is hard to tell if there enough
> > + bandwidth. Despite what theory says this appears to
> > + be true also for 16-bit color formats.
> > + */
> > + DSSERR("Not enough bandwidth (x-decimation factor %d > 4)",
> > + *decim_x);
>
> I think the error message could be improved. A normal user could hit
> this when setting up a plane, and I'm quite sure the above doesn't give
> any clue to the user what the issue is (too much downscaling).
Shouldn't the message be turned into a debug message ? Otherwise you'll give a
way for users to flood the kernel log, which is never good.
--
Regards,
Laurent Pinchart
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2017-02-08 18:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-07 14:41 [PATCH] drm/omapdrm: dispc: Refuse x-decimation above 4 for all but 8-bit formats Jyri Sarha
2017-02-08 11:25 ` Laurent Pinchart
2017-02-08 11:49 ` Tomi Valkeinen
2017-02-08 13:36 ` Jyri Sarha
2017-02-08 13:51 ` Tomi Valkeinen
2017-02-08 18:03 ` Laurent Pinchart [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=1653182.o8SOMWbSOr@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jsarha@ti.com \
--cc=tomi.valkeinen@ti.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).