From: Darren Etheridge <detheridge@ti.com>
To: Rob Clark <robdclark@gmail.com>
Cc: Felipe Balbi <balbi@ti.com>, David Airlie <airlied@linux.ie>,
"airlied@redhat.com" <airlied@redhat.com>,
Benoit Parrot <bparrot@ti.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] drm/tilcdc increase allowable supported resolution
Date: Thu, 24 Apr 2014 16:18:04 -0500 [thread overview]
Message-ID: <20140424211804.GA4101@ti.com> (raw)
In-Reply-To: <CAF6AEGuE2MvN9SrO-R2_DnWtHtxwuFLwH6kUe4vrwcREsG5XDQ@mail.gmail.com>
Rob Clark <robdclark@gmail.com> wrote on Thu [2014-Apr-24 16:51:04 -0400]:
> On Mon, Mar 3, 2014 at 2:08 PM, Felipe Balbi <balbi@ti.com> wrote:
> > From: Darren Etheridge <detheridge@ti.com>
> >
> > 1680x1050 appears to also be within the bandwidth capabilities
> > of the device and memory infrastructure.
>
> For this one, is 1680x1050 possible on all devices w/ tilcdc (like 1st
> gen beaglebone (white), etc)? If not, maybe better to keep the
> default conservative and override the default in devicetree..
>
Fair point Rob, I didn't test BeagleBone White at that resolution, only
BeagleBone Black. I'll redo this patch as a BBB specific dts change
given we already have a max-bandwidth DT binding in place for tilcdc.
Thanks for reviewing it.
Darren
> BR,
> -R
>
> > Signed-off-by: Darren Etheridge <detheridge@ti.com>
> > ---
> > drivers/gpu/drm/tilcdc/tilcdc_drv.h | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/gpu/drm/tilcdc/tilcdc_drv.h b/drivers/gpu/drm/tilcdc/tilcdc_drv.h
> > index 5bb64e3..b47ec24 100644
> > --- a/drivers/gpu/drm/tilcdc/tilcdc_drv.h
> > +++ b/drivers/gpu/drm/tilcdc/tilcdc_drv.h
> > @@ -43,7 +43,7 @@
> > * with optimized DDR & EMIF settings tweaked 1920x1080@24 appears to
> > * be supportable
> > */
> > -#define TILCDC_DEFAULT_MAX_BANDWIDTH (1280*1024*60)
> > +#define TILCDC_DEFAULT_MAX_BANDWIDTH (1680*1050*60)
> >
> >
> > struct tilcdc_drm_private {
> > --
> > 1.9.0
> >
prev parent reply other threads:[~2014-04-24 21:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-03 19:08 [PATCH] drm/tilcdc increase allowable supported resolution Felipe Balbi
2014-04-24 17:58 ` Felipe Balbi
2014-04-24 20:51 ` Rob Clark
2014-04-24 21:18 ` Darren Etheridge [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=20140424211804.GA4101@ti.com \
--to=detheridge@ti.com \
--cc=airlied@linux.ie \
--cc=airlied@redhat.com \
--cc=balbi@ti.com \
--cc=bparrot@ti.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robdclark@gmail.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