From: Felipe Balbi <balbi@ti.com>
To: Felipe Balbi <balbi@ti.com>
Cc: <airlied@linux.ie>, <airlied@redhat.com>, <robdclark@gmail.com>,
<bparrot@ti.com>, <dri-devel@lists.freedesktop.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Darren Etheridge <detheridge@ti.com>
Subject: Re: [PATCH] drm/tilcdc increase allowable supported resolution
Date: Thu, 24 Apr 2014 12:58:25 -0500 [thread overview]
Message-ID: <20140424175825.GC4659@saruman.home> (raw)
In-Reply-To: <1393873738-27327-1-git-send-email-balbi@ti.com>
[-- Attachment #1: Type: text/plain, Size: 1188 bytes --]
On Mon, Mar 03, 2014 at 01:08:58PM -0600, Felipe Balbi wrote:
> From: Darren Etheridge <detheridge@ti.com>
>
> 1680x1050 appears to also be within the bandwidth capabilities
> of the device and memory infrastructure.
>
> Signed-off-by: Darren Etheridge <detheridge@ti.com>
ping
> ---
> 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
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
balbi
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-04-24 17:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-03 19:08 Felipe Balbi
2014-04-24 17:58 ` Felipe Balbi [this message]
2014-04-24 20:51 ` Rob Clark
2014-04-24 21:18 ` Darren Etheridge
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=20140424175825.GC4659@saruman.home \
--to=balbi@ti.com \
--cc=airlied@linux.ie \
--cc=airlied@redhat.com \
--cc=bparrot@ti.com \
--cc=detheridge@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
Powered by JetHome